From: Roger Quadros <ext-roger.quadros@nokia.com>
To: ext Alexander Shishkin <virtuoso@slind.org>
Cc: ext Tony Lindgren <tony@atomide.com>,
"Gadiyar, Anand" <gadiyar@ti.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: linux-omap git tree updated to v2.6.32-rc1, important changes, please read
Date: Thu, 01 Oct 2009 11:06:26 +0300 [thread overview]
Message-ID: <4AC46302.20402@nokia.com> (raw)
In-Reply-To: <71a0d6ff0910010058m6f9f4fc0o70ef0d2020e170b3@mail.gmail.com>
ext Alexander Shishkin wrote:
> 2009/10/1 Roger Quadros <ext-roger.quadros@nokia.com>:
>> ext Tony Lindgren wrote:
>>> * Gadiyar, Anand <gadiyar@ti.com> [090930 10:05]:
>>>>>>>> Anyway, I haven't been able to make 2.6.31 boot on beagleboard, and
>>>>>>>> other people report similar issues:
>>>>>>>> http://www.spinics.net/lists/linux-omap/msg17968.html
>>>>>>>>
>>>>>>>> Have you got 2.6.32-rc1 (+fixes) to boot?
>>>>>>> Hmm, looks like it's musb again. This is what I get on my
>>>>>>> overo after applying the DEBUG_LL hack from omap-debug branch:
>>>>>> i've just sent a fix for this musb problem. patch is labelled "twl4030:
>>>>>> Fix
>>>>>> boot with twl4030 usb transceiver enabled"
>>>>> I can't quite locate it in linux-usb archives (or anywhere within
>>>>> google's reach). Could you sand it here or provide a link?
>>>>>
>>>> Here you go. Patchwork rocks!
>>>>
>>>> <http://patchwork.kernel.org/patch/50721/>
>>>>
>>> Great, thanks. Roger, please send your fix to Samuel for merging.
>>>
>>> Meanwhile, I'll apply it into fixes-testing while waiting for it
>>> to get to mainline via Samuel.
>>>
>>> Regards,
>>>
>>> Tony
>> OK Tony, I'll do that.
>
> It doesn't crash any more, but I fail to get it to work either:
> /sys/devices/platform/musb_hdrc/mode always says b_idle no matter what
> I do and the host never attempts to enumerate it (I have a g_ether
> statically compiled in for a gadget). Hints greatly appreciated.
>
> Regards,
> --
> Alex
Can you retry if it works without my patch and reverting commit
66760169492445395c530c812443f58e2cfdb3dc
cheers,
-roger
next prev parent reply other threads:[~2009-10-01 8:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 19:04 linux-omap git tree updated to v2.6.32-rc1, important changes, please read Tony Lindgren
2009-09-28 21:54 ` Kalle Valo
2009-09-29 14:36 ` green
2009-09-29 10:54 ` Shilimkar, Santosh
2009-09-30 17:55 ` Tony Lindgren
2009-10-01 4:04 ` Shilimkar, Santosh
2009-09-29 17:24 ` Felipe Contreras
2009-09-29 18:26 ` Tony Lindgren
2009-09-29 19:20 ` Alexander Shishkin
2009-09-29 19:26 ` Aguirre Rodriguez, Sergio Alberto
2009-09-29 19:42 ` Alexander Shishkin
2009-09-29 19:30 ` Tony Lindgren
2009-09-29 19:41 ` Alexander Shishkin
2009-09-30 15:53 ` Roger Quadros
2009-09-30 17:02 ` Alexander Shishkin
2009-09-30 17:04 ` Gadiyar, Anand
2009-09-30 17:31 ` Tony Lindgren
2009-10-01 7:30 ` Roger Quadros
2009-10-01 7:58 ` Alexander Shishkin
2009-10-01 8:06 ` Roger Quadros [this message]
2009-10-01 8:30 ` Roger Quadros
2009-10-01 8:31 ` Roger Quadros
2009-10-01 7:58 ` Roger Quadros
2009-09-30 14:07 ` Kevin Hilman
2009-09-30 17:25 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AC46302.20402@nokia.com \
--to=ext-roger.quadros@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=virtuoso@slind.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox