linux-kernel - arm: davinci: USB ethernet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 19 Mar 2012 05:46:02 -0500
From:	Darryl <ddegraff@...or.com>
To:	<prakash.pm@...com>, <sshtylyov@...sta.com>
CC:	<davinci-linux-open-source@...ux.davincidsp.com>,
	<linux@....linux.org.uk>, <linux-kernel@...r.kernel.org>
Subject: arm: davinci: USB ethernet

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/