[U-Boot] [PATCH 2/2] configs: dragonboard410c: Save environment data on eMMC

[Tom Rini]

On Wed, Nov 08, 2017 at 08:49:09AM +0100, Jorge Ramirez wrote:
> On 11/07/2017 11:50 PM, Tom Rini wrote:
> >On Mon, Nov 06, 2017 at 02:16:38PM +0100, Jorge Ramirez-Ortiz wrote:
> >
> >>Save the environment data at the end of the boot partition on emmc
> >>
> >>Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz at linaro.org>
> >>---
> >>  arch/arm/dts/dragonboard410c-uboot.dtsi | 7 +++++++
> >>  configs/dragonboard410c_defconfig       | 2 ++
> >>  include/configs/dragonboard410c.h       | 1 +
> >>  3 files changed, 10 insertions(+)
> >Implementation this seems fine.  Is there a reason to do this vs
> >ENV_IS_IN_FAT?  Or ENV_IS_IN_EXT ? And have it be in a filesystem
> >instead?  That usually seems to be best for eval/dev/etc style boards.
> 
> I think having it on a partition offset (a partition that typically just
> stores the uboot image) can be very convenient when having the filesystem on
> an NFS share.
> 
> It means that the user can completely ignore flashing and maintaining the
> filesystem until he is ready. The only issue I see is that it is up to the
> user - when he reprograms a new image or modifies the size of the
> environemnt- to make sure the environment and whatever image is in the
> partition dont overlap each other but I think that should be acceptable?

Well, if you think environment in flash is best, that's fine.  I just
want to make sure the alternatives are known as I keep surprising people
when I note that the env can be a file in FAT or similar.  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171108/ed3f7f8e/attachment.sig>