Hi Prabhakara, On 17.10.16 05:42, Prabhakar Kushwaha wrote: > Hi Alex, > >> -----Original Message----- >> From: Alexander Graf [mailto:ag...@suse.de] >> Sent: Saturday, October 15, 2016 3:33 PM >> To: u-boot@lists.denx.de >> Cc: york sun <york....@nxp.com>; Prabhakar Kushwaha >> <prabhakar.kushw...@nxp.com> >> Subject: [PATCH v5 1/7] ls2080: Exit dpaa only right before exiting U-Boot >> >> On ls2080 we have a separate network fabric component which we need to >> shut down before we enter Linux (or any other OS). Along with that also >> comes configuration of the fabric using a description file. >> >> Today we always stop and configure the fabric in the boot script and >> (again) exit it on device tree generation. This works ok for the normal >> booti case, but with bootefi the payload we're running may still want to >> access the network. >> >> So let's add a new fsl_mc command that defers configuration and stopping >> the hardware to when we actually exit U-Boot, so that we can still use >> the fabric from an EFI payload. >> >> For existing boot scripts, nothing should change with this patch. >> >> Signed-off-by: Alexander Graf <ag...@suse.de> >> > > Can we get one small modification in this patch to include env variable. > So if a user **always** want " lazyapply", this info can be stored in env > variable. This env variable will be used after reset without explicit u-boot > command.
I'm not sure I understand your suggestion. We use "lazyapply" because EFI payloads need to be able to use the fabric for network I/O which is impossible after a normal apply. Because we don't know in bootcmd whether we will end up in the old bootm path or in the fallback distro path (which again potentially means efi_loader), we have to play safe (lazyapply) by default. Alex _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot