Hallo Jan,


On 02.05.2018 16:32, Jan Lübbe wrote:
> On Sun, 2018-04-29 at 18:01 +0200, Andreas Schmidt wrote:
>> I guess, for such an use case Bootloader Spec specify "machine-id"
>> key. This patch implement the support for machine-id key.
> The way I read https://www.freedesktop.org/wiki/Specifications/BootLoad
> erSpec/ is that the "machine-id" field should contain the ID from
> /etc/machine-id, which is basically a UUID:
> "machine-id shall contain the machine ID of the OS /etc/machine-id.
> This is useful for boot loaders and applications to filter out boot
> entries, for example to show only a single newest kernel per OS, or to
> group items by OS, or to maybe filter out the currently booted OS in
> UIs that want to show only other installed operating systems."

I read this part in same way. I think, the patch isn't in conflict with
that. And, yes, you're right we would use it not exact in this way.

Out /etc/machine-id is building dynamically and would be the same as barebox
choose one. (Same way to set global.boot.machine_id and content of
/etc/machine-id)
But, all our FW would have different machine-id in dependent of devices
and not on
OS.

The spec says: "for example to show only ...". So I guess, it is not
hard requirement.
Was I'm wrong?

> Your use-case sound like you'd need a way to add a more specific DT
> board compatible at runtime. 

We need a decision witch DT has to be load at runtime. But they are all
compatible with the barebox DT. We have only one barebox DT for all devices.

> 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?

Regards,
Andreas