svn-archive/archive/package/utils/nvram/src, branch master

nvram: get rid of NVRAM_SPACE

2015-07-08T06:05:43Z

Now we support NVRAM whatever its size is. Signed-off-by: Rafał Miłecki SVN-Revision: 46262

nvram: fix displayed info about NVRAM size

2015-07-08T05:42:30Z

Use actual partition size and content offset to calculate it. Signed-off-by: Rafał Miłecki SVN-Revision: 46260

Revert "Revert "nvram: increase NVRAM size to 64 KiB""

2015-07-07T22:06:04Z

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 SVN-Revision: 46253

nvram: fix "Segmentation fault" caused by setting memory out of buffer

2015-07-07T21:21:49Z

Some MTD partitions with NVRAM have content starting in the middle. In such case offset is set and nvram_header returns pointer to the middle. It means we have to respect offset when calculating remaining space. By the way use real MTD partition size (nvram_part_size variable) as we may want to bump NVRAM_SPACE in the (very near) future. Signed-off-by: Rafał Miłecki SVN-Revision: 46251

Revert "nvram: increase NVRAM size to 64 KiB"

2015-04-24T15:38:38Z

This reverts commit ff84c27a281bc19df19bc62ee8688cca5586f6e3. This tool has really broken size handling (many values hardcoded), it crashes right now in case of NVRAM not filling whole MTD partition. Conflicts: package/utils/nvram/src/nvram.h Signed-off-by: Rafał Miłecki SVN-Revision: 45579

nvram: fix regression in finding NVRAM beginning

2015-04-24T14:28:57Z

The loop was giving up too early as it never expected NVRAM smaller than 0x10000. Signed-off-by: Rafał Miłecki SVN-Revision: 45578

nvram: increase NVRAM size to 64 KiB

2015-04-22T19:07:24Z

For years Broadcom devices use 64 KiB NVRAM partition size and some of them indeed have it filled in more than 50%. This change allows handling whole NVRAM e.g. on Netgear WNDR4500 and Netgear R8000. The same fix was applied to kernel in upstream commit 6ab7c29. Reported-by: Hante Meuleman Signed-off-by: Rafał Miłecki SVN-Revision: 45566

nvram: refuse to open NVRAM for writing if it's too big to be handled

2015-04-22T19:07:19Z

Otherwise writing anything will result in loosing data. Signed-off-by: Rafał Miłecki SVN-Revision: 45565

nvram: drop check for WGT634U using /proc/diag/model

2015-04-22T19:07:12Z

We don't have broadcom-diag for months or years now and the correct solution is to simply don't have "nvram" partition on WGT634U anyway. Signed-off-by: Rafał Miłecki SVN-Revision: 45564

nvram: use correct variable name for MTD partition size

2015-04-22T19:07:06Z

Sytax of /proc/mtd is following: dev: size erasesize name which means that sscanf "mtd%d: %08x" reads size, not erasesize. Signed-off-by: Rafał Miłecki SVN-Revision: 45563