Hi Simon,
On Thu, Sep 7, 2023 at 3:08 PM Simon Glass <s...@chromium.org> wrote:
> On Wed, 6 Sept 2023 at 23:20, Ilias Apalodimas
> >
> > > > I beg to differ. Devicetree is more than just hardware and always has
> > > > been. See, for example the /chosen and /options nodes.
> > >
> > > There are exceptions...
> > >
> >
> > We've been this over and over again and frankly it gets a bit annoying.
> > It's called *DEVICE* tree for a reason. As Rob pointed out there are
> > exceptions, but those made a lot of sense. Having arbitrary internal ABI
> > stuff of various projects in the schema just defeats the definition of a
> > spec.
>
> Our efforts should not just be about internal ABI, but working to
> provide a consistent configuration system for all firmware elements.
>
Sure, programmatically we can pass any data/info via DT, however it is
only meant to map hardware features onto data structures.
devicetree.org landing page
"The devicetree is a data structure for describing hardware."
devicetree-specification-v0.3.pdf Chapter-2 Line-1
"DTSpec specifies a construct called a devicetree to describe
system hardware."
If we want to digress from the spec, we need the majority of
developers to switch sides :) which is unlikely to happen and rightly
so, imho.
regards.
