View Single Post
Posts: 58 | Thanked: 28 times | Joined on Nov 2010
#26
Originally Posted by woody14619 View Post
Well, the issue isn't an apps behavior as much as it is how the system behaves. In the case of filling the param buffer, if that happens on the N900 in the right circumstances the kernel driver goes into a spin. It eats 100% cpu, and doesn't respond to requests, requiring a reboot to restore. If I can prevent that by changing a system parameter, I'm all about trying it.

And yes, if a single app is causing it, that's one thing. But it's more and more looking like it's an interaction of 2 or 3 kernel drivers (for GSM, GL, and maybe GPS) causing this, not a single app. And since the replies from the only Nokia rep on the bug thread has said there's probably not going to ever be a fix for this from Nokia, even a small tweek like this is better than nothing.
Are you sure it's not the Texas Instruments TMS320 failure? Anyway fell free to ask any questions from TI.
OMAP3xxx GIT:http://git.kernel.org/?p=linux/kerne....git;a=summary
TI is already providing wide range of support for the beagleboard(i.e OMAP34xx too or OMAP35xx.) yes the proccessor seems to be different but if you see the original Beagleboard C2 you will see the specifications and the drivers source codes are the same.That means searching inside the beagleboard support and expansions will fix many of your problems.
http://elinux.org/Main_Page Linux for embedded
http://elinux.org/BeagleBoard#Revision_C2 BeagleBoard main page

Last edited by aligoodidea; 2010-12-23 at 10:23.
 

The Following User Says Thank You to aligoodidea For This Useful Post: