From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: Add hardware handshaking to pseudo-tty and USB serial gadget
Date: Fri, 22 Mar 2013 14:22:39 +0000 (UTC) [thread overview]
Message-ID: <kihpff$3mi$1@ger.gmane.org> (raw)
In-Reply-To: 1363904564.4488.47.camel@thor.lan
On 2013-03-21, Peter Hurley <peter@hurleysoftware.com> wrote:
> On Thu, 2013-03-21 at 20:38 +0000, Grant Edwards wrote:
>> On 2013-03-21, Craig McQueen <craig.mcqueen@beamcommunications.com> wrote:
>> > It sounds as though people have done pseudo-ttys with HW handshaking
>> > support--eg tty0tty project. However I'd rather implement this
>> > function in the kernel pseudo-terminal driver itself. Is there any
>> > reason not to do that?
>>
>> No reason other than you and I are the only two people who care about
>> it. :)
>
> Assuming you're leaning toward an in-kernel solution, why not just
> implement a new tty driver that behaves like a local serial port?
I've been thinking about trying to do that except making it a
serial_core driver on the slave side rather than a tty driver. I just
converted a tty driver to the serial-core API and the code-size
dropped by almost 70% (hopefully the undiscovered bug count dropped as
well). I hadn't decided what to do for a master-side API. I'd
probably abandon the standard tty API altogether and do something from
scratch as a plain char device driver with custom ioctl calls.
--
Grant Edwards grant.b.edwards Yow! A dwarf is passing out
at somewhere in Detroit!
gmail.com
prev parent reply other threads:[~2013-03-22 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 11:21 Add hardware handshaking to pseudo-tty and USB serial gadget Craig McQueen
2013-03-21 20:38 ` Grant Edwards
2013-03-21 22:22 ` Peter Hurley
2013-03-21 23:32 ` Craig McQueen
2013-03-22 0:03 ` Peter Hurley
2013-03-22 1:44 ` Craig McQueen
2013-03-22 2:14 ` Peter Hurley
2013-03-22 10:11 ` Peter Korsgaard
2013-03-22 14:22 ` Grant Edwards [this message]
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='kihpff$3mi$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=linux-serial@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.