From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 2E3431EF756; Sat, 11 Oct 2014 05:55:52 -0400 (EDT) Received: from mail0131.smtp25.com (mail0131.smtp25.com [75.126.84.131]) by befuddled.reisers.ca (Postfix) with ESMTPS id B59311EF736 for ; Sat, 11 Oct 2014 05:55:50 -0400 (EDT) Received: from ccs.covici.com (s-out-001.smtp25.com [67.228.91.90]) by d-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id s9B9td1G004718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 11 Oct 2014 05:55:40 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id s9B9tcgF009863 for ; Sat, 11 Oct 2014 05:55:38 -0400 To: "Speakup is a screen review system for Linux." Subject: Re: speakup in the kernel In-reply-to: <20141011074623.GB2692@type> References: <86a956i23h.fsf@vibrator.pk5001z> <20141009125200.GI1044@opera.rednote.net> <86ppe1gyed.fsf@vibrator.pk5001z> <5436B2E4.5060306@math.wisc.edu> <5436B66A.4060600@tysdomain.com> <5436BD4A.1090208@math.wisc.edu> <21053.1412882630@ccs.covici.com> <5436EA36.5010105@math.wisc.edu> <20141011074623.GB2692@type> Comments: In-reply-to Samuel Thibault message dated "Sat, 11 Oct 2014 09:46:23 +0200." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.4.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Sat, 11 Oct 2014 05:55:38 -0400 Message-ID: <9862.1413021338@ccs.covici.com> From: covici@ccs.covici.com X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: d-out-001.smtp25.com-s9B9td1G004718 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.18 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: Sat, 11 Oct 2014 09:55:52 -0000 One of those people once told me that you could write a driver, pretend speakup is a new device or something like that and find the serial port the same way the current 8250 drivers do. Is this nonsense, or is it something we could do and this would make speakup much more robust than it is now. Samuel Thibault wrote: > John G. Heim, le Thu 09 Oct 2014 15:04:06 -0500, a =C3=A9crit : > > I once asked on the kernel developers list what the right way to > > access the serial port was. If speakup does it wrong, that implies ther= e is > > a right way, what is that? >=20 > "Doing it wrong" doesn't mean that the "right way" is already available. > The difficulty here is that the right way doesn't exist yet, even if the > kernel developers have an idea of how it would look like. It's a matter > of getting the time to do it. >=20 > Samuel > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup --=20 Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com