From: Dan Malek <dmalek@jlc.net>
To: Ryan Nielsen <ran@krazynet.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: esound for PPC
Date: Tue, 26 Oct 1999 10:10:42 -0400 [thread overview]
Message-ID: <3815B661.F4D901DE@jlc.net> (raw)
In-Reply-To: 19991025222905.A32256@gondolin.asf
Ryan Nielsen wrote:
> can someone fix that hissing problem ......
I did that in the 2.3.xx kernel while adding the recording stuff. At
the time the 2.2.x was "frozen" to updates so I didn't perform the same
updates in the 2.2.x tree. I guess I can go back and do that, although
there has been lots of activity around this driver lately, including
threats of re-writes.
I have some updates as well, so how about everyone working on something
in this driver speak up and we coordinate this......
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-26 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 3:48 esound for PPC Eric Dorland
1999-10-03 4:03 ` Elliot Lee
1999-10-03 18:54 ` Eric Dorland
1999-10-03 19:23 ` Tom Rini
1999-10-03 21:46 ` Elliot Lee
1999-10-04 6:27 ` Geert Uytterhoeven
1999-10-04 15:58 ` Elliot Lee
1999-10-05 8:54 ` Benjamin Herrenschmidt
1999-10-05 11:36 ` Elliot Lee
1999-10-06 0:40 ` Eric Dorland
1999-10-11 6:06 ` Eric Dorland
1999-10-11 19:43 ` Eric Dorland
1999-10-11 20:09 ` Tom Rini
1999-10-12 3:03 ` Ryan Nielsen
1999-10-12 3:10 ` Tom Rini
[not found] ` <19991014193940.A1143@HSE-MTL-ppp4505.qc.sympatico.ca>
[not found] ` <19991017190502.A13068@gondolin.asf>
[not found] ` <19991023152110.A525@HSE-MTL-ppp4445.qc.sympatico.ca>
[not found] ` <19991023203334.A26715@gondolin.asf>
[not found] ` <19991024223141.A758@HSE-MTL-ppp4328.qc.sympatico.ca>
1999-10-26 5:29 ` Ryan Nielsen
1999-10-26 6:30 ` recv programming problem Morningstar
1999-10-26 14:10 ` Dan Malek [this message]
1999-10-12 3:10 ` esound for PPC Eric Dorland
1999-10-12 3:20 ` Tom Rini
1999-10-12 4:26 ` Eric Dorland
1999-11-02 18:01 ` Elliot Lee
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=3815B661.F4D901DE@jlc.net \
--to=dmalek@jlc.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ran@krazynet.com \
/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 NNTP newsgroup(s).