From: Dan Malek <dan@netx4.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Dan Malek <dan@netx4.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.0-t1 & t3: dmasound
Date: Wed, 12 Jul 2000 12:35:06 -0400 [thread overview]
Message-ID: <396C9E3A.B1775C43@embeddededge.com> (raw)
In-Reply-To: 200007121558.QAA32590@hyperion.valhalla.net
Iain Sandoe wrote:
> Cool... can you tell me what AWACS rev you have working?
> (we have one report of rev == OK) My rev 3 (!OK)
Here is what I have been able to discover by poking around in the
device-tree and in memory. It has "davbus" and "sound", so it isn't
Burgandy. The value of awacs_revision in memory appears to be 3......
Now, when I say "works"......I have lots of my own custom audio
programs (lots of hacks, nothing interesting) and I don't typically
use any of the mixer or other playback programs (except mpeg3 players).
I can control speaker/line volume, enable disable speaker. I am
really interested in audio processing (hence the G4 :-), and use
the output to just validate things sound correct.
> [I'm struggling right now to try and get a common code base between
> 2.2.17prexx & 2.4.0 - to avoid confusion on *my* part :-)]
You mean it won't just "drop in" (just kidding, been there :-). Good
Luck...Have fun!
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-12 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 15:55 2.4.0-t1 & t3: dmasound Iain Sandoe
2000-07-12 16:35 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-12 18:07 Iain Sandoe
2000-07-12 18:19 ` Dan Malek
2000-07-12 13:16 Iain Sandoe
2000-07-12 11:06 Iain Sandoe
2000-07-12 13:10 ` schinder
2000-07-12 14:52 ` 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=396C9E3A.B1775C43@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.