From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Derrik Pates <dpates@dsdk12.net>
Cc: Dave Ray <g4tinker@yahoo.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Sound on G4 tower, success
Date: Wed, 24 Oct 2001 12:18:43 +0200 [thread overview]
Message-ID: <20011024101843.30384@smtp.adsl.oleane.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110232014430.17119-100000@andromeda.dsdk12.net>
>
>Yeah. Apparently there's some weird magic crap that you have to do to make
>the internal speaker actually work. Far as I know, no one's decoded how to
>actually make it work in Linux, and no one seems overly interested in
>figuring out how to anyway (since the internal speaker isn't anything
>startling sound-quality-wise anyhow).
>
>> regardless of whether a plug is connected. Is this a
>> bug? (Don't get me wrong, I'm delighted that it
>> works!)
>
>No, as I noted above, it's not a bug, it's just something we don't yet
>know how to control, and no one's felt it pressing to figure it out (and
>the lack of documentation on it would make it something of a task to
>figure out).
Well, I think I know how to control it. It's just that I don't have
the HW to test on ;)
I'll try to hack something soon.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-24 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 3:38 Sound on G4 tower, almost Dave Ray
2001-10-23 3:48 ` Derrik Pates
2001-10-23 18:21 ` Dave Ray
2001-10-23 18:29 ` Derrik Pates
2001-10-23 23:38 ` Sound on G4 tower, success Dave Ray
2001-10-24 2:19 ` Derrik Pates
2001-10-24 10:18 ` Benjamin Herrenschmidt [this message]
2001-10-24 10:48 ` Lars Brinkhoff
2001-10-26 12:08 ` Benjamin Herrenschmidt
2001-10-27 3:08 ` James Baughman
2001-10-28 18:59 ` Lars Brinkhoff
2001-10-28 20:39 ` Benjamin Herrenschmidt
2001-10-29 9:03 ` Lars Brinkhoff
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=20011024101843.30384@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=dpates@dsdk12.net \
--cc=g4tinker@yahoo.com \
--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).