From: Steve S. <sa...@gm...> - 2011-12-02 05:28:54
|
On Wed, Nov 30, 2011 at 8:07 PM, Steve Sakoman <sa...@gm...> wrote: > On Mon, Nov 21, 2011 at 7:40 AM, CoryS <cor...@ho...> wrote: >> >> Any luck with this? We are experiencing the same issue. > > I tested 10 recent date code COMs and found no issues with madc, so I > don't think it is a software issue (though that is always possible!) Well, it turns out that it was a software issue! There is a bug in the upstream madc driver in 2.6.39 and 3.0 that results in the madc channels 2 through 6 not being explicitly enabled! I've added a fix to my omap-3.0-pm repository: http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=commitdiff;h=8e69860734d81494e5b14b00fecb8b2af598ba32 If you want to use a pre-built GNOME or console image that contains the fix: http://sakoman.com/category/8-gnome-daily-builds-r13.html# Steve |