public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn Ervin at Home" <GlennErvin@cableone.net>
To: "Erik Heil" <eheil@patmedia.net>,
	"Speakup is a screen review system for Linux."
	<speakup@braille.uwo.ca>
Subject: Re: talking bios?
Date: Mon, 22 Dec 2003 20:18:34 -0600	[thread overview]
Message-ID: <007601c3c8fb$1138fdc0$6d00a8c0@desktop> (raw)
In-Reply-To: <010e01c3c88f$02da10f0$0201a8c0@eheil>

I think it would be great!
It frustrates me to wait for someone to come along to read the BIOS for me.
Glenn.

----- Original Message ----- 
From: "Erik Heil" <eheil@patmedia.net>
To: <igueths@comcast.net>; "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Sent: Monday, December 22, 2003 7:25 AM
Subject: Re: talking bios?


Hi.
Actually, it can be shown that such an item could be benificial to the
sighted community also.  There are times when using an actual display may be
impractical, say in a data center where space is at a premium.  I happen to
know for a fact that on Rs/6000 and P Series UNIX workstations that run AIX
(by IBM), this is possible, as you change the console port to one of the
serial ports.  That way you can use Winblows Terminal and you have access to
the Boot PROM, BIOS, etc.  But in all, point well taken. I'll be sure to
check out that Web site though.
----- Original Message ----- 
From: <igueths@comcast.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, December 22, 2003 2:08 AM
Subject: talking bios?


Hi all. I saw an article on Slashdot about a week or 2 ago about the
Linuxbios project, which can be found at linuxbios.org. This poses some
interesting ideas for the future...Theoretically, wouldn't it be possible
to integrate Speakup into the kernel that is used on the Rom chip? Also, I
think its a good idea to write to all the major motherboard manufacturers
about the Linuxbios project. And also explain how including a talking bios
in future motherboards would benifit the blind/visually impaired community.
And also explain how current bioses are inaccessible to visually impaired
people. What iare everyone's thoughts on this?

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  parent reply	other threads:[~ UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 igueths
 ` Erik Heil
   ` Sean McMahon
     ` Shaun Oliver
   ` Glenn Ervin at Home [this message]
     ` Luke Davis
 ` David Csercsics
 ` Garrett Klein
   ` David Csercsics
     ` Alex Snow
       ` David Csercsics
         ` Alex Snow
   ` Alex Snow
 ` randy turner
 ` Ralph W. Reid
 Gregory Nowak
 ` Jared
 ` Alex Snow
 igueths
 Dawes, Stephen
 ` Alex Snow
 Gregory Nowak
 Gregory Nowak
 ` Sean McMahon
 igueths
 Gregory Nowak
 ` Dave Hunt
   ` Alex Snow
 ` Ralph W. Reid
   ` Sean McMahon
 Gregory Nowak

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='007601c3c8fb$1138fdc0$6d00a8c0@desktop' \
    --to=glennervin@cableone.net \
    --cc=eheil@patmedia.net \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).