From: David Brownell <david-b@pacbell.net>
To: Nathan Monson <nmonson@gmail.com>
Cc: Steve Sakoman <sakoman@gmail.com>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: Current git head oops'es at boot on Overo
Date: Mon, 6 Oct 2008 14:39:19 -0700 [thread overview]
Message-ID: <200810061439.19486.david-b@pacbell.net> (raw)
In-Reply-To: <e5e6ade50810061415k60d77010x8f46be8835b6830d@mail.gmail.com>
On Monday 06 October 2008, Nathan Monson wrote:
> I'm set up as host, using a BeagleBoard, and with the current
> linux-omap git I can get USB working by unplugging and replugging the
> A side of the cable (at the mini-AB connector on the BeagleBoard).
>
> Just disconnecting the cable at the B side is not enough. It must
> have something to do with the ID pin. So, if you have a soldered ID
> pin it wouldn't work either.
Right. That's a bug in the transciever support, note ... on
host side there are TWO relevant cable events: ID pin grounded,
and D+/D- rising. It only understands the former for now, and
doesn't check for the state very well unless poked by an IRQ.
(All that can be a PITA to get right. It helps to have a cable
tester that will let you do things like switch the ID ground,
apply a variable VBUS load, apply D+/D- pullups/pulldowns,
and so on.)
> Also, my cable is going into a powered 4 port high speed hub. That
> might make a difference.
That's what I was doing too. It's a common setup ... just a
bit easier to preconfigure networking that way than through
a bridgede configuration.
- Dave
next prev parent reply other threads:[~2008-10-06 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:26 Current git head oops'es at boot on Overo Steve Sakoman
2008-10-06 19:53 ` David Brownell
2008-10-06 21:04 ` Steve Sakoman
2008-10-06 21:15 ` Nathan Monson
2008-10-06 21:39 ` David Brownell [this message]
2008-10-06 21:57 ` Steve Sakoman
2008-10-06 21:34 ` David Brownell
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=200810061439.19486.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=nmonson@gmail.com \
--cc=sakoman@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