From: Michael Trimarchi <michael@panicking.kicks-ass.org>
To: Andreas Hartmetz <ahartmetz@gmail.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: USB lockup on OMAP3530
Date: Sun, 14 Feb 2010 12:44:01 +0100 [thread overview]
Message-ID: <4B77E201.3010904@panicking.kicks-ass.org> (raw)
In-Reply-To: <f3642e6b1002131249y2af6704bk13875ab575c28e62@mail.gmail.com>
Hi
Andreas Hartmetz wrote:
> On Thu, Feb 11, 2010 at 7:57 PM, Michael Trimarchi
> <michael@panicking.kicks-ass.org> wrote:
>> Use an hub with external power and connect the hub to the OTG and the device
>> to the HUB.
>> Is it the same?
>>
> Uhm... what do you think how I attached a hard disk and a network
> device to the Beagle's USB OTG port (ONE port) that can only supply
> 100 mA?
> Of course I have everything connected to a powered hub that is
> connected to the OTG port.
> Note that my bug report is not about USB devices not working at all.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Sorry for that :), I haven't read all the message. But I had the same problem
using a camera with isoc transfer. BTW, I have the two patches applied and that
one from openembeeded doens't work.
Michael
prev parent reply other threads:[~2010-02-14 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 22:30 USB lockup on OMAP3530 Andreas Hartmetz
2010-01-26 23:13 ` Robert Nelson
2010-01-27 19:46 ` Andreas Hartmetz
2010-02-10 12:40 ` Gadiyar, Anand
2010-02-11 18:57 ` Michael Trimarchi
2010-02-13 20:49 ` Andreas Hartmetz
2010-02-14 11:44 ` Michael Trimarchi [this message]
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=4B77E201.3010904@panicking.kicks-ass.org \
--to=michael@panicking.kicks-ass.org \
--cc=ahartmetz@gmail.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
/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