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 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
