Re: Booting 2.6.25 on the OMAP5912OSK

2008-06-03 Thread Steve Poulsen
I too am seeing this same problem. Do you know when this was introduced (kernel version)? I am looking to update the kernel to address some flashing issues, and this is the only issue that remains for me. I am thinking to revert back to the I2C of the version that should fix this issue.

Re: Booting 2.6.25 on the OMAP5912OSK

2008-06-03 Thread Tony Lindgren
* Steve Poulsen [EMAIL PROTECTED] [080603 07:55]: I too am seeing this same problem. Do you know when this was introduced (kernel version)? I am looking to update the kernel to address some flashing issues, and this is the only issue that remains for me. I am thinking to revert back

Re: Booting 2.6.25 on the OMAP5912OSK

2008-06-03 Thread Felipe Balbi
On Tue, Jun 03, 2008 at 09:49:27AM -0700, Tony Lindgren wrote: Hmm, yeah sounds like something is broken.. Anybody want to try to narrow it down with git-bisect? ok, there's an easy way to reproduce. echo host /sys/devices/platform/musb_hdrc/mode from 3430sdp. Some of the transfers in

Booting 2.6.25 on the OMAP5912OSK

2008-06-01 Thread Philip Balister
I'm trying to update the Angstrom distribution to kernel version 2.6.25. The basic defconfig boots and runs, but when I turn on the vm file system for udev, the system hangs sometime after mounting root. While hung, it very slowly prints the following messages: i2c_omap i2c_omap.1: Transmit

Re: Booting 2.6.25 on the OMAP5912OSK

2008-06-01 Thread Felipe Balbi
Hi, On Sun, 01 Jun 2008 13:06:03 -0400, Philip Balister [EMAIL PROTECTED] wrote: i2c_omap i2c_omap.1: Transmit overflow tps65010: power off button Sounds like a bug in our i2c-omap.c Tony do you know about any issues with i2c-omap.c after highspeed i2c was introduced ? This could be a

Re: Booting 2.6.25 on the OMAP5912OSK

2008-06-01 Thread Felipe Balbi
Hi, On Sun, 01 Jun 2008 13:06:03 -0400, Philip Balister [EMAIL PROTECTED] wrote: i2c_omap i2c_omap.1: Transmit overflow tps65010: power off button Sounds like a bug in our i2c-omap.c Tony do you know about any issues with i2c-omap.c after highspeed i2c was introduced ? This could be a