From: "Chris Peterson" <capeterson@visi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: development questions
Date: Sat, 26 Jan 2002 21:09:59 -0600 [thread overview]
Message-ID: <000f01c1a6e0$1bbc1280$6801030a@greatmachine> (raw)
In-Reply-To: <x7g04sh6oq.fsf@speech.braille.uwo.ca>
> That tutorial is quite out of date but it covers the basic issues
> still quite well. 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
I'll go back through it and look, but I didn't see it the two or three times
I read that over.
> 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?
I'm not sure what I want added, if anything... I was just curious to know
how it worked. I have no experience with kernel coding, but this seemed
like as good a reason to learn as anything.
> 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
I don't doubt that, but it is good to learn these things... I'm in my last
semester of a computer science degree and, while I'm in the habit of
studying, I figured I might as well learn about some of this stuff.
> 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
I know about the reflecter, and I'm pleased to know about others using
SpeakFreely. Some friends and I run a reflecter on fox.sector14.net:2074
for our own enjoyment. Its a great tool, but the university just put in nat
to the dorms so I've been cut off from SpeakFreely until I can set up a VPN
to the outside or something else. I tried using SSH port forwarding, but
that didn't work so now I'm going to try a pptp connection to a friends box
to get a clear shot out the firewall. I just have to wait for him to set up
his machine to do it.
Thanks again and I'm sure that after I've learned a little more about how
the kernel is put together, I'll probably be able to be of some help to you.
Chris
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 [this message]
` Angelo Sonnesso
` 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='000f01c1a6e0$1bbc1280$6801030a@greatmachine' \
--to=capeterson@visi.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).