From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Linux boot and list loading feature
Date: Mon, 01 Aug 2011 16:13:12 +0200 [thread overview]
Message-ID: <4E36B478.7080403@gmail.com> (raw)
In-Reply-To: <4E36A28A.70904@ti.com>
Hi Aneesh,
On 08/01/2011 02:56 PM, Aneesh V wrote:
> Hi Simon,
>
> On Monday 01 August 2011 04:50 PM, Simon Schwarz wrote:
>> Hi Aneesh,
>>
>> I am working on the OS booting right now and have a bigger change of
>> your code in spl.c in mind.
>>
>> Hope you can say one or two words what you think about it.
>>
>> THE PROBLEM
>> For the direct OS boot and in some other situations - env image e.g., I
>> have to load more than one image in SPL.
>>
>> This can be done by hardcoding these cases and use #ifdef or ifs to
>> switch between them. Or I can implement a general image loading with
>> lists.
>> (This was discussed here:
>> http://article.gmane.org/gmane.comp.boot-loaders.u-boot/102345)
>
> At the outset, wonder why we can not use the default bootargs string in
> the kernel image instead of passing it from the bootloader. For direct
> kernel boot from SPL, that looks like the best option for me. Then we
> will not need all this. Am I missing something?
>
From the documentation it is mandatory for ARM to pass ATAGS (or FDT I
assume): http://www.arm.linux.org.uk/developer/booting.php
So I think your solution would work - but IMHO would be too simple.
The beauty is that we can save the config of ATAGS/FDT directly in
u-boot and pass this image at the next boot to the SPL. This means we
can boot the exact same configuration with the SPL as with standard
u-boot - without recompiling the kernel. Trade-off: a more complex SPL.
> best regards,
> Aneesh
Regards
Simon
next prev parent reply other threads:[~2011-08-01 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 11:20 [U-Boot] Linux boot and list loading feature Simon Schwarz
2011-08-01 12:56 ` Aneesh V
2011-08-01 14:13 ` Simon Schwarz [this message]
2011-08-02 12:41 ` Aneesh V
2011-08-02 13:03 ` Heiko Schocher
2011-08-02 13:45 ` Wolfgang Denk
2011-08-09 13:45 ` Simon Schwarz
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=4E36B478.7080403@gmail.com \
--to=simonschwarzcor@googlemail.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.