From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: "John G. Heim" <jheim@math.wisc.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: speakup bug
Date: Sun, 4 Mar 2012 01:18:06 +0100 [thread overview]
Message-ID: <20120304001806.GO4180@type.famille.thibault.fr> (raw)
In-Reply-To: <FD8CB954D8084F998E24C4558E41C627@hinkle>
John G. Heim, le Sat 03 Mar 2012 18:01:07 -0600, a écrit :
> >The speakup people have been told this repeatedly for years and years
And the kernel hasn't really provided the feature for speakup to use it
for years and years.
> >which is why their drivers work on less and less systems and won't run
> >with things PCI or USB serial ports, and why they are forever buried in
> >staging.
>
> Do you recall if they gave a reason for not wanting to use the serial layer?
Because no such facility really exists, it still has to to be done
before speakup can use it. It's on my TODO list for years now, and still
haven't found the time to work on it.
> I don't even know what the serial layer is (although the name is descriptive
> enough and I can guess).But I would think they'd have had some reason for
> not wanting to do that.
It's definitely not a "not want", but "can not use what does not exist".
Just for the record: what we need is being able to open a serial port
and read/write from inside the kernel. Using a daemon that does the open
and setting up speakup as a line discipline would be possible, but it
then depends on / working, and that's not something e.g. administrators
can really afford depending on.
Samuel
next prev parent reply other threads:[~2012-03-04 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 17:18 John G. Heim
2012-03-03 17:39 ` Alan Cox
2012-03-03 22:01 ` Ted Ts'o
2012-03-04 0:01 ` John G. Heim
2012-03-04 0:18 ` Samuel Thibault [this message]
2012-03-04 0:21 ` Samuel Thibault
2012-03-04 0:41 ` Ted Ts'o
2012-03-04 0:43 ` Samuel Thibault
2012-03-04 0:44 ` Samuel Thibault
2012-03-04 1:41 ` Ted Ts'o
2012-03-04 0:26 ` Ted Ts'o
2012-03-04 2:03 ` John G. Heim
2012-03-04 21:06 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120304001806.GO4180@type.famille.thibault.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jheim@math.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®