Thanks for sharing the final patch that you've got. The feedback is certainly helpful too. There was some difficulty in supporting hot plugs in KGDB and concurrent UMS. But let's see if they can be done. :)
On Aug 18, 11:04 am, wqs wlp <wqs...@gmail.com> wrote: > Thanks Danke's awesone work! The functions he wrote satisfied my debugging > pretty well. > > now I am sending the complete patch I am using. The thing is, you have to > modify board-mahimahi.c as well. > Because, you have to disable CONFIG_USB_ANDROID_MASS_STORAGE to avoid usb > interface enumeration errors. > other components just working fine. I am keeping cdc_acm gadget and adb > gadget in my devices kernel. > > Hope Danke or someone can help fix this > > Be noticed that disable CONFIG_USB_ANDROID_MASS_STORAGE does not mean you > lose your sdcard. But you just can not mount it directly from the host > system. You still can "adb push XXX /sdcard/" for your file transfer tasks. > > Another bug is , when you unplug the cable from the device, you will get the > following errors from the dmesg : > [52874.177911] ehci_hcd 0000:00:1d.7: devpath 7.2 ep2in 3strikes > [52874.178161] ehci_hcd 0000:00:1d.7: detected XactErr len 0/1024 retry 1 > [52874.178286] ehci_hcd 0000:00:1d.7: detected XactErr len 0/1024 retry 2 > [52874.178301] hub 5-7:1.0: state 7 ports 4 chg 0000 evt 0004 > [52874.178414] ehci_hcd 0000:00:1d.7: detected XactErr len 0/1024 retry 3 > [52874.178539] ehci_hcd 0000:00:1d.7: detected XactErr len 0/1024 retry 4 > [52874.178547] hub 5-7:1.0: port 2, status 0100, change 0001, 12 Mb/s > [52874.178664] ehci_hcd 0000:00:1d.7: detected XactErr len 0/1024 retry 5 > [52874.178672] usb 5-7.2: USB disconnect, address 113 > [52874.178674] usb 5-7.2: unregistering device > [52874.178676] usb 5-7.2: usb_disable_device nuking all URBs > > > > On Thu, Jul 15, 2010 at 11:29 AM, Danke Xie <danke....@gmail.com> wrote: > > I was trying to connect to the serial port on the Android device from > > the host PC. What I was doing was loading the "usbserial" driver: > > > modprobe usbserial product=<product id> vendor=<vendor id> > > > It seems it does recognize all serial functions in the USB and created > > several ttyUSB ports/devices. However, it seems (at least on my > > device) that the interface used by ADB is also picked up by > > "usbserial", and because of that, I couldn't use ADB to connect to the > > device until I unload usbserial. > > > Do you know if this is an issue? Is there a way to get both usbserial > > and ADB to work? > > > Thanks! > > > -- > > unsubscribe: > > android-kernel+unsubscr...@googlegroups.com<android-kernel%2bunsubscr...@go > > oglegroups.com> > > website:http://groups.google.com/group/android-kernel > > > > 0001-kgdb-over-USB.patch > 14KViewDownload -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
