Date: Thu, 24 Jul 2003 09:26:35 +0100
From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kurt =?iso-8859-1?Q?H=E4usler?= <Kurt@fub-group.de>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Accessing serial port from kernel module
Message-ID: <20030724082635.GA18443@axis.demon.co.uk>
References: <8FB92279C69C2944B325B4BD227401790156B8@nt-server.danziger.local> <1058970342.5520.74.camel@dhcp22.swansea.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1058970342.5520.74.camel@dhcp22.swansea.linux.org.uk>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1069
Lines: 24

On Wed, Jul 23, 2003 at 03:25:43PM +0100, Alan Cox wrote:
> The user space only approach is to use pty/tty pairs as things like
> xterm do. This gives you a "terminal/serial" device the other end of
> which is your user space program which can do the conversions it wants
> then talk to a real serial port

In this latter approach is there any way for the user space program to
catch the termios ioctls (eg to set baud rate etc) that the
application does on the tty end of the pty/tty pair?

(I believe the answer is no!  I got half way through writing a pty/tty
replacement driver which passed the relevant ioctls (decoded into
platform independent "change baud rate to 9600" etc) on the tty
in-band to the pty.  I used in-band so this data stream could then be
piped via ssh etc)

-- 
Nick Craig-Wood
ncw1@axis.demon.co.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/