public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirk Reiser <kirk@braille.uwo.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Advice saught on math functions
Date: 12 Jul 2002 10:52:07 -0400	[thread overview]
Message-ID: <x7ptxtdmnc.fsf@speech.braille.uwo.ca> (raw)
In-Reply-To: <E17T1a9-00037I-00@the-village.bc.nu>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> You can't use FPU operations in the x86 kernel.

That answers that! 'grin'

> Maybe you should do this in user space ? Certainly the more I talk to people
> like Nicholas Pitre the more it seems to me that most of the kernel side
> stuff is the wrong approach.

I agree, except for providing access from the very beginning.  If
access can be provided which would never leave the blind user without
speech with a user space solution this would be ideal.

> Instead would it not be better to
> 
> -	Fix select on /dev/vcsa to work
> -	During init start up after init processes are running have
> 	the init tasks (or for that matter the kernel) fire up the
> 	speech helper

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?

> The fact 95% of the speakup drivers are going to spontaneously go 
> obsolete the moment serial ports vanish bothers me.

It bothers me as well.  I am currently working toward trying to make
them into standard drivers which can be loaded as modules.  We have
new synths coming along which are pci, usb and pcmcia that would be
easier to integrate if I used a standard driver interface.

I am getting a lot of pressure to make some sort of software synth
solution available for folks that cannot afford a hardware synth or
use a platform which doesn't support hardware synths.  I also have an
over all philosophy which requires me to provide solutions that
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.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

  reply	other threads:[~2002-07-12 14:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 14:08 Advice saught on math functions Kirk Reiser
2002-07-12 14:39 ` Alan Cox
2002-07-12 14:52   ` Kirk Reiser [this message]
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
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=x7ptxtdmnc.fsf@speech.braille.uwo.ca \
    --to=kirk@braille.uwo.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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