From: Pete Zaitcev <zaitcev@redhat.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
rmk@arm.linux.org.uk, linux-usb-devel@lists.sourceforge.net,
zaitcev@redhat.com
Subject: Re: [PATCH RFC 0/11] usbserial: Serial Core port.
Date: Thu, 1 Jun 2006 23:48:33 -0700 [thread overview]
Message-ID: <20060601234833.adf12249.zaitcev@redhat.com> (raw)
In-Reply-To: <1149217397133-git-send-email-lcapitulino@mandriva.com.br>
On Fri, 02 Jun 2006 00:03:06 -0300, "Luiz Fernando N.Capitulino" <lcapitulino@mandriva.com.br> wrote:
This looks interesting, although I do not know if it buys us much.
The code seems sane at first view. The private lock inside pl2303
saves you from the most obvious races.
> The tests I've done so far weren't anything serious: as the mobile supports a
> AT command set, I have used the ones (with minicom) which transfers more data.
> Of course that I also did module load/unload tests, tried to disconnect the
> device while it's transfering data and so on.
Next, it would be nice to test if PPP works, and if getty and shell work
(with getty driving the USB-to-serial adapter).
> +static void serial_send_xchar(struct uart_port *port, char ch)
> +{
> + USBSERIAL_PORT->serial->type->uart_ops->send_xchar(port, ch);
> }
I think you just inherited a mistake in usb-serial design. It attempts
to act as an adaptation layer (like, say, USB core itself) instead of
a library like libata. Why can't the UART framework call pl2303?
Also this meaningless obfuscation has to go:
> +#define USBSERIAL_PORT ((struct usb_serial_port *)port)
> +static void pl2303_start_tx(struct uart_port *port)
> +{
> + struct usb_serial_port *usp = USBSERIAL_PORT;
Greetings,
-- Pete
next parent reply other threads:[~2006-06-02 6:49 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 ` Pete Zaitcev [this message]
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
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=20060601234833.adf12249.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--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
Powered by JetHome