On 2/17/2014 10:05 AM, Jason Cooper wrote: > All, > > At last weeks devicetree irc meeting, I took on the task of writing this > email. I'm a bit behind. > > One of the outcomes of the ARM/devicetree discussion at the 2013 Kernel > Summit was that we were going to hold off on separating the devicetree > from the Linux kernel tree. The primary reason for this was to get > through the backlog of patches. > > It's been several months, and we're seeing evidence of other projects > having difficulty keeping in sync with the kernel tree. Specifically, > barebox is having trouble syncing: > > http://list-archives.org/2014/02/07/barebox-lists-infradead-org/devicetree-maintenance-in-barebox/f/5820726136 < snip > Sascha, (Directing this to you, because the devicetree-maintenance-in-barebox thread begins with an email from you.) I have read through the referenced thread, but do not yet understand the cause of the issues the barebox project is facing. What I got from the thread is that the barebox project maintains some devicetree changes in the project repository, and it is difficult to manage these changes as the upstream project (the Linux kernel) makes changes. What are the barebox changes to dts files? Why are the changes not submitted upstream? (Or if they were submitted, why were they not accepted?) I'm not sure what else to ask to try to understand the issues for barebox. Is there anything else you can say to help me understand? How would moving the devicetree files to another repository (also external to the barebox project) resolve the issues for the barebox project? Thanks, -Frank -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
