Out of (kernel) tree device trees #62
Conversation
This bit of logic enables out of (kernel) tree device trees but still use the kernel build and oe support for device tree to compile it.
|
Do we really want to do this? it'll mean we need to synchronise poky with the kernel for every new device added. |
|
I think the vision is that we don't have any device trees in the kernel source. Or, they can be there, but they are just for you guys to develop against - similar to what we are doing with defconfigs. With that in mind is there still a sync needed? |
|
I'd disagree with that - the device tree is very tightly coupled with the kernel version (especially at the moment), and shouldn't affect things outside of the kernel. Kernel .configs are a little different in that regard, as they're providing features that OpenBMC requires, and not just items that the kernel requires. If we really do want to keep the device trees separate, we should do this once the drivers are all complete; it's just going to slow us down before that point. |
|
so what are we doing? i have an outstanding pull request in the kernel for this. Do I close that? |
|
Merging for now. We can revert if there is disagreement after discussion but we need to get the dev trees in now. |
Out of (kernel) tree device trees
|
@williamspatrick : why do we need the dev trees separate now? The dts files, as you merged them, were the same as the kernel's, no? |
mihawk: phosphor-gpu SRCREV bump f57188be82..dc27898de5
Add plumbing and initial device trees for Palmetto/Barreleye.
Bump kernel version.