From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 29 Apr 2016 14:06:53 -0400 Subject: [U-Boot] spl_mmc: allow to load raw image In-Reply-To: References: <1456745517-19797-1-git-send-email-yamada.masahiro@socionext.com> <20160317020452.GX23166@bill-the-cat> <20160317161210.GB23166@bill-the-cat> <20160429175350.GZ19598@bill-the-cat> Message-ID: <20160429180653.GA19598@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Apr 29, 2016 at 01:06:14PM -0500, Adam Ford wrote: > On Fri, Apr 29, 2016 at 12:53 PM, Tom Rini wrote: > > On Fri, Apr 29, 2016 at 09:59:00AM -0500, Adam Ford wrote: > > > >> Does anyone with an OMAP3 board have any issues with this patch? I > >> will admit I haven't stayed on top of stuff due to moving, and other > >> issues at home, but I pulled down the master to reviews some on > >> related stuff, and found that master doesn't boot. I used git bisect > >> this morning and it narrowed down a problem with booting to this > >> patch. > >> > >> With the patch, I get: > >> > >> U-Boot SPL 2016.03-00378-g4976f48 (Apr 29 2016 - 09:25:27) > >> Trying to boot from MMC > > > > OK. Do you have u-boot.bin or u-boot.img (which?) written to the raw > > offset in MMC or from filesystem? Based on the log it looks like > > filesystem. > > I have u-boot.img copied to the fatfs on the card, but I didn't put it > in a specific location. > > I never used to have to do that. Is this a new behavior and is it > documented somewhere? No what you're doing is a valid use case that should be working, thanks. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: