From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Benjamin Herrenschmidt <bh40@calva.net>,
Topi Kanerva <tkanerva@ees2.oulu.fi>,
linuxppc-dev@lists.linuxppc.org, daenzerm@student.ethz.ch,
SteffenH@hyperion-software.de, geert@linux-m68k.org
Subject: Re: sound again [was: Re: xf4 bug report]
Date: Wed, 26 Jul 2000 19:38:27 +0100 [thread overview]
Message-ID: <200007261838.TAA21891@hyperion.valhalla.net> (raw)
Hello all,
I'd say that a summary of today's (most interesting) thread is...
That:
(a) There's no real difference in behaviour between the back-port and the
2.2.17preXX monolithic dmasound module.
(b) The finger of blame is still pointing where I suspected (i.e. the mixer
abstraction).
OK -
1/ Is there an "official" maintainer?
2/ If not, is there anyone else (other than me) who wants to volunteer to
get to the bottom of it?
3/ Is there any reason to work on the 2.2.17preXX monolithic version or can
we continue with the 2.4.0-testxx with conditionals? (my preference as it
will transport directly to 2.4.0).
FYI: there is another party working on the I2C bus to bring support to the
iBook etc. - I've already made contact but he wants to get things going
before merging...
I *am* willing to have a go at doing a further split & debug job (certainly
on the pmac stuff). Is there any news as to whether the code is OK of the
other platforms?
Thanks everyone for your input & an exciting read after a long and tiring
day out of the office :-)
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-26 18:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-26 18:38 Iain Sandoe [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-26 18:29 sound again [was: Re: xf4 bug report] 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: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=200007261838.TAA21891@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=SteffenH@hyperion-software.de \
--cc=bh40@calva.net \
--cc=daenzerm@student.ethz.ch \
--cc=geert@linux-m68k.org \
--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).