[android-kernel] Re: Android USB gadget driver - kernel module instead of built-in

2013-03-04 Thread Hans Kokx
Ryan, This looks like it might be related to your issue: [ 257.163085] sysfs: cannot create duplicate filename '/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0' Before you insmod the module, can you du '/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0' and see if the

[android-kernel] Re: Android USB gadget driver - kernel module instead of built-in

2013-02-21 Thread Nari
2012년 10월 30일 화요일 오전 4시 26분 35초 UTC+9, Ryan Leonard 님의 말: > > Hello all, > > My question is, is it possible to build the linux kernel for an android > device without the usb gadget driver built-in? My motivation and what I > have tried thus far is listed below. > > I am attempting to emulate t

[android-kernel] Re: Android USB Gadget Driver

2012-03-14 Thread bobbark
It looks like there is an issue with the byte alignment. I found this post: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg20797.html and based on that made the following changes to drivers/usb/gadget/ u_ether.c: 257,258c257 < < //skb_reserve(skb, NET_IP_ALIGN); ---

[android-kernel] Re: Android USB Gadget Driver

2012-03-14 Thread bobbark
One more update.. After booting everything up this morning, I did not create the fake ARP entries and ran the pings again. According to Wireshark there was an ARP message coming from the host and an unknown message coming from the Droid, but they were identical lengths. After examining the conte

[android-kernel] Re: Android USB Gadget Driver

2012-03-13 Thread bobbark
Just a little more data... after using arp on the host side and ip on the android side to manually add entries, the Destination Host Unreachable errors went away but still no ping response. I ran Wireshark on the host and the messages from the device are not correct. The displayed mac addresses

[android-kernel] Re: Android USB gadget driver

2009-08-30 Thread Mike Lockwood
On Thu, Aug 27, 2009 at 10:13 PM, 育宇 wrote: > 1)There was one discussion about running two gadget driver > simultaneously before. Does the problem still exist in android1.5? Yes, this is a fundamental limitation of the gadget driver design and still exists in the latest kernel. > 2)I still try t