From: Greg KH <gregkh@suse.de>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH RFC 0/11] usbserial: Serial Core port.
Date: Tue, 6 Jun 2006 00:29:53 -0700 [thread overview]
Message-ID: <20060606072953.GC17682@suse.de> (raw)
In-Reply-To: <20060603190352.5249c934@home.brethil>
On Sat, Jun 03, 2006 at 07:03:52PM -0300, Luiz Fernando N. Capitulino wrote:
> On Fri, 2 Jun 2006 13:48:39 -0700
> Greg KH <gregkh@suse.de> wrote:
>
> | On Fri, Jun 02, 2006 at 12:03:06AM -0300, Luiz Fernando N.Capitulino wrote:
> | >
> | > Hi folks.
> | >
> | > This patch series is my first attempt to port the USB-Serial layer to the
> | > Serial Core API. Currently USB-Serial uses the TTY layer directly, duplicating
> | > code and solutions from the Serial Core implementation.
> | >
> | > The final (ported) USB-Serial code is simpler and cleaner. Now I'd like to know
> | > whether I'm doing it right or not.
> | >
> | > Note that this is a work in progress though. I've only ported the USB-Serial
> | > core and one of its drivers, the pl2303 one.
> | >
> | > Most of my questions and design decisions are adressed in the patches, please
> | > refer to them for details.
> |
> | Nice first cut at this. But please try to also convert 2 other drivers
> | at the same time to make sure that the model is right. I'd suggest the
> | io_edgeport and the funsoft drivers. io_edgeport because it is very
> | complex in that it doesn't share a single bulk in/out pair for every
> | port, but multiplexes them all through one pipe. And funsoft because we
> | want to still be able to write usb-serial drivers that are this simple.
>
> I'd love to do that but, unfortunatally, USB-Serial cables are too
> expensive in Brazil (and I have no sure if I can find these ones in
> Curitiba).
No need to test fully, if it builds, I can test the io_edgeport driver,
and the funsoft one is pretty much a "nothing" driver.
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-06 7:32 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
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 [this message]
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=20060606072953.GC17682@suse.de \
--to=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