I do not remember why. There was an explanation some months ago as to why,
but the important question would be: "Will capemgr ever be in 3.14.x?"
Then, I'm pretty sure the answer would be "NO!"

Charles' universal io is enabled in the latest TI 3.14.x with pin
configuration available via sysfs. So there is an alternative. At least I
think, as I use 3.8.x in my own "production" images, but I have been
exploring the latest TI 3.14.x kernel available via APT. I can tell
universal io is there. config-pin is not( at least as far as I can tell -
sudo which config-pin returns nothing ).

Anyway, I have a bit more to explore yet, but if what I am reading will
work. Something like:

*# echo <some_value> > <some_file>* should configure the pins fine. So long
as they're available to use. Personally, I think this is great, Make it
really easy to configure pins on an app by app basis.

Anyway, get back to me in a few days, I'll possibly have a blog write-up on
it next month. After new years of course . . .

On Fri, Dec 12, 2014 at 1:53 AM, Karl Karpfen <[email protected]>
wrote:

> What is the reason the newer kernels do not have camepanager-support? Was
> it dropped out of current kernels for some strange reason or wasn't it
> never part of a "official" kernel release?
>
> Am Dienstag, 9. Dezember 2014 11:24:57 UTC+1 schrieb William Hermans:
>>
>> 3.14.x kernels do not have capemgr, and the element14 beaglebone blacks
>> come stock with 3.8.13-bone47 ( at least the 3 we ordered did ).
>>
>>
>
> --
> 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.

Reply via email to