From: Dan Malek <dan@netx4.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-t1 & t3: dmasound
Date: Wed, 12 Jul 2000 10:52:47 -0400 [thread overview]
Message-ID: <396C863F.1E6285A6@embeddededge.com> (raw)
In-Reply-To: 200007121106.MAA13142@hyperion.valhalla.net
Iain Sandoe wrote:
>
> has anyone got dmasound_awacs to produce output under test1-ac21 or test3?
I am using test2-ac18 on my G4 server (workstation :-). It works
fine there. I haven't tried -test3 yet because of all of the other
bugs we are fixing.
By the way, I have some 48Khz modifications. Basically the inverse
of the expand functions. Anyone else doing this or attempting 48Khz
playback? Obviously record only works at 44.1Khz.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-12 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 11:06 2.4.0-t1 & t3: dmasound Iain Sandoe
2000-07-12 13:10 ` schinder
2000-07-12 14:52 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-12 13:16 Iain Sandoe
2000-07-12 15:55 Iain Sandoe
2000-07-12 16:35 ` Dan Malek
2000-07-12 18:07 Iain Sandoe
2000-07-12 18:19 ` Dan Malek
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=396C863F.1E6285A6@embeddededge.com \
--to=dan@netx4.com \
--cc=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).