From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 56C171F0A1A; Tue, 24 Jan 2017 03:30:48 -0500 (EST) Received: from hera.aquilenet.fr (hera.aquilenet.fr [141.255.128.1]) by befuddled.reisers.ca (Postfix) with ESMTP id 4FEA01F0A04 for ; Tue, 24 Jan 2017 03:30:47 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id CABE8B2DC; Tue, 24 Jan 2017 09:30:46 +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 5eUpFkXFDa4n; Tue, 24 Jan 2017 09:30:46 +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 4AF42A3C4; Tue, 24 Jan 2017 09:30:46 +0100 (CET) Received: from samy by var.youpi.perso.aquilenet.fr with local (Exim 4.88) (envelope-from ) id 1cVwV3-0005Qx-Qe; Tue, 24 Jan 2017 09:30:45 +0100 Date: Tue, 24 Jan 2017 09:30:45 +0100 From: Samuel Thibault To: Okash Khawaja Cc: "Speakup is a screen review system for Linux." Subject: Re: Line discipline Message-ID: <20170124083045.GN2695@var.home> References: <20161220010836.GN2895@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, 24 Jan 2017 08:30:48 -0000 Okash Khawaja, on Tue 24 Jan 2017 06:16:46 +0000, wrote: > Combined the refactor changes with your tty code to test speakup_dummy. It > seems okay Good :) > except for problem when unloading speakup.ko - it is in use so can't > be unloaded. I have just got this so investigating it. I guess it's a release issue on the tty or such. Could you share your code so we can investigate too? > One question. Using your code, we can obtain tty, cache it and use it directly > for all subsequent writes. Why then use ldisc? To be able to read characters. There is no "read" operation in the tty. We'll receive characters through the receive_buf callback. Samuel