Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> This is how Nicholas stuff works, you can still get the kernel messages
> by scrolling back. I'm told this meets S508.
I don't give two shits about S508. For one thing that is a
U.S. statute. It has no relevance here.
> Actually some of this is true for sighted people. You only get console
> messages after PCI is initialised, until then they are queued away or
> only on serial console.
Even though, pci gets initialized pretty early in the boot sequence
doesn't it? Considerably before init?
>
> If you are using a conventional BIOS then the first kernel messages being
> readable as they occur versus just after seems to have only a little value.
> If you have a fully accessible LinuxBIOS thats something quite different.
> In that case can you use a Linuxbios hook for the console speech until
> user space takes over ?
I don't really know. I haven't had time to really get into the BIOS
accessibility yet. I know for serial synths we can turn serial on in
lilo and at least hear what is going on. Without modifying lilo for
each synth other than serial we have no way of knowing whether we have
the full lilo prompt or what.
If we could modify a linux BIOS and then flash it onto any flashable
BIOS that would be really useful.
Kirk
--Kirk Reiser The Computer Braille Facility e-mail: kirk@braille.uwo.ca University of Western Ontario phone: (519) 661-3061 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:22 EST