From: Vojtech Pavlik <vojtech@suse.cz>
To: "David S. Miller" <davem@redhat.com>
Cc: rmk@arm.linux.org.uk, jsimmons@transvirtual.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.31-serport
Date: Sat, 31 Aug 2002 00:36:18 +0200 [thread overview]
Message-ID: <20020831003618.B33615@ucw.cz> (raw)
In-Reply-To: <20020830.150359.16679671.davem@redhat.com>; from davem@redhat.com on Fri, Aug 30, 2002 at 03:03:59PM -0700
On Fri, Aug 30, 2002 at 03:03:59PM -0700, David S. Miller wrote:
> From: Russell King <rmk@arm.linux.org.uk>
> Date: Fri, 30 Aug 2002 22:39:11 +0100
>
> 2. What happens if I open and try to read from this port while something
> has the serport_ldisc attached? I suspect that you'll create nice
> loop of serio devices in serio.c and an infinite loop when you try to
> traverse the list to remove a different serio device.
>
> SERIO devices are not meant to be registered as normal TTYs.
> At least I don't do this for any of the Sparc serial ports
> when they are the keyboard/mouse serio device.
No, but using serport.c, you can bind a serio to a tty via a line
discipline, for example if you want a PC serial mouse on /dev/ttyS0 to
talk to sermouse.c via serio. I don't like the approach much, I hope(d) we
could switch somewhere below the tty layer, but it sort of works, and
maybe will have the bugs fixed sooner or later.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-08-30 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 21:39 Russell King
2002-08-30 22:03 ` David S. Miller
2002-08-30 22:36 ` Vojtech Pavlik [this message]
2002-08-30 22:43 ` David S. Miller
2002-08-31 0:34 ` Alan Cox
2002-08-30 22:40 ` Vojtech Pavlik
2002-08-31 14:16 ` [patch] Fixes in serport.c Vojtech Pavlik
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=20020831003618.B33615@ucw.cz \
--to=vojtech@suse.cz \
--cc=davem@redhat.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®