I add some code to know what is really received by the CDC-ACM driver and when i send the OBEX Authentification packet, the cdc-acm driver receive : Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: Entering acm_rx_tasklet Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xA0 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x0 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x1F Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x10 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x0 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x8 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x0 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x4A Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x0 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x13 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xF9 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xEC Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x7B Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xC4 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x95 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x3C Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x11 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xD2 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x98 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x4E Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x52 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x54 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x0 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xDC Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x9E Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x9 Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0xCB Feb 6 20:51:57 antimony kernel: drivers/usb/class/cdc-acm.c: 0x0
Which are *EXACTLY* the waited answer !!! However, when my program read the socket, it received lots of 0xF8 datas. It means the cdc-acm driver has a bug! I will work on it to find out the problem. Regards, P.S.: Datas are send in the logs in the acm_rx_tasklet loop. Le dimanche 6 FÃvrier 2005 20:17, AurÃlien Croc a Ãcrit : > Hi, > Since several times, i try to develop a software which manage files contained > in cellphones by the OBEX protocol and serial connection (USB, IR, Bluetooth, > etc..) and I have same troubles. > For example, when i send the AT+MODE=22 and after the first connection > OBEX packet, in my logs with DEBUG enabled in the cdc-acm driver, i have : > > (Send the AT+MODE=22 command and receive the answer (echo and "OK"): > > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Get 12 bytes > from user space... > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Successfully > copied. > Feb 6 20:04:30 antimony kernel: > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_write_bulk with status 0 > Feb 6 20:04:30 antimony kernel: > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_softint. > Feb 6 20:04:30 antimony kernel: > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_read_bulk with status 0 > Feb 6 20:04:30 antimony kernel: > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_rx_tasklet > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Handed 14 bytes > to tty layer > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_read_bulk with status 0 > Feb 6 20:04:30 antimony kernel: > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_rx_tasklet > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: Handed 7 bytes > to tty layer > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: input control > lines: dcd- dsr- break- ring- framing- parity- overrun- > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: input control > lines: dcd- dsr- break- ring- framing- parity- overrun- > Feb 6 20:04:30 antimony kernel: drivers/usb/class/cdc-acm.c: input control > lines: dcd- dsr+ break- ring- framing- parity- overrun- > Feb 6 20:04:31 antimony last message repeated 122 times > > (Send the OBEX authentification packet): > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_tty_write to write 34 bytes from user space, > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Get 32 bytes > from user space... > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Successfully > copied. > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: input control > lines: dcd- dsr+ break- ring- framing- parity- overrun- > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_write_bulk with status 0 > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_softint. > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_tty_write to write 2 bytes from user space, > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Get 2 bytes > from user space... > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Successfully > copied. > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_write_bulk with status 0 > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_softint. > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: input control > lines: dcd- dsr+ break- ring- framing- parity- overrun- > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_read_bulk with status 0 > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_rx_tasklet > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Handed 32 bytes > to tty layer > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_tty_write to write 7 bytes from user space, > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Get 7 bytes > from user space... > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Successfully > copied. > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_write_bulk with status 0 > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: Entering > acm_softint. > Feb 6 20:04:31 antimony kernel: > Feb 6 20:04:31 antimony kernel: drivers/usb/class/cdc-acm.c: input control > lines: dcd- dsr+ break- ring- framing- parity- overrun- > Feb 6 20:04:31 antimony last message repeated 2 times > > However i receive 31 bytes from the cellphone, but it's not what it's > expected : 0XF8 31 times ! > I don't understand!! My software works fine when i don't use this binary mode! > Regards, > -- AurÃlien Projet APÂC - http://www.ap2c.org Clef Publique : http://www.ap2c.org/aurelien.gpg ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
