linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@ozlabs.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: PowerBook5,4 -- no sound?
Date: Tue, 18 Apr 2006 07:50:57 +1000	[thread overview]
Message-ID: <1145310657.3912.23.camel@localhost.localdomain> (raw)
In-Reply-To: <jey7y3dgzw.fsf@sykes.suse.de>

On Mon, 2006-04-17 at 23:33 +0200, Andreas Schwab wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> 
> > On Mon, 2006-04-17 at 15:45 +0200, Andreas Schwab wrote:
> >> request_mem_region(80000000 - 80000fff, i2sbus control)
> >> 
> >>       80000000-8007ffff : 0.80000000:mac-io
> >>         8000002c-8000002f : 0.0000004c:fans
> >>         80000030-80000033 : 0.0000004c:fans
> >>         80000034-80000037 : 0.0000004c:fans
> >>         8000004c-8000004f : 0.0000004c:fans
> >>         80000050-8000008a : 0.00000050:gpio
> >
> > Johannes,
> >
> > Look like the bugs in the device-tree I told you about ...
> 
> There is special support for K2-Keylargo in sound/ppc/pmac.c, is it that
> what you mean?

Yes, though it doesn't seem to affect all K2 based models, thus in this
regard, snd-powermac isn't bug free neither ... Apple keeps fucking up
their device-tree in all sort of funny ways.. at least kept, hopfeully
this is finished now :)

Ben.

  reply	other threads:[~2006-04-17 21:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-16 14:39 PowerBook5,4 -- no sound? Paul Collins
2006-04-16 15:49 ` Andreas Schwab
2006-04-16 20:43   ` Benjamin Herrenschmidt
2006-04-16 23:33     ` Andreas Schwab
2006-04-16 23:54       ` Benjamin Herrenschmidt
2006-04-17  0:27         ` Andreas Schwab
2006-04-17  0:30           ` Benjamin Herrenschmidt
2006-04-17 13:45             ` Andreas Schwab
2006-04-17 20:51               ` Benjamin Herrenschmidt
2006-04-17 20:57                 ` Johannes Berg
2006-04-17 21:33                 ` Andreas Schwab
2006-04-17 21:50                   ` Benjamin Herrenschmidt [this message]
2006-05-17 10:34                 ` PowerMac7,3 sound (was: PowerBook5,4 -- no sound?) Johannes Berg
2006-05-17 19:32                   ` Andreas Schwab
2006-05-17 20:14                     ` Andreas Schwab
2006-05-18 10:39                     ` Johannes Berg
2006-05-18 12:48                       ` Andreas Schwab
2006-05-18 21:49                         ` Benjamin Herrenschmidt
2006-05-19 12:47                         ` Johannes Berg
2006-05-19 13:30                           ` Andreas Schwab
2006-05-19 13:48                             ` Johannes Berg
2006-05-19 14:30                               ` Andreas Schwab
2006-05-19 14:32                                 ` Johannes Berg
2006-05-18  3:13                   ` Benjamin Herrenschmidt
2006-04-16 20:43 ` PowerBook5,4 -- no sound? Benjamin Herrenschmidt
2006-04-17  0:34   ` Paul Collins
2006-04-17  0:51     ` Paul Collins

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=1145310657.3912.23.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=schwab@suse.de \
    /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).