mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: kirk@braille.uwo.ca (Kirk Reiser)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Advice saught on math functions
Date: Fri, 12 Jul 2002 16:32:19 +0100 (BST)	[thread overview]
Message-ID: <E17T2P5-0003DF-00@the-village.bc.nu> (raw)
In-Reply-To: <x7ptxtdmnc.fsf@speech.braille.uwo.ca> from "Kirk Reiser" at Jul 12, 2002 10:52:07 AM

> Can you give me more details?  I certainly don't mind looking into
> this as a possible solution.  Are you willing to give up seeing
> anything on the screen until init gets started?

This is how Nicholas stuff works, you can still get the kernel messages
by scrolling back. I'm told this meets S508.

> include speech and review capabilities from power up to power down.
> Open BIOS and Linux for the first time ever can provide a way for the
> blind community to not be a second class citizen to information
> access.  I am afraid that if I just take the emacspeak approach to
> accessibility then my community will stay beholding to others for
> their access to available information.  I am sorry about the soap-box
> preaching but it is a fundamental problem with just user space
> solutions.

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.

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 ?

Alan

  reply	other threads:[~2002-07-12 15:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 14:08 Kirk Reiser
2002-07-12 14:39 ` Alan Cox
2002-07-12 14:52   ` Kirk Reiser
2002-07-12 15:32     ` Alan Cox [this message]
2002-07-12 16:04       ` Kirk Reiser
2002-07-12 16:31         ` Alan Cox
2002-07-12 16:21           ` Dave Jones
2002-07-15  9:46           ` Eric W. Biederman
2002-07-16  5:26             ` H. Peter Anvin
2002-07-15 10:03         ` Eric W. Biederman
2002-07-15 14:10           ` Kirk Reiser
2002-07-15 16:38             ` Eric W. Biederman
2002-07-12 15:46     ` Nicolas Pitre
2002-07-12 16:30       ` Kirk Reiser
2002-07-12 17:03         ` Nicolas Pitre
2002-07-12 16:22   ` J.A. Magallon
2002-07-12 16:49     ` William Park
2002-07-13 14:00   ` Pavel Machek
2002-07-13 17:10     ` Alan Cox
2002-07-12 14:46 ` Richard B. Johnson
2002-07-12 15:42 ` Sandy Harris
2002-07-12 16:46   ` Kirk Reiser
2002-07-14  0:20   ` Erik Andersen
2002-07-14 14:17     ` Sandy Harris
2002-07-14 16:49       ` Albert D. Cahalan
2002-07-14 17:01       ` Thunder from the hill

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=E17T2P5-0003DF-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=kirk@braille.uwo.ca \
    --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®