Re: New problem with BeagleBoard

2010-11-23 Thread Ira Rosen
On 22 November 2010 21:07, Michael Hudson michael.hud...@canonical.com wrote: On Mon, 22 Nov 2010 15:09:29 +0200, Ira Rosen ira.ro...@linaro.org wrote: On 22 November 2010 15:02, Anand Gadiyar anand.gadi...@linaro.org wrote: If it's the XM (as your bootloader claims), then there is no

Re: Issues with ondemand governor

2010-11-23 Thread Amit Kucheria
Vishwa, Have you had a chance to do some usetime tests with these changes? It would be interesting to measure the power consumption with and without these changes. /Amit On Tue, Nov 23, 2010 at 5:59 PM, Vishwanath Sripathy vishwanath.sripa...@linaro.org wrote: Thanks David for the inputs. I

Re: omap4 panda ehci failure

2010-11-23 Thread Anand Gadiyar
On 23 November 2010 11:38, John Rigby john.ri...@linaro.org wrote: All omap4 experts, I have a packaged kernel for omap3/omap4 that boots to a shell prompt on a Panda and a Beagle XM. One problem on Panda is that I have not network. When I looked at the dmesg I noticed that the ehci driver

Re: omap4 panda ehci failure

2010-11-23 Thread John Rigby
Anand, Thanks for the info. On Tue, Nov 23, 2010 at 9:12 AM, Anand Gadiyar anand.gadi...@linaro.org wrote: On 23 November 2010 11:38, John Rigby john.ri...@linaro.org wrote: All omap4 experts, I have a packaged kernel for omap3/omap4 that boots to a shell prompt on a Panda and a Beagle XM.

Re: omap4 panda ehci failure

2010-11-23 Thread Anand Gadiyar
On 23 November 2010 21:42, Anand Gadiyar anand.gadi...@linaro.org wrote: On 23 November 2010 11:38, John Rigby john.ri...@linaro.org wrote: All omap4 experts, I have a packaged kernel for omap3/omap4 that boots to a shell prompt on a Panda and a Beagle XM. One problem on Panda is that I

Re: omap4 panda ehci failure

2010-11-23 Thread Anand Gadiyar
On 23 November 2010 22:17, John Rigby john.ri...@linaro.org wrote: On Tue, Nov 23, 2010 at 9:12 AM, Anand Gadiyar anand.gadi...@linaro.org wrote: On 23 November 2010 11:38, John Rigby john.ri...@linaro.org wrote: I'll see if I can rebase against linux-linaro-2.6.36 and send a pull

Re: omap4 panda ehci failure

2010-11-23 Thread Nicolas Pitre
On Tue, 23 Nov 2010, John Rigby wrote: On Tue, Nov 23, 2010 at 9:12 AM, Anand Gadiyar anand.gadi...@linaro.org wrote: Do I need to post the patches here for review first? Or is it sufficient to point to a git branch for people to take a look? That is a question of Nicolas. I think the

Re: omap4 panda ehci failure

2010-11-23 Thread Nicolas Pitre
On Tue, 23 Nov 2010, Anand Gadiyar wrote: Okay - I haven't received any review comments yet - but that could be because most people are out due to holidays this week. Either that, or there is nothing blatently controvertial about those patches. I'll wait until they're queued up in the

Re: omap4 panda ehci failure

2010-11-23 Thread Nicolas Pitre
On Tue, 23 Nov 2010, Anand Gadiyar wrote: I just checked - the patches I posted apply cleanly against linux-linaro-2.6.36. Patch 3 has some line offsets, but otherwise applies cleanly. EHCI works on Panda after applying these patches, however I didn't get a chance to check if EHCI on OMAP3

Re: omap4 panda ehci failure

2010-11-23 Thread John Rigby
On Tue, Nov 23, 2010 at 11:31 AM, Nicolas Pitre nicolas.pi...@linaro.org wrote: On Tue, 23 Nov 2010, Anand Gadiyar wrote: I just checked - the patches I posted apply cleanly against linux-linaro-2.6.36. Patch 3 has some line offsets, but otherwise applies cleanly. EHCI works on Panda after

Minutes actions: Kernel Working Group meeting of Nov 22, 2010

2010-11-23 Thread Mounir Bsaibes
Greetings, Enclosed you'll find a link to the agenda, minutes and actions from the Linaro kernel working group weekly meeting of November 22nd, 2010. https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Meetings/2010-11-22 Regards, Mounir

[RFC] thermal sensor drivers under drivers/hwmon

2010-11-23 Thread Yong Shen
Hi there, In power management group, we have a working item of exposing thermal information to user space through sysfs. However, so far, the thermal sensor drivers under 'drivers/hwmon' expose their information in various nodes under sysfs, which makes information collection difficult. Intel's