Hi Alex, > -----Original Message----- > From: Alexander Graf [mailto:ag...@suse.de] > Sent: Friday, May 27, 2016 7:58 PM > To: Prabhakar Kushwaha <prabhakar.kushw...@nxp.com>; u- > b...@lists.denx.de > Cc: york sun <york....@nxp.com> > Subject: Re: [U-Boot] [PATCH 1/5] ls2080: Exit dpaa only right before exiting > U-Boot > > On 05/18/2016 02:29 PM, Prabhakar Kushwaha wrote: > >> -----Original Message----- > >> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of > >> Alexander Graf > >> Sent: Friday, May 13, 2016 5:52 PM > >> To: u-boot@lists.denx.de > >> Subject: [U-Boot] [PATCH 1/5] 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> > > With this patch. > > > > If I does not apply MC, I am getting following crash:- > > > > Starting kernel ... > > > > "Synchronous Abort" handler, esr 0x96000044 > > So should we consider it a bug fix or regression then? :) > >
Are you planning to fix it? If not let me know I will try to work on it. --prabhakar _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
