From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 11 Oct 2017 14:41:38 -0400 Subject: [U-Boot] fsl_esdhc driver is broken with DM In-Reply-To: References: <20171001144930.GG3503@bill-the-cat> Message-ID: <20171011184138.GO12015@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 Wed, Oct 11, 2017 at 01:09:04PM -0300, Fabio Estevam wrote: > On Wed, Oct 11, 2017 at 1:06 PM, Jagan Teki wrote: > > > I've observed here, u-boot is unable to relocate. So when I build > > U-Boot with removing u-boot,dm-spl from dts it works fine, but idea > > here I need to use SPL_OF_CONTROL and it is not related to DM_MMC I > > suppose. > > Ok, a different bug then. > > I was wondering if we could have some automated boot tests in U-Boot mainline? > > Something like https://kernelci.org/ for U-Boot? The problem(s) there are related to lack of hardware support for testing firmware in a CI type environment. For example, I do test/py/test.py on real hardware before every push cycle. The problem for iMX in this case at least is that I haven't seen (nor had a chance to come up with) the scripting to update u-boot from within u-boot, to catch the kind of failures that we don't see when doing the USB recovery boot method. I can test sabrelite via u-boot.imx (and in theory I could test my hummingboard with SPL, but my quick pass at enabling USB gadget support there didn't seem to work). I would very much welcome more labs running tests however. There's already a few, but I guess the gap we see right here and now is that there's none for iMX. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: