From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 8B9761EFD6B; Tue, 15 Nov 2016 13:41:12 -0500 (EST) Received: from hera.aquilenet.fr (hera.aquilenet.fr [141.255.128.1]) by befuddled.reisers.ca (Postfix) with ESMTP id 6BAC11EFCCD for ; Tue, 15 Nov 2016 13:41:11 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id E3AE3A01A; Tue, 15 Nov 2016 19:41:10 +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 0VLL13REHPZW; Tue, 15 Nov 2016 19:41:10 +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 609C2A011; Tue, 15 Nov 2016 19:41:10 +0100 (CET) Received: from samy by var.youpi.perso.aquilenet.fr with local (Exim 4.87) (envelope-from ) id 1c6ifN-0002ty-Va; Tue, 15 Nov 2016 19:41:09 +0100 Date: Tue, 15 Nov 2016 19:41:09 +0100 From: Samuel Thibault To: jheim@math.wisc.edu, "Speakup is a screen review system for Linux." Subject: Re: Status of kernel Message-ID: <20161115184109.GH2448@var.home> References: <20161111162750.GK2417@var.home> <20161111163209.GV2417@var.home> <20161112154759.GP2417@var.home> <20161112221844.GK2417@var.home> <20161113221139.GZ18437@var.home> <582B40D4.1000900@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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:41:12 -0000 John G Heim, on Tue 15 Nov 2016 12:16:26 -0600, wrote: > The one thing that bothers me is that somebody is always > messing with the code that disables speakup access to the serial port. > So somebody is taking the time to diddle with it but not to fix it. Just to be sure: really, nobody is trying hard to break speakup. It's just a side effect of Speakup doing things in a way which is really not supported. When there are changes in the main code, it has side effects on speakup. Plugging properly into the serial as a line discipline drivers would avoid the issue entirely. > Something just occured to me... I wonder if I could get permission from the > University of Wisconsin, where I work, to rewrite speakup for USB. You'd get exactly the same issue. If you write a USB driver that pokes port, then it'll be disturbed by the rest of the kernel. > Everybody who has serial only synths would still be screwed but it'd be a > step forward. No, it'd be just a step aside. Samuel