Hi Caleb,
On Wed, 29 May 2024 at 15:55, Caleb Connolly wrote:
>
>
>
> On 29/05/2024 21:49, Simon Glass wrote:
> > Hi Caleb,
> >
> > On Wed, 29 May 2024 at 13:04, Caleb Connolly
> > wrote:
> >>
> >>
> >>>
> >>> How about using the compatible string, instead of a GUID? Is that
> >>> possible?
>
On 29/05/2024 21:49, Simon Glass wrote:
Hi Caleb,
On Wed, 29 May 2024 at 13:04, Caleb Connolly wrote:
How about using the compatible string, instead of a GUID? Is that possible?
Could you elaborate?
Well, the compatible string (in the root node) is how we normally
decide which DT
Hi Caleb,
On Wed, 29 May 2024 at 13:04, Caleb Connolly wrote:
>
>
> >
> > How about using the compatible string, instead of a GUID? Is that possible?
>
> Could you elaborate?
Well, the compatible string (in the root node) is how we normally
decide which DT to use and which machine we are
How about using the compatible string, instead of a GUID? Is that possible?
Could you elaborate?
Regards,
Simon
--
// Caleb (they/them)
Hi Caleb,
On Wed, 29 May 2024 at 08:49, Caleb Connolly wrote:
>
> As more boards adopt support for the EFI CapsuleUpdate mechanism, there
> is a growing issue of being able to target updates to them properly. The
> current mechanism of hardcoding UUIDs for each board at compile time is
>
As more boards adopt support for the EFI CapsuleUpdate mechanism, there
is a growing issue of being able to target updates to them properly. The
current mechanism of hardcoding UUIDs for each board at compile time is
unsustainable, and maintaining lists of GUIDs is similarly cumbersome.
In this
6 matches
Mail list logo
