Browse Source
When applying overlays, we merge symbols from the overlay into the target tree. At the moment the logic for this assumes all symbols in the overlay are attached to a node of the form: /fragment@XXX/__overlay__/relative/path And will end up applied to the relative/path node under the fragment's target. However, this disallows the case of a symbol in the form just: /fragment@XXX/__overlay__ This does have a pretty obvious sensible meaning: attach the new symbol directly to the fragment's target, but we don't currently do that. It's pretty easy to workaround this limitation in one's overlays, but it's also easy to handle in the overlay applying code, so we might as well extend it to cover this case. Reported-by: Christophe Braillon Signed-off-by: David Gibson <david@gibson.dropbear.id.au>main
David Gibson
5 years ago
4 changed files with 42 additions and 6 deletions
@ -0,0 +1,13 @@ |
|||||||
|
/dts-v1/; |
||||||
|
/plugin/; |
||||||
|
/ { |
||||||
|
fragment@1 { |
||||||
|
target-path = "/foonode"; |
||||||
|
foo: __overlay__ { |
||||||
|
overlay-1-property; |
||||||
|
bar: barnode { |
||||||
|
bar-property = "bar"; |
||||||
|
}; |
||||||
|
}; |
||||||
|
}; |
||||||
|
}; |
Loading…
Reference in new issue