> Am 13.05.2016 um 16:26 schrieb Stuart Yoder <stuart.yo...@nxp.com>: > > > >> -----Original Message----- >> From: Alexander Graf [mailto:ag...@suse.de] >> Sent: Friday, May 13, 2016 7:22 AM >> To: u-boot@lists.denx.de >> Cc: Stuart Yoder <stuart.yo...@nxp.com>; york sun <york....@nxp.com> >> Subject: [PATCH 5/5] ls2080ardb: Convert to distro boot >> >> Most new systems in U-Boot these days make use of the generic "distro" >> framework which allows a user to have U-Boot scan for a bootable OS >> on all available media types. >> >> This patch converts the LS2080ARDB board to use that framework instead >> of booting from a hard coded flash offset. >> >> Signed-off-by: Alexander Graf <ag...@suse.de> >> >> --- >> >> This obviously means that we can no longer boot from said offset. Is >> that a reasonable thing to do or should I put the bootm back into the >> default boot command and only do distro boot if it fails? > > To date all armv8 FSL/NXP sdk releases, field engineers, etc have been using > bootm. I'm a little concerned about changing the default boot command > right now...as I assume things will unexpectedly appear to just stop > working. Or, is booting from the NOR flash one of the distro boot > "media" types?
The problem with boot from NOR is that we have no source of information on what lies where. So distro boot can't have it in its target list, as you have to know magical offsets. We could put the magical bootm after tge distro list, but that would mean that field engineers get pxe boot with long timeouts first and then their NOR bootm booted. So the only option left that I can see is to always try magical offset NOR bootm and do distro boot if it fails. Then just tell people to write zeros to the NOR kernel offset and they get distro boot automatically. Alex _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
