From: Felipe Balbi <me@felipebalbi.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: felipe.balbi@nokia.com, dbrownell@users.sourceforge.net,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Linux Embedded <linux-embedded@vger.kernel.org>,
tony@atomide.com
Subject: Re: omap udc driver problem with beagle board
Date: Sun, 30 May 2010 19:00:48 +0300 [thread overview]
Message-ID: <20100530160047.GA7704@gandalf> (raw)
In-Reply-To: <4C0235AD.70008@gmail.com>
On Sun, May 30, 2010 at 11:53:49AM +0200, Marco Stornelli wrote:
> Hi,
>
> I'm using the kernel 2.6.34 with the beagle board rev. c4. I have got
> some problems with the ethernet gadget to use nfs over usb. The problem
> is with the usb. When the g_ether driver register itself, the omap udc
> driver returns ENODEV because the kernel didn't call the probe for
> this driver. Looking at the code, it seems the problem is in board
> specific management of the usb. There isn't the registration of the
> platform device to match the omap udc platform driver. It should be done
> in the omap_usb_init() but in case of beagle board this function is
> never called, so omap udc driver cannot work. Is it a regression? Is
> there any workaround?
beagle board uses musb. You shouldn't be relying on the udc controller.
Your Kconfig is just wrong.
--
balbi
next prev parent reply other threads:[~2010-05-30 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 9:53 omap udc driver problem with beagle board Marco Stornelli
2010-05-30 16:00 ` Felipe Balbi [this message]
2010-05-31 6:30 ` Marco Stornelli
2010-05-31 7:06 ` Marco Stornelli
[not found] ` <AANLkTine39Za56t8UQRJVeoH94dOuoFAysGPq_cXYhEe-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-31 7:29 ` Felipe Balbi
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=20100530160047.GA7704@gandalf \
--to=me@felipebalbi.com \
--cc=dbrownell@users.sourceforge.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).