Hy,
> Were you getting such messages from the kernel? "dmesg"
> would show them if you were.
Sorry, i forgot to mention that i included some "extended" printk's by myself.
> But again: if you're not already getting those warnings,
> don't bother looking since that's not the problem.
I get no messages from the "normal" g_serial module.
I'm using the PuTTYtel (version. 0.6 on Windows XP SP2) and the error message
after plugin the USB cable is:
"unable to open connection to COM4. Unable to configure serial port."
(i configured PuTTYtel with speed: 115200 and connection type: serial)
Sorry, if i bore you, just to get sure there is no "methodic" error:
0. configure and compile hardware udc driver and gadget serial module
1. "mknod /dev/ttygserial c 127 0"
2. modprobe g_serial use_acm=1
3. plugin USB client cable
3.a following printouts on Client were created:
-- START PRINT OUT --
gs_disconnect: Gadget Serial disconnect
gs_disconnect: Gadget Serial disconnect
gs_disconnect: Gadget Serial disconnect
gs_set_config: Gadget Serial configured, full speed CDC-ACM config
-- END PRINT OUT --
3.b On Host (Windows XP SP-2) in the device manager is a comport COM4
created with the name "Gadget Serial"
(Until now, all seems to be ok)
4. start PuTTYtel and try to open the COM4 (115200,8,1,None,no flow control)
(at least the speed configuration has no effect)
5. after a few seconds the error message described above is shown.
(Steps 0-3 are documented in the gadget_serial.txt)
Some (perhaps silly) questions:
1. to "attach" a terminal programm (like getty) to that resulting device i have
to do "/sbin/getty -L 115200 /dev/ttygserial"?
2. If i haven't done "attaching terminal programm" may be that the errror
(handling error by myself)?
3. The "extern int net2280_set_fifo_mode(...)" statement on line 251 (serial.c)
should be adapted to the "real" hardware or replaced by the appropriate
function of the *_udc driver?
As a try to compare i used a linux (Suse 10.1) as host. I unpluged the usb
cable (no target system restart) and attached the cable to a linux host.
The resulting dmesg of the host (!):
-- START DMESG HOST OUTPUT --
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: new device found, idVendor=0525, idProcduct=a4a7
usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-1: Product: Gadget Serial
usb 3-1: Manufacturer: Linux 2.6.22-default with pxa27x_udc
usb 3-1: SerialNumber: 0
usb 3-1: configuration #2 chosen from 1 choice
drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is
no modem.
cdc_acm 3-1:2.0: ttyACM0: USB ACM device
usbcore: registred new driver cdc_acm
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB
modems and ISDN adapters
-- END DMESG HOST OUTPUT --
On the target side i executed a 'cat /dev/ttygserial'.
Afterwards on the host side i executed a 'echo "1" > /dev/ttyACM0'
As expected a "1" appeares on the target side.
But the other way round the "1" didn't appear.
After attaching a getty to the /dev/ttygserial (descibed above)
and starting a configured minicom on the linux host i'm able to
login on the target platform.
After a "exit" (exit off the login on the target platform) the "attached" getty
terminates.
What is the "correct" way to attach the getty "permanently" to
the ttygserial device? (entry in the inittab? But on the time inittab excecutes
the ttygserial is not present to the system).
Conclusions:
1. pxa27x_udc seems to be ok
2. gadget serial in ACM mode works on linux hosts
=> Windows seems to do some none standard procedures (?)
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
