From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] testing x86 builds on the fly
Date: Sun, 07 Aug 2011 20:21:21 +1000 [thread overview]
Message-ID: <4E3E6721.1020002@gmail.com> (raw)
In-Reply-To: <4E3DE248.5030408@gmail.com>
Hi Mike, Marek,
On 07/08/11 10:54, Graeme Russ wrote:
> Hi Mike, Marek,
>
> On 07/08/11 09:43, Mike Frysinger wrote:
>> On Sat, Aug 6, 2011 at 05:49, Marek Vasut wrote:
>>> On Saturday, August 06, 2011 01:22:38 PM Mike Frysinger wrote:
>>>> disclaimer: i have like 0 u-boot experience on x86. but i cant find
>>>> README's in the src to answer my questions.
>>>>
>>>> the PIC support on x86 is finished right ? so does that mean we can
>>>> take a u-boot.bin, tftp it to a running system into external memory,
>>>> and then boot that on the fly purely for testing purposes ?
A little more explanation...
I did once have full PIC support for x86 when loaded with SDRAM already
initialised - It would figure out were it was loaded in relation to
TEXT_BASE and perform the required adjustments during the relocation
phase). But this functionality was removed when the Cache-As-RAM
implementation was introduced.
[snip]
> Now it would be fairly trivial to add a parameter passed by the 'go'
> command which sets a flag in global data that would tell board_init_f to
> not perform SDRAM init which is on my todo list (see below)
Well I just looked at the code and the warm reset entry point sets
GD_FLG_WARM_BOOT in gd->flags so you could easily bypass SDRAM
initialisation by doing a test in the arch specific dram_init_f()
int dram_init_f(void)
{
if (gd->flags | GD_FLG_WARM_BOOT)
return 0;
...
}
Regards,
Graeme
prev parent reply other threads:[~2011-08-07 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 11:22 [U-Boot] testing x86 builds on the fly Mike Frysinger
2011-08-06 12:49 ` Marek Vasut
2011-08-06 23:43 ` Mike Frysinger
2011-08-07 0:54 ` Graeme Russ
2011-08-07 10:21 ` Graeme Russ [this message]
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=4E3E6721.1020002@gmail.com \
--to=graeme.russ@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.