On Monday 28 February 2005 12:04 pm, Danilo Halla wrote:
> > Odd.  Presumably earlier kernels worked for you; you should
> > find out when it stopped working.  It's possible some of the
> > recent updates for OSK stomped on Innovator or 1510 support.
>  
> I got the same results with 2.6.11-rc1-omap1 and an old release from
> http://www.celinuxforum.org based on kernel 2.4 (celinux-040503)

Well, if 2.6.9-omap1 doesn't work for you, then I'd guess maybe
your hardware is misbehaving.

Wait -- you do have CONFIG_OMAP_MUX so that the pins get set up
correctly, right?  As a rule, you want that on all developer
boards, since the boot loader (like U-Boot) doesn't set up
all the pins.  Production boards are expected to work a bit
differently, and there Linux saves some pages of flash by not
duplicating that setup.  But if you enable OMAP_MUX_WARNINGS,
you'll surely notice Linux needing to tweak some stuff.

When each pin on the SOC chip can serve up to eight different
roles, and with multiple modes for some of those roles, it's
extremely important for Linux board init code to set things up
when nobody else does!  Things just won't work otherwise, and
in 2.6 it's a goal to keep such stuff out of drivers.  It's a
bit more complex for USB than most other things ... :)

You might have better luck asking on the linux-omap list, where
there are more folk with those boards.  (And where you should
send any OMAP patches.)  But be sure OMAP_MUX is enabled first.

- Dave


> Could the USB initializing be the problem?
> 
> Thanks for your help.
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to