Proposal: new device-tree syntax and semantics for extendinginformation from included dts files

[Stephen Neuendorffer]

> -----Original Message-----
> From: David Gibson [mailto:david at gibson.dropbear.id.au]
> Sent: Wednesday, October 13, 2010 5:46 PM
> To: Stephen Neuendorffer
> Cc: grant.likely at secretlab.ca; John Bonesio;
devicetree-discuss at lists.ozlabs.org
> Subject: Re: Proposal: new device-tree syntax and semantics for
extendinginformation from included dts
> files
> 
> On Wed, Oct 13, 2010 at 04:41:59PM -0700, Stephen Neuendorffer wrote:
> [snip]
> > > I'm not thrilled with the example because it still shows the empty
> > > braces which could be construed as the node still being present.
How
> > > about this syntax instead:
> > > 	serial at 2800 /remove-node/;
> > >
> > > I also wonder if it would be better to have the directives before
the
> > > node name.  ie:
> > > 	/extend/ node1 { ... };
> > > 	/replace/ node1 { ... };
> > > 	/remove/ node1;
> >
> > Or better yet, outside of the braces?
> >
> > 		/ {
> > 		soc: soc5200 at f0000000 {
> > 				#address-cells = <1>;
> > 				#size-cells = <1>;
> >  				compatible = "fsl,mpc5200b-immr";
> >  				...
> >
> >  				serial at 2600 {		// PSC4
> >  					compatible =
> > "fsl,mpc5200b-psc-uart","fsl,mpc5200-psc-uart";
> > 					reg = <0x2600 0x100>;
> > 					interrupts = <2 11 0>;
> >  				};
> >
> > 				serial at 2800 {		// PSC5
> >  					compatible =
> > "fsl,mpc5200b-psc-uart","fsl,mpc5200-psc-uart";
> >  					reg = <0x2800 0x100>;
> >  					interrupts = <2 12 0>;
> >  				};
> >             };
> >             /remove/ {
> >  				serial at 2600 { };		// PSC4
> >
> >  				serial at 2800 { };		// PSC5
> >  		};
> 
> Um.. no.  That makes even less sense in the conceptual framework of a
> stack of overlays.

Why exactly?  Instead of being a stack of overlays, it seems to me like
a stack of trees with operators..
The point is exactly that operators make most sense at the stack of
trees level and not
at the individual node level.

Steve

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.