public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: dwmw2@infradead.org, rmk@arm.linux.org.uk, gregkh@suse.de,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, zaitcev@redhat.com
Subject: Re: [PATCH RFC 0/11] usbserial: Serial Core port.
Date: Sun, 4 Jun 2006 16:24:53 -0700	[thread overview]
Message-ID: <20060604162453.696f190b.zaitcev@redhat.com> (raw)
In-Reply-To: <20060604201223.7cd37936@home.brethil>

On Sun, 4 Jun 2006 20:12:23 -0300, "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br> 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.

Running uploads and downloads with things like xmodem is a good
test of hardware flow control, so someone will have to do it too.

>  Unfortunatally this is a very expensive test environment, and I can't use
> it for development. The best one would be to have a USB<->DB9 cable..

PL-2303 already has a DB-9, you actually you need a DB-9-to-DB-9
Null Modem (cross-over) cable.

Anyway, I do not expect pl2303 failing this test, mind. It's more
of a problem for simpler devices.

-- Pete

  reply	other threads:[~2006-06-04 23:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1149217397133-git-send-email-lcapitulino@mandriva.com.br>
2006-06-02  6:48 ` [PATCH RFC 0/11] usbserial: Serial Core port Pete Zaitcev
2006-06-02 10:03   ` David Woodhouse
2006-06-02 13:45     ` Luiz Fernando N. Capitulino
2006-06-02 13:54       ` David Woodhouse
2006-06-02 14:07         ` Luiz Fernando N. Capitulino
2006-06-02 22:47     ` Pete Zaitcev
2006-06-04 23:12       ` Luiz Fernando N. Capitulino
2006-06-04 23:24         ` Pete Zaitcev [this message]
2006-06-05 12:14           ` Luiz Fernando N. Capitulino
2006-06-05 12:29             ` David Woodhouse
2006-06-02 13:39   ` Luiz Fernando N. Capitulino
2006-06-02 20:48 ` Greg KH
2006-06-03 22:03   ` Luiz Fernando N. Capitulino
2006-06-06  7:29     ` Greg KH
2006-06-06 13:03       ` Luiz Fernando N. Capitulino
     [not found] ` <1149217398434-git-send-email-lcapitulino@mandriva.com.br>
2006-06-02 20:50   ` [PATCH 8/11] usbserial: pl2303: Ports tty functions Greg KH
2006-06-02 22:41     ` Pete Zaitcev
2006-06-02 22:44       ` Greg KH
2006-06-03 22:19         ` Luiz Fernando N. Capitulino
2006-06-06  7:34           ` Greg KH
2006-06-06  9:23             ` Alan Cox
2006-06-06 16:15               ` Luiz Fernando N. Capitulino
2006-06-06 13:10             ` Luiz Fernando N. Capitulino
2006-06-06 16:38               ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060604162453.696f190b.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=lcapitulino@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rmk@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox