Greg KH wrote:
On Tue, Apr 27, 2010 at 11:08:54AM -0400, Jason wrote:
I had what I thought was a great idea, and started stubbing out code
for what would be a USB-over-Ethernet driver. This would be very
similar to the existing, in-kernel, ATA over Ethernet driver. The end
goal would be to access webcams, thumbdrives, printers, etc from my
Android-based phone (no real usb host).
As I was digging around for a proper (minimal) Kconfig to copy into my
directory, I happened upon staging/usbip... oops. They've put a lot
more work into this than I have. However, it's IP. The thing I like
about AoE is that it isn't routable, it's simple and there's less
overhead since it's running at a lower layer.
So, before I burn too many cycles, should I just add my uoe*.c files
to staging/usbip/ or should I create my own staging/uoe/ and borrow
the vhci stuff?
Why not merge it with the existing code, that way the userspace tools
will also work for you, unless you really want to also write new ones of
those?
I agree. Just after an initial glance at [1], it looks like I'll be attempting to write a drop-in replacement for usbip_common_mod.ko.
thx,
Jason.
[1] http://usbip.svn.sourceforge.net/viewvc/usbip/linux/trunk/src/README?view=markup
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
