Re: musb broken, was [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Sep 7, 2008 at 10:37 AM, David Brownell <david-b@xxxxxxxxxxx> wrote:
> On Sunday 07 September 2008, Måns Rullgård wrote:
>> I've also had to revert the "usb: musb: pass configuration specifics
>> via pdata" commits:
>>
>>   ffd60d49c70b31d26430a1098edf0eef5e4dfac8 in linux-omap
>>   ca6d1b1333bc2e61e37982de1f28d8604c232414 in mainline
>>
>> I suspect there are simply some tables missing for the Beagle board,
>> but I haven't a clue what should go in them.
>
> Odd, that's in the RC3 code and it works for me.

I don't need to revert those commits on Overo and it works "as well as
it ever has" which means that I get disconnects/reconnects of all
devices at random intervals.  I am using musb in host mode, whereas I
think Mans is in device/gadget mode.

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux