-----Original Message----- From: Lu, Yinghai
To my understanding, you don't need to waiting for Eric's code. You can use the cable on two systems without debug port support. So just extend the program to make it can write the data too.
Greg,
Anyone is working on creating one usb_serial_driver for USB debug device without using host debug port?
YH
On Fri, Dec 01, 2006 at 10:26:19AM -0800, Lu, Yinghai wrote:
-----Original Message----- From: Lu, Yinghai
To my understanding, you don't need to waiting for Eric's code. You can use the cable on two systems without debug port support. So just extend the program to make it can write the data too.
Greg,
Anyone is working on creating one usb_serial_driver for USB debug device without using host debug port?
I can do that in about 15 minutes if you give me the device ids for the usb debug device that you wish to have.
Or you can also use the generic usb-serial driver today just fine with no modification. Have you had a problem with using that option?
thanks,
greg k-h
On Fri, Dec 01, 2006 at 10:41:23AM -0800, Greg KH wrote:
On Fri, Dec 01, 2006 at 10:26:19AM -0800, Lu, Yinghai wrote:
Anyone is working on creating one usb_serial_driver for USB debug device without using host debug port?
I can do that in about 15 minutes if you give me the device ids for the usb debug device that you wish to have.
The host (aka remote) end of the NET20DC debug device has vid 0x0525 and pid 0x127a.
Or you can also use the generic usb-serial driver today just fine with no modification. Have you had a problem with using that option?
Does it check for a debug descriptor and attach to the device if one is found? Neat!
//Peter
On Fri, Dec 01, 2006 at 08:04:26PM +0100, Peter Stuge wrote:
On Fri, Dec 01, 2006 at 10:41:23AM -0800, Greg KH wrote:
On Fri, Dec 01, 2006 at 10:26:19AM -0800, Lu, Yinghai wrote:
Anyone is working on creating one usb_serial_driver for USB debug device without using host debug port?
I can do that in about 15 minutes if you give me the device ids for the usb debug device that you wish to have.
The host (aka remote) end of the NET20DC debug device has vid 0x0525 and pid 0x127a.
You can use the usb-serial generic driver with those ids (as module parameters) today, with no kernel changes needed.
Or you can also use the generic usb-serial driver today just fine with no modification. Have you had a problem with using that option?
Does it check for a debug descriptor and attach to the device if one is found? Neat!
No, sorry, you need to use the device ids.
thanks,
greg k-h
-
Greg KH -
Lu, Yinghai -
Peter Stuge