From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Yaroslav Halchenko <yoh@psychology.rutgers.edu>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: sound problem on recent PowerBook5,8 MacRISC3
Date: Thu, 09 Feb 2006 16:04:41 +1100 [thread overview]
Message-ID: <1139461481.5003.34.camel@localhost.localdomain> (raw)
In-Reply-To: <1139460919.30058.16.camel@mindpipe>
On Wed, 2006-02-08 at 23:55 -0500, Lee Revell wrote:
> On Thu, 2006-02-09 at 09:29 +1100, Benjamin Herrenschmidt wrote:
> > On Wed, 2006-02-08 at 11:00 -0500, Yaroslav Halchenko wrote:
> > > Dear Kernel People,
> > >
> > > Sound fails to work on the PowerBook laptop
> > > information on which could be found from
> > > http://www.onerussian.com/Linux/bugs/bug.sound/
> > >
> > > On 2.6.16-rc1 and got
> > > dmasound_pmac: couldn't find a Codec we can handle
> > > ....
> > > snd: Unknown layout ID 0x52
> > > (and ALSA failed to find any device)
> >
> > The sound chipset on these new machines isn't yet supported.
> >
>
> Please file a feature request in the ALSA bugzilla, so this won't get
> lost. Please include pointers to any Darwin code or any other docs you
> think might help.
>
> https://bugtrack.alsa-project.org/alsa-bug/login_select_proj_page.php?ref=bug_report_advanced_page.php
Well, I have started tracking down all chipset models and all ways they
are routed in the different mac models. It's a total mess but I'm slowly
getting there. I intend to rewrite a new driver that can handle properly
those new scenarios of multiple i2c busses and multiple codecs per bus,
among others.
Ben.
prev parent reply other threads:[~2006-02-09 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 16:00 sound problem on recent PowerBook5,8 MacRISC3 Yaroslav Halchenko
2006-02-08 22:29 ` Benjamin Herrenschmidt
2006-02-09 4:55 ` Lee Revell
2006-02-09 5:04 ` Benjamin Herrenschmidt [this message]
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=1139461481.5003.34.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=yoh@psychology.rutgers.edu \
/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.