On 09/05/2014 18:14, Owen Kirby wrote:
> On 14-05-08 11:09 PM, Luka Perkov wrote:
>> On Thu, May 08, 2014 at 02:07:13PM -0700, Matthew Fatheree
>> wrote:
>>> From 4a9565f1139fbb585727638fd69a0437bdd212b6 Mon Sep 17
>>> 00:00:00 2001 From: Matthew Fatheree
>>> <matthew.fathe...@belkin.com> Date: Sun, 4 May 2014 19:04:04
>>> +0700 Subject: [PATCH 15/30] mamba mvebu: add fw_printenv tool
>>> to read U-boot environment from Linux
>>>
>>> The /tmp/fw_env.config is generated by looking for the "u_env"
>>> partition at the system startup
>>>
>>> Signed-off-by: Matthew Fatheree <matthew.fathe...@belkin.com>
>>> --- package/linksys-base-files/files/etc/fw_env.config | 1
>>> + .../files/lib/preinit/04_fw_env_config_init | 18
>>> ++++++++++++++++++ 2 files changed, 19 insertions(+) create
>>> mode 120000 package/linksys-base-files/files/etc/fw_env.config
>>> create mode 100644
>>> package/linksys-base-files/files/lib/preinit/04_fw_env_config_init
>>
>>>
NACK. Package uboot-envtools should be extended for this feature.
> This is actually a feature we've wanted to implement on our boards
> as well, but we went about it the same was as Belkin did with some
> board-specific preinit scripts that parsed /proc/mtd. We weren't
> sure if there was a generic way way to probe the MTD partitions for
> U-boot environments without relying on the partition name.
>
> For example, the u-boot environment format doesn't have any magic
> numbers in the header (though, a valid CRC would be a good
> heuristic check), and the backup environments might be left as
> erased flash.
>
the feature might make sense but not placed in that package without
integration into uboot-envtools.
John
> Cheers, Owen _______________________________________________
> openwrt-devel mailing list openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
