On Sun, 4 Jun 2006 16:24:53 -0700 Pete Zaitcev <[EMAIL PROTECTED]> wrote:
| On Sun, 4 Jun 2006 20:12:23 -0300, "Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote: | | > | I understand. My intent was different, however. One of the bigger sticking | > | points for usb-serial was its interaction with line disciplines, which are | > | notorious for looping back and requesting writes from callbacks | > | (e.g. h_hdlc.c). They are also sensitive to drivers lying about the | > | amount of free space in their FIFOs. This is something you never test | > | when driving a serial port from an application, no matter how cleverly | > | written. | | > In all the tests the modem was configured to answer the calls, and the | > cell phone was configured to dial to the modem (my home's number). | | This is exactly backwards, and so it tests different code paths. | The line discipline is involved into driving a cooked mode port, | e.g. the one where getty is. I was going to try it last night and realized that my cell phone can't answer data calls. :(( -- Luiz Fernando N. Capitulino _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
