From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fsl_esdhc driver is broken with DM
Date: Wed, 11 Oct 2017 14:41:38 -0400 [thread overview]
Message-ID: <20171011184138.GO12015@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5BvQ1rHC71kfT3pqsm63t_ir6WbuzS-YhfKRBRsFn4L5A@mail.gmail.com>
On Wed, Oct 11, 2017 at 01:09:04PM -0300, Fabio Estevam wrote:
> On Wed, Oct 11, 2017 at 1:06 PM, Jagan Teki <jagannadh.teki@gmail.com> 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: <http://lists.denx.de/pipermail/u-boot/attachments/20171011/b3b005c1/attachment.sig>
next prev parent reply other threads:[~2017-10-11 18:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 15:35 [U-Boot] fsl_esdhc driver is broken with DM Fabio Estevam
2017-10-01 14:29 ` Fabio Estevam
2017-10-01 14:49 ` Tom Rini
2017-10-01 15:50 ` Fabio Estevam
2017-10-01 17:46 ` Łukasz Majewski
2017-10-01 19:13 ` Fabio Estevam
2017-10-02 10:23 ` Jagan Teki
2017-10-02 11:06 ` Fabio Estevam
2017-10-09 18:05 ` Jagan Teki
2017-10-10 11:48 ` Fabio Estevam
2017-10-11 10:17 ` Jagan Teki
2017-10-11 15:49 ` Fabio Estevam
2017-10-11 16:06 ` Jagan Teki
2017-10-11 16:09 ` Fabio Estevam
2017-10-11 16:29 ` Jagan Teki
2017-10-11 18:41 ` Tom Rini [this message]
2017-10-13 8:16 ` Lukasz Majewski
2017-10-13 13:33 ` Fabio Estevam
2017-10-16 20:51 ` Jagan Teki
2017-10-16 21:52 ` Fabio Estevam
2017-10-19 21:52 ` Adam Ford
2017-10-19 22:44 ` Fabio Estevam
2017-10-20 2:18 ` Adam Ford
2017-10-20 11:41 ` Fabio Estevam
2017-10-24 22:38 ` Jagan Teki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171011184138.GO12015@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox