[PATCH 06/17] Document the linux,network-index property.

[Segher Boessenkool]

>> Well it still needs to know property encoding...
>
> Well, yes, but in the most likely fixup cases that's trivial:
> clock-frequency properties are u32, memory address/size are u32 or
> u64, mac addresses are char[6].

Nit: what you call u64 actually is u32[2].  Alignment
matters sometimes.

>> It would be interesting to see if anyone actually uses this
>> feature ;-)
>
> Yes, it will.
>
> Oh, I have been planning for ages to make it possible (if less
> convenient) to use this with dtb as well as asm output, by
> (optionally) generating a "map file" (possibly in the form of a .h
> with #defines) alongside the dtb, giving the offsets of all the
> labels.

Sounds like overengineering to me but feel free to prove
me wrong :-)


Segher