All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darryl <ddegraff@licor.com>
To: <prakash.pm@ti.com>, <sshtylyov@mvista.com>
Cc: <davinci-linux-open-source@linux.davincidsp.com>,
	<linux@arm.linux.org.uk>, <linux-kernel@vger.kernel.org>
Subject: arm: davinci: USB ethernet
Date: Mon, 19 Mar 2012 05:46:02 -0500	[thread overview]
Message-ID: <4F670E6A.9060403@licor.com> (raw)

We are currently using a DA850 eval board but will eventually use a 
custom board to interface host system to davinci using ethernet over 
USB.  We are using 2.6.37 with real-time patches, but a cursory look 
(have not been able to build yet) at 3.3-rc7 suggests that the issues 
noted below still exist.

There are currently two issues:

- Documentation/usb/hotplug.txt suggests that the drivers should be 
built as modules so that such things as loading drivers and, in this 
case, bringing up the interface, can ge moderated in user-space.  
However, though the code can be build modular, the drivers are never 
loaded.  I suspect that one or more of the several relevant configs (I 
see at least these:  USB_MUSB_HDRC, USB_MUSB_DA8XX_GLUE, USB_GADGET, 
USB_ETH, USB_GPIO_VBUS, NOP_USB_XCEIV, USB_ETH_RNDIS, USB_OTG_UTILS) are 
required to be built in, but cannot seem to determine the correct ones.

- Even when compiling all the driver code built-in, neither the plug-in 
nor plug-out event is propagated to user space, again, so that the 
interface can be brought up.

I am happy enough to build-in the driver code, but I still need the 
ability to bring up the interface.  I know that I can use a call to
         call_usermodehelper
to get to use-space, but I'd still be faced with where that call would 
work best.

So, I'm wondering if you have suggestions regarding how to proceed.

Thanks,
Darryl


             reply	other threads:[~2012-03-19 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 10:46 Darryl [this message]
2012-03-20 13:58 ` arm: davinci: USB ethernet Greg KH
2012-03-20 15:52   ` ddegraff
2012-03-20 16:00     ` Greg KH

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=4F670E6A.9060403@licor.com \
    --to=ddegraff@licor.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=prakash.pm@ti.com \
    --cc=sshtylyov@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.