From: Sam Hartman <hartmans@debian.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Sam Hartman <hartmans@debian.org>,
Zhenzhong Duan <zhenzhong.duan@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Question about dynamic minor number of misc device
Date: Tue, 21 Jan 2020 12:54:21 -0500 [thread overview]
Message-ID: <tslh80o3dbm.fsf@suchdamage.org> (raw)
In-Reply-To: <20200121163110.GK15860@mit.edu> (Theodore Y. Ts'o's message of "Tue, 21 Jan 2020 11:31:10 -0500")
>>>>> "Theodore" == Theodore Y Ts'o <tytso@mit.edu> writes:
Theodore> Sam,
Theodore> Would you happen to know how commonly used the speakup system would be
Theodore> --- in particular, on non-udev systems where changing the minor number
Theodore> of the device node might break some folks? Does your hardware system
Theodore> use speakup, or some other interface?
Speakup is used by things like the Debian Installer in speech mode.
I'd assume D-I uses udev.
However Speakup is also likely to be used by blind people who prefer
older environments--no GUI, no pulseaudio, that sort of thing.
No udev is kind of pushing that mindset to the extreme though.
Speakup is not typically used without a keyboard or similar, so you're
not going to see it on embedded systems.
Theodore> Also, who would be the best people to reach out at the
Theodore> linux-speakup.org project to verify what the potential impact might be
Theodore> of making this change. It looks like some of the web pages are a bit
Theodore> dated, so I wasn't sure what's up to date.
I might ask on debian-accessibility@lists.debian.org.
My recollection is that the upstream is not very energetic, and that the
distros keep speakup working because it's quite important for some
people.
We broke it on hda_intel for the original Buster release and that
certainly generated lots of user feedback.
debian-accessibility is Debian specific. There is the more general
blinux-l@lists.redhat.com (blind linux users), but that lists tends to
be so user focused that you might not get good feedback to a question
like this.
--Sam
next prev parent reply other threads:[~2020-01-21 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 8:33 Question about dynamic minor number of misc device Zhenzhong Duan
2020-01-20 10:03 ` Arnd Bergmann
2020-01-20 10:25 ` Zhenzhong Duan
2020-01-20 10:59 ` Arnd Bergmann
2020-01-20 22:13 ` Theodore Y. Ts'o
2020-01-21 7:56 ` Arnd Bergmann
2020-01-21 16:31 ` Theodore Y. Ts'o
2020-01-21 17:54 ` Sam Hartman [this message]
2020-01-21 15:42 ` Greg Kroah-Hartman
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=tslh80o3dbm.fsf@suchdamage.org \
--to=hartmans@debian.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zhenzhong.duan@gmail.com \
/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