From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id C401D1EFDB7; Tue, 15 Nov 2016 14:15:44 -0500 (EST) Received: from hera.aquilenet.fr (hera.aquilenet.fr [IPv6:2a01:474::1]) by befuddled.reisers.ca (Postfix) with ESMTP id 809CF1EFDB2 for ; Tue, 15 Nov 2016 14:15:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id 7CB66A475; Tue, 15 Nov 2016 20:15:25 +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 ioxbZMVW3y25; Tue, 15 Nov 2016 20:15:25 +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 F0E009598; Tue, 15 Nov 2016 20:15:24 +0100 (CET) Received: from samy by var.youpi.perso.aquilenet.fr with local (Exim 4.87) (envelope-from ) id 1c6jCW-0003lz-Co; Tue, 15 Nov 2016 20:15:24 +0100 Date: Tue, 15 Nov 2016 20:15:24 +0100 From: Samuel Thibault To: John G Heim Cc: "Speakup is a screen review system for Linux." Subject: Re: Status of kernel Message-ID: <20161115191524.GQ2448@var.home> References: <20161112154759.GP2417@var.home> <20161112221844.GK2417@var.home> <20161113221139.GZ18437@var.home> <582B40D4.1000900@verizon.net> <20161115184109.GH2448@var.home> 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 19:15:46 -0000 John G Heim, on Tue 15 Nov 2016 13:12:49 -0600, wrote: > I figure I can understand the linux kernel. But > maybe you're saying that by the time /dev is populated, it's too late? Please would like to have speakup ready to talk before the /dev directory even exists. > Speakup cannot work like any other device driver? No, because it shouldn't drive hardware, it should be a layer on top of serial drivers. > I already have udev rules to recognize when I plug in the USB cable on my > tripletalk. When it's plugged in during boot, I get speech during boot via > the searial port. Instead of enableing speakup through the serial port, why > can't it talk to my tripletalk via the USB port? It could if it implemented drivers for USB ports. But it's a loot better to just layer it on top of the existing drivers. Samuel