Messages in this thread | | | Date | Mon, 4 Feb 2008 10:06:17 -0800 | From | Greg KH <> | Subject | Re: [PATCH] Basic braille screen reader support |
| |
On Mon, Feb 04, 2008 at 05:24:41PM +0000, Samuel Thibault wrote: > Hello, > > Greg KH, le Mon 04 Feb 2008 09:10:08 -0800, a ?crit : > > On Mon, Feb 04, 2008 at 03:18:43AM +0000, Samuel Thibault wrote: > > > This adds a minimalistic braille screen reader support. > > > This is meant to be used by blind people e.g. on boot failures or when / > > > cannot be mounted etc and thus the userland screen readers can not work. > > > > Will this api work with the SpeakUp kernel drivers? Are the hooks > > sufficient for what those drivers are expecting? > > SpeakUp and this are quite independant (though they will probably both > end up in the drivers/a11y/ directory), at least just because the way > they review the screen is very different. Speech synthesis' matter is > the time to say things, while braille's matter is the space to show > things. > > However, they share the same low-level primitives: the recently added > keyboard and vc notifiers, screen_glyph(), inverse_translate(), > kd_mksound, etc.
I guess I'm worried that the hooks that you add here will not be usable by speakup, and we'll have to add more in places close to this, but not quite the same.
I know speaking and "showing" are two different things, but they both require the same data flow going into them in order to achieve their goals, I just don't want to see this work being done without considering both needs.
But, if you feel that both will work properly with these limited exports, I have no objections.
thanks,
greg k-h
| |