diff options
| author | Rafał Miłecki <zajec5@gmail.com> | 2015-07-07 22:06:04 +0000 |
|---|---|---|
| committer | Rafał Miłecki <zajec5@gmail.com> | 2015-07-07 22:06:04 +0000 |
| commit | 4014ba376c685bb151324183b64d01cd523aed63 (patch) | |
| tree | ca85297c8d1df2f5537267d538956c450d935ece /.gitignore | |
| parent | 9f158499108eae39555bc65d1abfd86bd0c65533 (diff) | |
| download | master-31e0f0ae-4014ba376c685bb151324183b64d01cd523aed63.tar.gz master-31e0f0ae-4014ba376c685bb151324183b64d01cd523aed63.tar.bz2 master-31e0f0ae-4014ba376c685bb151324183b64d01cd523aed63.zip | |
Revert "Revert "nvram: increase NVRAM size to 64 KiB""
This reverts commit r45579.
With the latest change r46251 ("nvram: fix "Segmentation fault" caused
by setting memory out of buffer") nvram utility shouldn't crash anymore.
It was tested on 3 brcm47xx devices:
1) Unknown with 0x10000 NVRAM size (0x8000 offset)
2) Linksys E1000 V2.1 with 0x10000 (0x8000 offset)
3) Linksys WRT300N V1 with 0x10000 (0x8000 offset)
And 3 bcm53xx devices:
1) Buffalo WZR-600DHP2 with 0x160000 NVRAM size
2) Buffalo WZR-1750DHP with 0x10000 NVRAM size
3) Netgear R6250 V1 with 0x180000 NVRAM size
(all using 0 offset)
This is an important change as it allows reading whole NVRAM. This may
critical when reading some basic configuration (e.g. switch ports).
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46253
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions