linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Topi Kanerva <tkanerva@ees2.oulu.fi>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: sound again [was: Re: xf4 bug report]
Date: Wed, 26 Jul 2000 15:10:18 +0200	[thread overview]
Message-ID: <20000726131018.5434@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0007261551420.7775-100000@stekt6>


>so this behaviour is also happening on Burgundy. I've got an AWACS rev 3
>here in my Pismo (device-tree name for the chip is 'screamerawacs')
>and everything else works for me _except_ the damned built-in speakers.
>as long as I don't have any external speakers to connect to, this is _very_
>annoying, I have to boot to MacOS to listen to CD's etc etc... first I
>thought the problem was in the new version of the sound chip, but since
>Burgundies seem to have the same problem, I'm not so sure about it anymore.
>However, poking around the mixer code doesn't shed any more light into the
>problem.
>
>Now, what do the Burgundy and AWACS rev.3 have in common? Most certainly
>not the registers.

New "screamer" revisions of AWACS have more registers than defined in the
current Linux driver. I'm not sure this is the cause of our problem, but
it could be. I thinking about a problem setting up an external amplifier.

Note also that a working sound driver wont give you CD playback "out of
the box". On all new machines, the CD audio output is _not_ wired to the
sound chip. You have to use a player software that actually reads the
digital audio datas from the CD via ATAPI and sends them back to the
sound driver. There's an XMMS plugin for that, I managed to use it but it
still contains a lot of bugs.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-26 13:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-25 19:30 sound again [was: Re: xf4 bug report] 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 [this message]
2000-07-26 13:13       ` Topi Kanerva
  -- strict thread matches above, loose matches on Subject: below --
2000-07-26 18:38 Iain Sandoe
2000-07-26 18:29 Iain Sandoe
2000-07-25 21:41 Iain Sandoe
2000-07-25 19:53 Iain Sandoe
2000-07-26  3:51 ` Steffen Haeuser
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=20000726131018.5434@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tkanerva@ees2.oulu.fi \
    /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).