From: Steffen Haeuser <SteffenH@hyperion-software.de>
To: Iain Sandoe <iain@sandoe.co.uk>,
daenzerm@student.ethz.ch, linuxppc-dev@lists.linuxppc.org
Subject: Re: sound again [was: Re: xf4 bug report]
Date: Tue, 25 Jul 2000 17:50:21 -0500 [thread overview]
Message-ID: <yam8241.1084.150101632@mail.lf-online.de> (raw)
In-Reply-To: <200007251441.PAA21903@hyperion.valhalla.net>
Am 25-Jul-00 schrieb Iain Sandoe:
Hi!
>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...
Hmmm, I never touched the source code... the latest with working sound was
2.2.15
... well, actually I never tried the sound there... but I *think* this error
message
during bootup concerning sound came first with the new kernel (something about
dma
it said... if that helps I can look up the exact error message...).
>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
I guess the dmasnd-v2a.patch is the file to get ? Hmmm, is there also a Binary
Version available somewhere ? I do not have the latest Kernel Source on my
machine
and would like to avoid having to download it if possible...
BTW: Note about this page: at the start there is written
"PowerMac/Amiga/Atari/etc."
There is no such thing as a PowerAtari... there is a PowerAmiga, yes... but no
PowerAtari... Atari never got rid of the 68k CPU Architecture...
(and never, never name Amiga and Atari in one sentence :) )
>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..
>:-(
No clue what soundchip... it is a out-of-the-box "Blue/White" G3 Mac 1st
Revision...
no changes...
Steffen
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-25 22:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-25 14:42 sound again [was: Re: xf4 bug report] Iain Sandoe
2000-07-25 22:50 ` Steffen Haeuser [this message]
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=yam8241.1084.150101632@mail.lf-online.de \
--to=steffenh@hyperion-software.de \
--cc=daenzerm@student.ethz.ch \
--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).