From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Date: Fri, 27 May 2016 16:27:47 +0200 Subject: [U-Boot] [PATCH 1/5] ls2080: Exit dpaa only right before exiting U-Boot In-Reply-To: References: <1463142095-182586-1-git-send-email-agraf@suse.de> <1463142095-182586-2-git-send-email-agraf@suse.de> Message-ID: <57485963.6030405@suse.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 05/18/2016 02:29 PM, Prabhakar Kushwaha wrote: >> -----Original Message----- >> From: U-Boot [mailto:u-boot-bounces at lists.denx.de] On Behalf Of >> Alexander Graf >> Sent: Friday, May 13, 2016 5:52 PM >> To: u-boot at 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 > 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? :) Alex