From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 0DA361EFD6B; Tue, 15 Nov 2016 13:47:15 -0500 (EST) Received: from hera.aquilenet.fr (hera.aquilenet.fr [141.255.128.1]) by befuddled.reisers.ca (Postfix) with ESMTP id 898621EFCCD for ; Tue, 15 Nov 2016 13:47:13 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id 0721FA01A; Tue, 15 Nov 2016 19:47:13 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at aquilenet.fr Received: from hera.aquilenet.fr ([127.0.0.1]) by localhost (hera.aquilenet.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKEchiit6L_e; Tue, 15 Nov 2016 19:47:11 +0100 (CET) Received: from var.youpi.perso.aquilenet.fr (unknown [IPv6:2a01:cb19:181:c200:3602:86ff:fe2c:6a19]) by hera.aquilenet.fr (Postfix) with ESMTPSA id 68E32A011; Tue, 15 Nov 2016 19:47:11 +0100 (CET) Received: from samy by var.youpi.perso.aquilenet.fr with local (Exim 4.87) (envelope-from ) id 1c6ilC-0003CP-UH; Tue, 15 Nov 2016 19:47:10 +0100 Date: Tue, 15 Nov 2016 19:47:10 +0100 From: Samuel Thibault To: Okash Khawaja Cc: John Covici , David Borowski , "Speakup is a screen review system for Linux." Subject: Re: Status of kernel Message-ID: <20161115184710.GI2448@var.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2D152C7E-B42B-4978-9E23-E8B65145334D@gmail.com> User-Agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 18:47:15 -0000 Okash Khawaja, on Tue 15 Nov 2016 06:58:24 +0000, wrote: > On Tue, Nov 15, 2016 at 6:36 AM, Samuel Thibault <[2] > samuel.thibault@ens-lyon.org> wrote: > > And how will /dev/ttyx be used? > > It won't be used. As a line discipline speakup will plug higher in the > stack. > > Could you explain this more? May be a concrete example? > I mean is this something that a user space application will read from? Normally what happens, for instance when running a serial mouse driver, is that a userland program opens /dev/ttyS0, calls an ioctl to set the N_MOUSE line discipline, and then leaves /dev/ttyS0 alone. All the work is done by the line discipline, userland doesn't do any read/write on the device. I.e. the line discipline catches the data before it reaches userland. > If so, what is the specific advantage of speakup being line > discipline? It's simply because that's the way things work for all other drivers "over serial lines", like mice, joysticks ppp, gsm, etc. There is then no risk for speakup to break at all, these have been working for decades without a fuss. And they will work with anything that looks more or less like a serial port, be it ISA, PCI, USB, bluetooth, irda, whatever. > Please add any links/documentation that will help > understand this. Thanks Unfortunately line disciplines are a rather obscure area not many people work on. There is linux/Documentation/serial/tty.txt > > Also is there a link to where you pasted your idea from? > > I wrote it. > > Of course. I mean a link to full discussion to get more context. There is a thread starting here: http://www.spinics.net/lists/linux-serial/msg21752.html Samuel