mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andreas Schmidt <list@schmidt-andreas.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] blspec: add checking of optional key machine-id
Date: Thu, 3 May 2018 17:31:33 +0200	[thread overview]
Message-ID: <2ecb2475-07fa-8036-f94d-39e93c90aaad@schmidt-andreas.de> (raw)
In-Reply-To: <1525340087.17782.32.camel@pengutronix.de>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1680 bytes --]


On 03.05.2018 11:34, Jan Lübbe wrote:
[...]
>>> Then the existing selection logic would
>>> handle your case as well.
>> Ohh ... ok. And could you explain please, who we could do that? Because,
>> all our DTs are compatible with barebox DT and barebox would choose simple
>> the first one and boot it. Or is using of Bootloader Spec isn't right
>> way, to solve this issue?
> So in the barebox DT you'd have:
> / {
>         model = "Foo Common i.MX6 Board";
>         compatible = "foo,mx6-common", "fsl,imx6q";
> };
> [...]
>
> Then for the kernel DTs you can use different compatible lists, which
> each use a different and more specific entry.
>
> mx6-variant1.dts:
> / {
>         model = "Foo Variant 1 i.MX6 Board";
>         compatible =
> "foo,mx6-variant1", "foo,mx6-common", "fsl,imx6q";
> };
> [...]
>
> mx6-variant2.dts:
> / {
>         model = "Foo Variant 2 i.MX6 Board";
>         compatible = "foo,mx6-variant2", "foo,mx6-common", "fsl,imx6q";
> };
> [...]
>
> Then, in barebox, you need to have a way to override which compatible
> string the bootspec code is looking for.
Ok, the way is to override/extend barebox DT compatible string while
initialisation,
so barebox would be match only one boot entry.

> I'd prefer this to the machine-id approach, as the DT compatible list
> mechanism is designed exactly for handing these different levels of
> compatibility declarations.
Yes, I agree with you. That could be better for us to solve our issue.
Thank you for explanation!

Do your mean, for using the machine-id in right way, the patch could be
apply?
If Sascha still agree, of course.

Regards,
Andreas

[-- Attachment #1.1.1.2: 0xFEE0A611BEA6DEA0.asc --]
[-- Type: application/pgp-keys, Size: 3133 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2018-05-03 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 16:01 Andreas Schmidt
2018-05-02 11:02 ` Sascha Hauer
2018-05-02 13:23   ` [PATCH v2] " Andreas Schmidt
2018-05-08  6:13     ` Sascha Hauer
2018-05-02 14:32 ` [PATCH] " Jan Lübbe
2018-05-03  8:42   ` Andreas Schmidt
2018-05-03  9:34     ` Jan Lübbe
2018-05-03 15:31       ` Andreas Schmidt [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=2ecb2475-07fa-8036-f94d-39e93c90aaad@schmidt-andreas.de \
    --to=list@schmidt-andreas.de \
    --cc=barebox@lists.infradead.org \
    /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