[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGngYiU_gDceVw9G7id6PmpdJt1iegoNVA3-ozkQzDFN9hUR5g@mail.gmail.com>
Date: Tue, 28 Apr 2020 08:20:42 -0400
From: Sven Van Asbroeck <thesven73@...il.com>
To: Frank Rowand <frowand.list@...il.com>
Cc: Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Q] devicetree overlays
Hello Frank, thank you for sharing your expertise. Much appreciated !
On Mon, Apr 27, 2020 at 4:26 PM Frank Rowand <frowand.list@...il.com> wrote:
>
> On 4/16/20 9:46 AM, Sven Van Asbroeck wrote:
> > My situation is this: I have hardware which consists of several modules.
> > Knowledge about the type and location of these modules is located in an
> > on-board eeprom.
> >
> > So now I need to assemble a devicetree, by puzzling various 'blobs' together.
> > This could be done in the bootloader,
>
> Do this, if at all reasonably possible.
>
> > - is there perhaps a more canonical / idiomatic way to solve this?
>
> Yes, apply the overlays before booting.
Powered by blists - more mailing lists