Hello Bruno,
Yes, use the same U-Boot package for both bootloader and tools.
Then we have the block device (emmc, etc.) vs. mtd[1] (NAND, NOR) support
issue.
As I see there are the following solutions:
1) Select fw_printenv/fw_setenv storage support based on define in board
-Original Message-
From: ptxdist-boun...@pengutronix.de [mailto:ptxdist-boun...@pengutronix.de] On
Behalf Of Michael Olbrich
Sent: 8. august 2014 12:18
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC] u-boot-tools: emmc support in fw_printenv/fw_setenv
On Tue, Aug 05, 2014 at 02
Hello Bruno,
Am 04.08.2014 10:29, wrote Bruno Thomsen:
Provide read/write access to U-Boot environment stored in eMMC flash from
Linux.
Access to U-Boot environment can be very useful; dual kernel/rootfs images,
production default values, change kernel bootargs, etc.
Tested with U-Boot
On Tue, Aug 05, 2014 at 02:29:12PM +0200, Markus Niebel wrote:
Hello Bruno,
Am 04.08.2014 10:29, wrote Bruno Thomsen:
Provide read/write access to U-Boot environment stored in eMMC flash from
Linux.
Access to U-Boot environment can be very useful; dual kernel/rootfs images,
Hello Bruno,
Am 04.08.2014 10:29, wrote Bruno Thomsen:
Provide read/write access to U-Boot environment stored in eMMC flash from
Linux.
Access to U-Boot environment can be very useful; dual kernel/rootfs images,
production default values, change kernel bootargs, etc.
Tested with U-Boot
Provide read/write access to U-Boot environment stored in eMMC flash from Linux.
Access to U-Boot environment can be very useful; dual kernel/rootfs images,
production default values, change kernel bootargs, etc.
Tested with U-Boot 2009.08 and 2013.04 on TQMa28.
Warning! This is not ready for
