On Wed, Oct 13, 2010 at 07:40:36PM -0600, Grant Likely wrote:
> On Thu, Oct 14, 2010 at 11:38:33AM +1100, David Gibson wrote:
> > On Wed, Oct 13, 2010 at 05:17:47PM -0600, Grant Likely wrote:
> > > On Tue, Oct 12, 2010 at 02:56:01PM -0700, John Bonesio wrote:
> &some-node {
> property-to-remove /remove-prop/;
> property-to-replace = "new value";
> property-to-replace-with-empty-prop;
>
> node-to-remove /remove-node/;
> node-to-replace /remove-node/ { prop = "blah"; };
> };
>
> Or perhaps with the keyword preceding:
>
> &some-node {
> /remove-prop/ property-to-remove;
> property-to-replace = "new value";
> property-to-replace-with-empty-prop;
>
> /remove-node/ node-to-remove;
> /remove-node/ node-to-replace { prop = "blah"; };
> };
I should probably also mock-up what it would look like when the target
node is at the top level. With keyword after the node name:
/ {
...
};
&some-node-to-remove /remove-node/;
&some-node-to-replace /remove-node/ { prop = "blah"; };
And with keywords preceeding:
/ {
...
};
/remove-node/ &some-node-to-remove;
/remove-node/ &some-node-to-replace { prop = "blah"; };
g.
_______________________________________________
devicetree-discuss mailing list
[email protected]
https://lists.ozlabs.org/listinfo/devicetree-discuss
