EHCI debug device gadgets and host

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

Is someone actively working on or maintaining the EHCI debug device
gadget driver? I would like to see some fixes and/or improvements to it
but do not know the gadget framework and some of the required hardware
is not yet on my desk.

So the incomplete report here is from a friends' experiment.

The behaviour was experienced on both BeagleBone Black and GTA04 used as
the gadget side. These and other recent ARM boards could be used for
kernel debugging of x86 platforms where EHCI debug port is available and
there is no classic serial port.

The problem is with CONFIG_G_DBGP_SERIAL disconnecting the TTY on USB
resets. While this may be correct behaviour for most use cases, it means
when connected to a debug target with EHCI debug port in kernel, the TTY
link does not survive over target board USB reset signalling.
Also in my use case (debugging coreboot) we may need one or two USB
resets even before kernel.


For the debug target side, I have previously written some patches to get
compatibility with USB FX2 chips to be used as a replacement debug
device now that the Net20DC part is hard to get.

I hope we could discuss if some patches here are relevant for
upstreaming:

https://bitbucket.org/kmalkki/linux-kernel/commits/branch/ehci-dbgp-test2


Regards,
KM

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux