I'm building a kernel that can run on a handful of hardware
configurations, all using OF-unaware U-Boot. I know how to make a
static device tree (dts file) that works on one of these hardware
variations, and how to add nodes and modify properties in the platform
init code. But I don't see a nice way to deal with nodes that should be
present on only some hardware configurations.
I could have the dts file contain only the common elements, and add all
the variable elements in the startup code. But that means the bulk of
the device tree will be expressed as relatively ugly C source instead of
the much more readable and maintainable dts notation. I would much
rather have the dts file contain the union of all platforms and have the
platform init code delete the nodes that are not applicable, but I don't
see an API to do those deletions.
I suppose I could instead compile N different dts files and have the
platform init code pick the appropriate dtb blob to pass to fdt_init().
Any suggestions for the best way to do this?
-=] Mike [=-
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
