From: Tom Rini <trini@konsulko.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: u-boot@lists.denx.de
Subject: Re: Broken commit d433c74eecdce1e4952ef4e8c712a9289c0dfcc2
Date: Thu, 22 Dec 2022 19:36:58 -0500 [thread overview]
Message-ID: <20221223003658.GP3787616@bill-the-cat> (raw)
In-Reply-To: <20221222210242.opzl5qmregv6atyx@pali>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Thu, Dec 22, 2022 at 10:02:42PM +0100, Pali Rohár wrote:
> On Thursday 22 December 2022 13:22:50 Tom Rini wrote:
> > I suspect that how we fire up QEMU means that the issue you're
> > noting isn't triggered since we don't boot it from flash but instead
> > pass the binary.
>
> Yes, this sounds like that problematic part is not tested. To spot this
> issue some end-to-end test is needed... For flash setup - booting
> directly from the qemu flash (execute in place) without initialized RAM
> and letting u-boot to do it. For SD card setup - booting via BootROM
> (like it is on the real HW). Seems that SD card BootROM is not available
> on internet and no idea if it can be dumped from some Freescale CPU (it
> is even legal to do it?). So some alternative bootrom implementation for
> such testing is needed... which is lot of work.
We do some things like this already, for other QEMU platforms (the
flash_impl variable is set to the shell script to create a flash image)
but, it's unlikely to be worth expending the effort here, the ROM QEMU
uses here isn't the Freescale one, but from openhackware.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-12-23 0:37 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 9:13 Broken commit de47ff536363289f92f85ed1e4901724d238432d Pali Rohár
2022-08-02 10:58 ` Tom Rini
2022-08-03 16:00 ` Pali Rohár
2022-08-03 16:13 ` Tom Rini
2022-08-05 14:21 ` Pali Rohár
2022-08-05 14:47 ` Tom Rini
2022-08-05 14:59 ` Pali Rohár
2022-08-05 15:03 ` Tom Rini
2022-08-05 15:12 ` Pali Rohár
2022-08-05 15:44 ` Tom Rini
2022-08-05 15:51 ` Pali Rohár
2022-08-05 15:54 ` Tom Rini
2022-08-05 20:17 ` Pali Rohár
2022-08-05 22:20 ` Tom Rini
2022-08-08 7:51 ` Marek Behún
2022-08-08 13:37 ` Tom Rini
2022-08-17 9:29 ` Pali Rohár
2022-08-26 14:53 ` Tom Rini
2022-10-09 12:41 ` Pali Rohár
2022-10-09 12:45 ` Tom Rini
2022-10-09 13:10 ` Pali Rohár
2022-10-09 16:32 ` Tom Rini
2022-10-10 12:20 ` Marek Behún
2022-11-01 23:14 ` Pali Rohár
2022-11-21 17:56 ` Pali Rohár
2022-12-16 18:01 ` Pali Rohár
2022-12-16 19:24 ` Marek Behún
2022-12-16 21:56 ` Broken commit d433c74eecdce1e4952ef4e8c712a9289c0dfcc2 Pali Rohár
2022-12-22 2:54 ` Tom Rini
2022-12-22 7:49 ` Pali Rohár
2022-12-22 14:29 ` Tom Rini
2022-12-22 17:13 ` Pali Rohár
2022-12-22 17:33 ` Tom Rini
2022-12-22 17:56 ` Pali Rohár
2022-12-22 18:22 ` Tom Rini
2022-12-22 21:02 ` Pali Rohár
2022-12-23 0:36 ` Tom Rini [this message]
2022-12-25 10:42 ` Freescale P2020 Internal Boot ROM Pali Rohár
2022-12-23 19:10 ` Broken commit d433c74eecdce1e4952ef4e8c712a9289c0dfcc2 Pali Rohár
2022-12-23 19:18 ` Tom Rini
2022-12-23 21:39 ` Pali Rohár
2022-12-23 22:34 ` Pali Rohár
2022-12-24 16:13 ` Tom Rini
2022-12-24 17:03 ` Pali Rohár
2022-12-28 14:45 ` Pali Rohár
2022-12-23 21:56 ` Pali Rohár
2022-12-22 17:36 ` Simon Glass
2022-12-28 16:50 ` Broken commit de47ff536363289f92f85ed1e4901724d238432d Pali Rohár
2022-12-28 17:13 ` Tom Rini
2022-12-28 17:50 ` Broken socrates board (Was: Re: Broken commit de47ff536363289f92f85ed1e4901724d238432d) Pali Rohár
2022-12-29 22:38 ` Simon Glass
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=20221223003658.GP3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=pali@kernel.org \
--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