From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Brad Campbell <brad@wasp.net.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Advice on a userspace tty serial driver
Date: Mon, 13 Aug 2007 16:55:23 -0400 [thread overview]
Message-ID: <20070813205523.GA9412@csclub.uwaterloo.ca> (raw)
In-Reply-To: <46BC59E3.2010402@wasp.net.au>
On Fri, Aug 10, 2007 at 04:28:19PM +0400, Brad Campbell wrote:
> I'm building a bit of hardware. It's basically a serial multiplexer that
> communicates to the PC using a single usb-serial port. It has the ability
> to run between 2 and 8 standard async ports over this single interface.
>
> I'd rather not write a kernel driverif possible as I figure this would be a
> perfect application for a userspace daemon to do the control and mux/demux.
> I'd prefer to present standard serial style devices (/dev/ttySxx) to
> userspace giving me the ability to run unmodified software to talk to the
> multiplexed ports.
>
> I think tty/pty pairs looks roughly what I'm after, but will they allow me
> to use standard IOCTLS for conveying baud rate and other standard serial
> parameters to the daemon?
>
> I've spotted several userspace serial driver projects in the last 7 or so
> years, but I can't seem to find any that made it into the kernel.
>
> Am I on the right track with tty/pty or is there a better way?
I don't think you can do any serial specific stuff, like parity and stop
bits and the like across a pty. You might have to actually write a
serial driver to present the devices and handle the ioctls, even if you
have a user space process handle the mux/demux between the real serial
port and the fake ports.
I am curious how you are going to pass the data to the external device,
and indicate which port the data should go through. What will you do
when there is too much data being sent for the real serial port to
handle? I guess if you had a single high speed port, that would be a
start.
--
Len Sorensen
next prev parent reply other threads:[~2007-08-13 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 12:28 Brad Campbell
2007-08-13 20:55 ` Lennart Sorensen [this message]
2007-08-13 21:17 ` Alan Cox
2007-08-13 21:32 ` Arnaldo Carvalho de Melo
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=20070813205523.GA9412@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=brad@wasp.net.au \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®