linux-kernel - Re: [PATCH] Add the ability to layer another driver over the serial driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Dec 2006 20:01:10 +0100 (CET)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	Alan <alan@...rguk.ukuu.org.uk>
cc:	Corey Minyard <cminyard@...sta.com>,
	Tilman Schmidt <tilman@...p.cc>, linux-serial@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Hansjoerg Lipp <hjlipp@....de>, Russell Doty <rdoty@...hat.com>
Subject: Re: [PATCH] Add the ability to layer another driver over the serial
 driver

On Mon, 11 Dec 2006, Alan wrote:

> On Sun, 10 Dec 2006 19:23:54 -0600
> Corey Minyard <cminyard@...sta.com> wrote:
> 
> > Nothing has come of this yet.  But we have these two requests and a 
> > request from Russell Doty at Redhat.
> > 
> > It would be nice to know if this type of thing was acceptable or not, 
> > and the problems with the patch.  The patch is at 
> > http://home.comcast.net/~minyard
> 
> This looks wrong. You already have a kernel interface to serial drivers.
> It is called a line discipline. We use it for ppp, we use it for slip, we
> use it for a few other things such as attaching sync drivers to some
> devices.

Alan, my understanding might be wrong, but, I think, line disciplines are 
there as "protocols" for user-tty interfaces, i.e., you need a user, that 
opens a tty, sets a line discipline to it, and does io (read/write) over 
it, and NOT to be completely initialised and driven from the kernel. 
Whereas, what some users need is a complete in-kernel interface, when 
either another driver (like in case with the previous poster), or the 
platform code (linkstation) know that there's a device attached to this 
UART, know how and WHEN to operate it, and the user doesn't care about it 
at all. Think of it as about, say, i2c devices, that have user device 
interface and in-kernel interface, to which you can connect rtc, USB 
transceivers, that get controlled completely from the kernel TRANSPARENTLY 
for the user.

Thanks
Guennadi
---
Guennadi Liakhovetski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/