I've been working with Angstrom for beaglebone since late 2011 and have
been comfortably using the analog access through the sysfs API, but
since updating to V2012.12, it no longer works. I've Googled until my
fingers almost bleed (a slight exaggeration) looking for clues, but all
I can find is what appears to be motion toward inclusion of a
touch-panel system causing conflicts with the analog channel access.
I've seen a few questions by others about this, but no resolution nor
information as to how the problem can be resolved.
I've patched what appear to be the requisite files in arch/arm/boot/dts
(found mentioned occasionally) so that the tsdadc stuff is 'enabled' so
now the driver does get instantiated, but none of the channels appear
and I can't seem to find any way they *would* appear from perusing the
driver source. I'm no noob to linux (been hacking since 0.12 *way back
when*) so I do know my way around the kernel and I've written quite a
few drivers for my own purposes and some for custom user applications,
so I *generally* understand things even though the ARM stuff have moved
that in a significantly further direction than my current experience.
Some messages suggest there is (or will be) a char driver in 3.8 (the
current kernel is 3.8.2) but I find no evidence of that in the system,
as built, nor do I find any kernel configs to create it.
My confusion comes from not understanding motives of the development
process. Even when building a standard 'cloud9-gnome-image' version,
the ADC doesn't show up and yet it's part of the documented interfaces
provided by information from TI. Considering I may have missed
something, I'm hoping to find there is a simple configuration/patch step
I've missed or that "real soon now" the kernel will be re-updated to
include these missing features.
I could drop back to V2012.05, but I appreciate the fact that power
management works sufficiently for me to actually power down the device,
so I can abandon my patches that fixed that missing functionality. Lots
of progress has been made by this new release and moving to the Yocto
environment is a HUGE improvement (IMHO) so I don't want to 'go back.'
I made a stab at moving to V2013.06 but was met with numerous compile
issues, though I admit I may have pulled some incorrect updates (still
learning the git mechanics of this project.)
I don't want anyone to take this as a rant, even thought it probably
sounds like one. That tone comes only from not understanding the
motives of the developers and finding myself feeling stranded with
respect to status of this particular subsystem.
I've looked through the archives on this list and have found no mention
of this issue that I can use as a means of a solution.
Any additional help will be gratefully received.
Thanks,
Gary
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
