From: Kirk Reiser <kirk@braille.uwo.ca>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Advice saught on math functions
Date: 15 Jul 2002 10:10:53 -0400 [thread overview]
Message-ID: <x7n0sthyj6.fsf@speech.braille.uwo.ca> (raw)
In-Reply-To: <m1adotpats.fsf@frodo.biederman.org>
ebiederm@xmission.com (Eric W. Biederman) writes:
> The current architecture does allows for all BIOS parameters to be set
> from Linux so there is an accessibility gain there.
>
> Given the space constraints on the BIOS side, either a very small
> standalone speach synthsizer needs to be constructed, or more likely
> a set of tones (that can work like post codes) can be introduced
> to give a feel where in the boot process the BIOS is.
A small synthesizer is one of the things I am trying to work on.
After reading all the wonderful suggestions I've seen here on this
thread I'm not sure just how I'll fit it all together. Key tones to
indicate when particular events have taken place with the pc's speaker
could be very useful. We use the bell character to indicate the lilo
boot prompt currently. It could be expanded to indicate a lot of
useful events if built-in to the BIOS.
A user space program to give access to the cmos bios settings is
another feature which would be very useful. Currently there is no way
for a blind person to set up his/her own bios under the other O.S but
it could conceivably be done under Linux.
A few folks have written me suggesting the possibility of using the pc
speaker as the output for a low quality speech synth. I am skeptical
about the feasability of this but it would give everyone blind or
otherwise useful feedback possibly on systems which are headless. I
am not exactly sure yet just how small I can get a useable speech
synth. That is the whole reason for this thread in the first place.
>
> After that a nice bootloader based on the Linux kernel with a real
> user space can be loaded from the hard drive where there is plenty of
> room. Everything that possibly could would need to be built as
> modules to decrease the time to user space, and to allow as many
> messages to be processed by the speech synthesizer.
Is there an organized linuxbios project? If so, could someone give me
a pointer please.
Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
next prev parent reply other threads:[~2002-07-15 14:08 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
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 [this message]
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=x7n0sthyj6.fsf@speech.braille.uwo.ca \
--to=kirk@braille.uwo.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--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®