From: William Hermans <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, August 26, 2014 at 3:11 PM To: "[email protected]" <[email protected]> Subject: Re: [beagleboard] Re: Unifying cape overlays into boot .dtb for BeagleBoard.org boards
>> Didn't say that it doesn't work. It hasn't yet been added to our 3.14 tree >> which will require a backport. It looks like it should land upstream in 3.17 >> and we'll likely backport it from there. > > What I mean is this: Why doesn't the capemgr that is in 3.8.x work in 3.14.x > *right now* Why is it not a drop-in addition ? Obviously something is > different, but I am trying to understand why the kernel progresses in a manner > that breaks things in previous version, that are not all that old. That is because when Pantelis Antoniou worked for Circuitco, he developed cape manager, but his work was never accepted into mainline. When Pantelis left Circuitco, he wasn¹t available to merge his work into the newer kernels. However, over the last year, Pantelis did some nice work with some other very smart kernel developers and hopefully dynamic devicetree will be accepted into mainline V3.17. Regards, John > > > > On Tue, Aug 26, 2014 at 3:01 PM, Robert Nelson <[email protected]> > wrote: >> >> >> >> On Tue, Aug 26, 2014 at 4:50 PM, Jason Kridner <[email protected]> >> wrote: >>> On Tue, Aug 26, 2014 at 5:35 PM, William Hermans <[email protected]> wrote: >>>> Jason, >>>> >>>> What is so radically different that capemgr does not work ? >>> >>> Didn't say that it doesn't work. It hasn't yet been added to our 3.14 tree >>> which will require a backport. It looks like it should land upstream in 3.17 >>> and we'll likely backport it from there. >> >> 1 more step: >> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ae >> 36e95cf81c98b111b84317adeb358aaffa80e2 >> >> Group changes to the device tree. In preparation for adding device tree >> overlay support, OF_DYNAMIC is reworked so that a set of device tree changes >> can be prepared and applied to the tree all at once. OF_RECONFIG notifiers >> see the most significant change here so that users always get a consistent >> view of the tree. Notifiers generation is moved from before a change to >> after it, and notifiers for a group of changes are emitted after the entire >> block of changes have been applied >> >> Regards, >> >> -- >> Robert Nelson >> http://www.rcn-ee.com/ >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
