All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: SteffenH@hyperion-software.de, daenzerm@student.ethz.ch,
	linuxppc-dev@lists.linuxppc.org
Subject: sound again [was: Re: xf4 bug report]
Date: Tue, 25 Jul 2000 15:42:08 +0100	[thread overview]
Message-ID: <200007251441.PAA21903@hyperion.valhalla.net> (raw)


On Tue, Jul 25, 2000, Steffen Haeuser wrote:
> Am 25-Jul-00 schrieb Iain Sandoe:
[...]
>>> Don't bother, that's a known problem as well. Blame Apple for not releasing
>>> specs for the latest sound chips...
>
>>which machine, which kernel (and, if possible, which sound chip - can be
>>found from the MacOS side if not the Linux) ?
>
> A "blue/white" G3 Mac first Revision. Kernel is: 2.2.17pre10-ben2 (with the
> older
> kernel Sound worked - at least I cannot remember that an error message during
> OS-booting happened, I never tried out the sound then.
> But the new Kernel is needed for the X Server V4)
>

OK, which was the last working version (prob. easiest is if you mail me
drivers/sound/dmasound.c).  I can diff that to what we have under 17preXX
and see if there are any clues...

I did a back-port of the 2.4.0-test4 dmasound stuff to 2.2.17pre10-ben2
(will check on pre13-ben1 later):
http://www.drfruitcake.com/linux/linuxppc.html

For some people this helps - but it seems that there are problems (some
minor, some major) across the board.   I would much prefer to work on the
2.4.0-testX code (more useful in the grand scheme of things) and so would
encourage you to test the back-port :-)

Having said that, I would expect your machine to work - I think it's an
AWACS sound chip of some variety?  If it has a DACA you'll have to wait..
:-(

Iain.

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

             reply	other threads:[~2000-07-25 14:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-25 14:42 Iain Sandoe [this message]
2000-07-25 22:50 ` sound again [was: Re: xf4 bug report] 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
  -- strict thread matches above, loose matches on Subject: below --
2000-07-25 15:58 Iain Sandoe
2000-07-25 23:30 ` Steffen Haeuser
2000-07-25 16:46   ` Franz Sirl
2000-07-25 18:35 Iain Sandoe
2000-07-26  1:59 ` Steffen Haeuser
2000-07-26  2:30 ` Steffen Haeuser
2000-07-25 18:53 Iain Sandoe
2000-07-26  2:31 ` Steffen Haeuser
2000-07-25 19:25 Iain Sandoe
2000-07-26  2:53 ` 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:53 Iain Sandoe
2000-07-26  3:51 ` Steffen Haeuser
2000-07-25 21:41 Iain Sandoe
2000-07-26 18:29 Iain Sandoe
2000-07-26 18:38 Iain Sandoe

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=200007251441.PAA21903@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=SteffenH@hyperion-software.de \
    --cc=daenzerm@student.ethz.ch \
    --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.