Re: Node name & property name collusion - json/yaml implications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Sat, Feb 6, 2021 at 1:26 AM David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Fri, Feb 05, 2021 at 06:57:54AM -0600, Kumar Gala wrote:
> > There’s an old thread about this from 2016:
> >
> > https://www.spinics.net/lists/devicetree-spec/msg00296.html
>
> That is not the only case of this - IIRC old Apple machine device
> trees had both an 'l2-cache' property and an 'l2-cache' node under
> each CPU node.

According to a dump I have, '/cpus/PowerPC,G4' has 'l2-cache' property
and '/cpus/PowerPC,G4/PowerPC,G4' node has a node name of 'l2-cache'.
So this would actually work with yaml if we brought back explicit
'name' properties. But this highlights we've already diverged from
OpenFirmware.

Specs evolve all the time deprecating old behavior. I don't see this
as any different. We can debate deprecating vs. outright changing the
spec. It's so rare, do we need to even bother deprecating it?

Rob




[Index of Archives]     [Device Tree]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Photos]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]

  Powered by Linux