From: "Angelo Sonnesso" <asonnesso@coastalnet.com>
To: <speakup@braille.uwo.ca>
Subject: Re: development questions
Date: Sun, 27 Jan 2002 07:09:50 -0500 [thread overview]
Message-ID: <008001c1a730$a0b882c0$7f78f5cd@angeloso> (raw)
In-Reply-To: <x7g04sh6oq.fsf@speech.braille.uwo.ca>
Is there any documentation explaining how to change speakup speech
parameters?
We don't use loadspk/dumpspk anymore. That
> functionally is totally handled by the /proc filesystem these days. I
> am pretty sure the tutorial states that the actual declarations are in
> speakup.h. Which is where they are. There was also an article I
> wrote a few years ago about how to write functions to be included but
> I don't seem to be able to find it. What functions do you want added?
> How much experience do you have kernel coding? I am not trying to
> discourage you but there are things which will bite you in the ass if
> you aren't good and familiar with kernel issues. We can always use
> extra hands though so if you're willin to put in the work it will be
> nice having you on board. I also recommend you get on the reflector
> if that is the case. If you don't know about the reflector, then I
> recommend you read the web site at linux-speakup.org. It would have
> told you the lt was covered as well.
>
> Kirk
>
> --
>
> 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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Peterson
` Kirk Reiser
` Chris Peterson
` rmann
` Thomas Ward
` Chris Peterson
` Kirk Reiser
` Chris Peterson
` Angelo Sonnesso [this message]
` Geoff Shang
` Gregory Nowak
` Geoff Shang
` Buddy Brannan
` Thomas Ward
` Kirk Wood
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='008001c1a730$a0b882c0$7f78f5cd@angeloso' \
--to=asonnesso@coastalnet.com \
--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).