From: Jarkko Nikula <jhnikula@gmail.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: Gary Thomas <gary@mlbassoc.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: MUSB Host problems
Date: Wed, 10 Jun 2009 08:12:48 +0300 [thread overview]
Message-ID: <20090610081248.417f5d98.jhnikula@gmail.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F52BB72D@dbde02.ent.ti.com>
On Wed, 10 Jun 2009 07:55:17 +0530
"Pandita, Vikram" <vikram.pandita@ti.com> wrote:
> >>> similar to the Beagle). When I startup, I get this message:
> >>> Clock usbhost_48m_fck didn't enable in 100000 tries
> >>
> >> This is bad
> >
> >Why? What does it mean? How do I fix it?
>
> The ehci driver on linux-omap works for Beagleboard and sdp.
> so this may not be a fatal problem
>
Actually it's currently broken but issue is known:
http://marc.info/?l=linux-omap&m=124419824625121&w=2
--
Jarkko
next prev parent reply other threads:[~2009-06-10 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 17:45 MUSB Host problems Gary Thomas
2009-06-09 17:49 ` Pandita, Vikram
2009-06-09 18:28 ` Gary Thomas
2009-06-10 2:25 ` Pandita, Vikram
2009-06-10 5:12 ` Jarkko Nikula [this message]
2009-06-10 13:15 ` Gary Thomas
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=20090610081248.417f5d98.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=gary@mlbassoc.com \
--cc=linux-omap@vger.kernel.org \
--cc=vikram.pandita@ti.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