From: "Zachary Kline" <klinez@onid.orst.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup drivers with 2.6.24
Date: Sat, 29 Mar 2008 21:25:46 -0700 [thread overview]
Message-ID: <000301c8921e$210f8ac0$0401a8c0@ZKMOBILE> (raw)
In-Reply-To: <20080330035126.GA24781@linux1>
Hi,
I must admit I'm not sure about the reasons behind all this. Call me a
traditionalist, but I've always associated /proc as being the main place
where such configurable kernel parameters are kept. Is there a reason
behind moving stuff out of there?
Thanks,
Zack.
----- Original Message -----
From: "William Hubbs" <williamh@gentoo.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, March 29, 2008 8:51 PM
Subject: Re: speakup drivers with 2.6.24
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This is being worked on as well. The goal is to move everything from
> /proc/speakup to /sys/module/speakup/parameters.
>
> On Sat, Mar 29, 2008 at 10:46:21PM -0400, Nick Stockton wrote:
>> with out /proc/speakup will there be another way to make shell scripts to
>> change the pitch, rate, key_echo, delay_time etc or will that ability be
>> gone?
>> Nick Stockton
>> ----- Original Message -----
>> From: "Kirk Reiser" <kirk@braille.uwo.ca>
>> To: "Speakup is a screen review system for Linux."
>> <speakup@braille.uwo.ca>
>> Sent: Saturday, March 29, 2008 6:07 PM
>> Subject: Re: speakup drivers with 2.6.24
>>
>>
>> > Auh yes, you have put your finger on one of the problems with the
>> > current git repository. Once a built-in synth is loaded there is no
>> > current way to switch to another built-in synth. Upon loading a
>> > module there's no way to switch to another built-in synth. If
>> > changing synths is necessary I would recommend builting them as
>> > modules which can be loaded and unloaded at will.
>> >
>> > We are working on bringing back the ability to change synths but it is
>> > not complete yet. I will turn my attention to that as soon as I have
>> > the cut and paste issue fixed and ready for testing. It's current
>> > status is that I can lock a machine with a single mark keystroke
>> > everytime ten out of ten tries! 'grin' Anyone want to test it?
>> >
>> >
>> >
>> > Kirk Reiser The Computer Braille Facility
>> > e-mail: kirk@braille.uwo.ca University of Western Ontario
>> > phone: (519) 661-3061
>> >
>> > _______________________________________________
>> > 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
>
> - --
> William Hubbs
> gentoo accessibility team lead
> williamh@gentoo.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.7 (GNU/Linux)
>
> iD8DBQFH7w4+blQW9DDEZTgRAms5AKCOMayalwLLA1aTESs0duwSANGIhQCgsHCR
> vL+XWIxiU0YTrkypBc8BoCc=
> =clj3
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Kirk Reiser
` Chuck Hallenbeck
` Nick Stockton
` William Hubbs
` Zachary Kline [this message]
` Daniel Dalton
` Samuel Thibault
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='000301c8921e$210f8ac0$0401a8c0@ZKMOBILE' \
--to=klinez@onid.orst.edu \
--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).