public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Balbi, Felipe" <balbi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP3 & USB NFS root
Date: Wed, 16 Feb 2011 08:44:26 +0200	[thread overview]
Message-ID: <1297838666.2031.8.camel@deskari> (raw)
In-Reply-To: <20110214140216.GJ2549@legolas.emea.dhcp.ti.com>

On Mon, 2011-02-14 at 08:02 -0600, Balbi, Felipe wrote:
> On Mon, Feb 14, 2011 at 04:00:39PM +0200, Tomi Valkeinen wrote:
> > On Mon, 2011-02-14 at 07:48 -0600, Balbi, Felipe wrote:
> > > On Mon, Feb 14, 2011 at 03:46:46PM +0200, Tomi Valkeinen wrote:
> > > > Hi,
> > > > 
> > > > I've been trying to get USB ethernet gadget driver working so that I can
> > > > use NFS root to boot my board (overo or beagle).
> > > > 
> > > > With 2.6.37 I did get it work, but only after I enabled host mode and
> > > > set the driver mode to OTG. With just USB peripheral mode it didn't seem
> > > > to work.
> > > > 
> > > > With 2.6.38-rc4 I don't seem to get it working at all, not matter what
> > > > config options I have tried.
> > > > 
> > > > And when I say "not working" I mean I don't get any output about USB
> > > > when the kernel is waiting for the rootfs. Not even if I unplug and plug
> > > > the USB cable. And the PC's kernel messages don't show anything when the
> > > > board's kernel boots up.
> > > > 
> > > > I've attached the configs I have tried.
> > > 
> > > try this patch:
> > > 
> > > commit d5f42190e7cf11b20face63ee96f26c7d2067b63
> > > Author: Ming Lei <tom.leiming@gmail.com>
> > > Date:   Wed Jan 5 22:03:21 2011 +0800
> > > 
> > >     arm: omap4: panda: remove usb_nop_xceiv_register(v1)
> > >     
> > >     Panda uses both twl6030 otg phy(vbus, id) and internal
> > >     phy(data lines, DP/DM), so removes usb_nop_xceiv_register to make
> > >     twl6030 otg driver working since current otg code only supports
> > >     one global transceiver. Otherwise, musb doesn't work without
> > >     the remove.
> > 
> > I don't use Panda (yet, damn fedex...), but Overo or Beagle.
> 
> ah, ok. So it's another problem. I don't have beagle, but I have an old
> overo here. Will try tomorrow to see what's going on. Thanks for the
> report.

Did you get a chance to try this? Or any suggestions what I could try? I
could of course try to bisect it, but that's quite laborious as I have
to store the kernel into an mmc to be able to use it.

 Tomi



  reply	other threads:[~2011-02-16  6:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1297691206.2951.8.camel@deskari>
2011-02-14 13:48 ` OMAP3 & USB NFS root Felipe Balbi
2011-02-14 14:00   ` Tomi Valkeinen
2011-02-14 14:02     ` Felipe Balbi
2011-02-16  6:44       ` Tomi Valkeinen [this message]
2011-02-16  8:02         ` Felipe Balbi
2011-02-16  8:05           ` Felipe Balbi
2011-02-16  9:44             ` Tomi Valkeinen
2011-02-16  9:49               ` Felipe Balbi
2011-02-16 10:00                 ` Tomi Valkeinen
2011-02-16 10:26                   ` Felipe Balbi
2011-02-16 10:30                     ` Tomi Valkeinen

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=1297838666.2031.8.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.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