From: Deedra Waters <dmwaters@tampabay.rr.com>
To: speakup@braille.uwo.ca
Subject: Re: timer problems
Date: Tue, 6 Nov 2001 16:03:25 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1011106160301.15847A-100000@deedra> (raw)
In-Reply-To: <Pine.LNX.3.96.1011106155455.15658A-100000@deedra>
Ok I'm stupid... it was right in front of me and I didn't see it.
On Tue, 6 Nov 2001, Deedra Waters wrote:
> Ok, I've found the alsa drivers, and the libraries, but I don't see
> anything on the websight that says anything about utilities in the ftp
> directories, if someone could point me in the right direction I'd
> appreciate it.
>
>
> On Tue, 6 Nov 2001, Barry Pollock wrote:
>
> > use the alsa drivers.
> > they are compiled separately from the rest of the kernel. because the
> > timing is esential for the digital, speakup effects the kernel's timing in
> > order to perform its functions. alsa uses its own libraries which allows
> > it to perform independantly.
> > although this may not be exactly what happens, use the alsa drivers to
> > build your sound modules.
> > they are available from www.alsa-project.org you can download the drivers
> > the libraries utilites and anything you may need from ftp.alsa-project.org
> > build the drivers first
> > then the libries
> > then the utilities.
> > do not mix the versions
> >
> >
> >
> > _______________________________________________
> > 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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Barry Pollock
` Deedra Waters
` Deedra Waters [this message]
` Shaun Oliver
` Frank Carmickle
` Shaun Oliver
Watson, Keith
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=Pine.LNX.3.96.1011106160301.15847A-100000@deedra \
--to=dmwaters@tampabay.rr.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).