Re: [Power.org:parch] ePAPR 1.1 to do list

[Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>]

On Mon, 30 Aug 2010 14:34:44 -0700
Yoder Stuart-B08248 <B08248-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:

> I've consolidated what I am aware of with respect to errors found in
> 1.0,
> clarifications needed, and new mechanisms to go into ePAPR 1.1 into
> a single list.
> 
> Let me know if you are aware of anything else.

2.2.1.1 should perhaps have a stronger connection between unit addresses
and reg -- if you don't have the latter, you can't have the former.
This is required for bindings to work on real Open Firmware.  David
Gibson just posted a patch to dtc yesterday that verifies this.

Disambiguation without reg can still be achieved by appending numbers
to the node names, without @.

One use case to consider is nodes that have no reg, but do have
ranges, such as the somewhat misnamed "soc" nodes.  The unit address
mechanism has similar advantages here as with reg (a standardized way
to disambiguate based on child-bus address, and ability to omit the unit
address to get the first one).  We could make the rule be "first reg
address, if no reg then first ranges child-bus address, if no reg or
ranges then no unit address".

Such unit addresses may not work on true OF as is, but bindings should
not require the use of unit addresses -- and if people using real OF
find them useful, it doesn't seem like it would be unreasonable to
modify OF to support ranges-based unit addresses in the absence of reg.

-Scott