From: "Iain Sandoe" <iain@sandoe.co.uk>
To: SteffenH@hyperion-software.de, linuxppc-dev@lists.linuxppc.org
Subject: Re: sound again [was: Re: xf4 bug report]
Date: Tue, 25 Jul 2000 22:41:05 +0100 [thread overview]
Message-ID: <200007252142.WAA27135@hyperion.valhalla.net> (raw)
Hi Steffen,
I think we should take this off-list... (it's getting to be a bit
long-winded)...
Ben, Franz (if you are 'listening' or have an interest) let me know and I'll
cc you otherwise we'll report back when there's some solution.
>>1. what does dmesg now show?
>
> DMA sound driver core [Ed 3]
Good that's definitely the back-port code...
> 4 Buffers of 32 K for Output
> Same for Input
You've abbreviated this (I hope)...
> AWACS rev 100
>
> registers:
>
> 1400 782d 7810 0001 00a1 0021 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 0000 0000 4000 0000 26bb 0010 0000 0002
> 0001 0000 0000 0000 0000 0000 0000 0000
Good, it's recognised your Burgundy chip...
>>2. have you tried headphones/versus built-in speaker? (others have reported
>>a problem here - which is why the finger of blame is currently pointing at
>>the mixer abstraction)...
>
> Up to now only built-in speakers. Will try with headphones :)
>
[snip]
The rest looks OK too...
Now, I'll have a quick look at the amp-enable code (again) - that did have a
problem at one point.
I'm out (on paid work :) tomorrow... so not much action 'till late...
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-25 21:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 21:41 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-26 18:38 sound again [was: Re: xf4 bug report] Iain Sandoe
2000-07-26 18:29 Iain Sandoe
2000-07-25 19:53 Iain Sandoe
2000-07-26 3:51 ` Steffen Haeuser
2000-07-25 19:30 Iain Sandoe
2000-07-26 14:37 ` Steffen Haeuser
2000-07-26 9:59 ` Michel Dänzer
2000-07-26 11:09 ` Benjamin Herrenschmidt
2000-07-26 12:55 ` Topi Kanerva
2000-07-26 13:10 ` Benjamin Herrenschmidt
2000-07-26 13:13 ` Topi Kanerva
2000-07-25 19:25 Iain Sandoe
2000-07-26 2:53 ` Steffen Haeuser
2000-07-25 18:53 Iain Sandoe
2000-07-26 2:31 ` Steffen Haeuser
2000-07-25 18:35 Iain Sandoe
2000-07-26 1:59 ` Steffen Haeuser
2000-07-26 2:30 ` Steffen Haeuser
2000-07-25 15:58 Iain Sandoe
2000-07-25 23:30 ` Steffen Haeuser
2000-07-25 16:46 ` Franz Sirl
2000-07-25 14:42 Iain Sandoe
2000-07-25 22:50 ` Steffen Haeuser
2000-07-25 18:49 ` Geert Uytterhoeven
2000-07-26 18:59 ` Steffen Haeuser
2000-07-26 17:27 ` Michael Schmitz
2000-07-27 0:49 ` Steffen Haeuser
2000-07-26 17:58 ` Michael Schmitz
2000-07-26 18:48 ` Michel Dänzer
2000-07-26 19:28 ` Michael Schmitz
2000-07-27 1:29 ` Steffen Haeuser
2000-07-27 12:13 ` Geert Uytterhoeven
2000-07-27 20:44 ` Steffen Haeuser
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=200007252142.WAA27135@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=SteffenH@hyperion-software.de \
--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).