Hi All I am seeking some clarification and/or insights into the current state and future of BBB GPIO and device support.
It is my understanding that the Cape Manager will not be ported to kernels greater than 3.8. This, as far as I can tell, does not seem to be an official position rather it seems there is no momentum behind the Cape Manager in its current form and nobody who has the skills to do so is very keen on working on a port to future kernels. Is that a fair assessment? I have seen references to a sort of Generic Device Driver which will make it possible to configure the GPIO and muxed devices from user space kind of like a super sysfs. However, I can no longer find the name or the link. Does such a thing exist and if so, is it the likely way forward? I also have also seen references to a sort of generic .dbs file which contains a number of #includes people can comment and uncomment in order to enable specific cape functionality. Is this anything other than an idea at present and is this likely to be the way device tree support for capes is implemented going forward? What is currently thought to be the best practice to configure GPIO's and muxed devices for kernels with no cape manager? I am currently editing the Device Tree .dbs file manually. However, since the .dbs file is complicated and usually requires edits in multiple locations, this is not the easiest of configuration steps to communicate to users. I would appreciate any advice. In short, what is the current thinking and likely direction on the BBB GPIO and other device configuration? Any insights or comments to clarify where we are and where we are likely to go would be appreciated. -- 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.
