From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Beno=c3=aet_Th=c3=a9baudeau?= <benoit@wsystem.com>
Date: Tue, 6 Oct 2015 17:00:31 +0200
Subject: [U-Boot] Inconsistencies in commands regarding load_addr
Message-ID: <5613E20F.8060306@wsystem.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi all,

I've just noticed that before the commit
045fa1e1142552799ad3203e9e0bc22a11e866ea, ext2load and ext4load were setting the
load_addr global variable, but not fatload. Since then, none of these commands
set load_addr (initially derived from the loadaddr environment variable).

ubifsload also does not set load_addr, but a quick grep shows that some other
filesystem commands set it, e.g. for zfs, jffs2, reiser or cramfs.

Also, some commands set it only on success, while some other commands set it
from the command line arguments unconditionally.

What's the expected correct behavior here?

Best regards,
Beno?t