On Sat, 2 Jul 2016, kendell clark wrote: > What he means by staging is the kernel modules that are considered > unstable for whatever reason. It usually only contains brand new > kernel modules while they're being developed and they're moved out > into the main kernel. But speakup has never made it out. I don't know > why, but I've heard that it's because of the way it access older > serial based synthesizers, communicating raw commands instead of using > the /dev/ttyusb0 and /dev/ttys0 and other serial devices.
Speakup really ought to move out of the kernel entirely and be made to work as a regular process like Brltty does. Yes there might be some politics behind this, but it is by far a flexibility and ease of maintenance issue. And it wouldn't be hard for the kernel to export the needed information to user space. Speakup already relies on special notifier hooks located in the core kernel console code to figure out what to speak. Those same hooks could be used to transmit the same information to any interested user space process as well. Nicolas _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
