On Tue, Aug 26, 2014 at 5:11 PM, William Hermans <[email protected]> wrote: >> 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.
The capemgr patch-set touched code in almost every kernel subsystem. If it worked that easily, we would have moved off v3.8.x long ago.. 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.
