From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Selecting from multiple device trees at runtime
Date: Tue, 08 Jan 2013 10:37:13 -0700 [thread overview]
Message-ID: <50EC5949.7030708@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ3qgA0h1ongBRySU-FLujbSSK8RAEt6+HqoP1F5YrrYfw@mail.gmail.com>
On 01/08/2013 09:51 AM, Simon Glass wrote:
> Hi Stephen,
>
> On Tue, Jan 8, 2013 at 8:42 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 01/07/2013 08:16 PM, Simon Glass wrote:
>>> Hi,
>>>
>>> On Mon, Jan 7, 2013 at 2:21 PM, Curt Brune <curt@cumulusnetworks.com> wrote:
>>>>
>>>>
>>>> On 01/07/2013 12:12 PM, Wolfgang Denk wrote:
>>>>>
>>>>> Dear Curt Brune,
>>>>>
>>>>> In message <50EB0D92.2020707@cumulusnetworks.com> you wrote:
>>>>>>
>>>>>>
>>>>>> What I would love is to have a single multi-file uImage I could use on
>>>>>> all my platforms. The idea is to introduce a new image type that is a
>>>>>> list of device tree blobs.
>>>>>
>>>>>
>>>>> In addition to the file system based approach suggested by Stephen,
>>>>> you should have a look into using FIT images (see doc/uImage.FIT/ ).
>>>>> One of the reasons for creating these was to deal with situations
>>>>> exactly as you describe...
>>>>
>>>>
>>>> I think that will work perfectly. Thank you for the suggestion.
>>>
>>> Note also there is code in mainline now to select the correct FDT from
>>> a list of them in a FIT. based on the model name. Then it can pass
>>> this to the kernel. So if you have a way of getting the model name in
>>> U-Boot, it might just work.
>>
>> Hmmm. What's the model name compared against? U-Boot board name variable
>> would be nice!
>
> At the moment it compares against the model in the U-Boot FDT
> (CONFIG_OF_CONTROL). When flashing a board, you pack u-boot.bin with
> the selected .dtb file containing this model name. Then when U-Boot
> runs it knows what its model is.
>
> You could do what you describe, but it is then a compile-time check, I think.
>
> There could be other ways to decide on the model name, such as looking
> at strapping GPIOs, for example:
>
> static const char *detect_model(void)
> {
> if (gpio_get_value(36))
> return "snow";
> else
> return "flax";
> }
Right - I believe the TI guys introduced the board_name variable or
similar to indicate the runtime-detected board ID for this purpose
(whereas the board variable I introduced is the board U-Boot was
compiled for). It'd be nice to be able to select a DTB from FIT based on
$board_name instead of U-Boot's own DTB's model given all this. Do the
sub-images in the FIT image have filenames that could be selected as
e.g. ${soc}-${board}.dtb? Using $board or $board_name would also help
where U-Boot doesn't use a DT itself.
next prev parent reply other threads:[~2013-01-08 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:01 [U-Boot] Selecting from multiple device trees at runtime Curt Brune
2013-01-07 18:36 ` Stephen Warren
2013-01-07 19:44 ` Curt Brune
2013-01-07 20:12 ` Wolfgang Denk
2013-01-07 22:21 ` Curt Brune
2013-01-08 3:16 ` Simon Glass
2013-01-08 16:42 ` Stephen Warren
2013-01-08 16:51 ` Simon Glass
2013-01-08 17:37 ` Stephen Warren [this message]
2013-01-08 17:58 ` Simon Glass
2013-01-08 22:37 ` Stephen Warren
2013-01-08 22:47 ` Simon Glass
2013-01-09 1:40 ` Curt Brune
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=50EC5949.7030708@wwwdotorg.org \
--to=swarren@wwwdotorg.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