From: Johannes Berg <johannes@sipsolutions•net>
To: Takashi Iwai <tiwai@suse•de>
Cc: linuxppc-dev@ozlabs•org, Lee Revell <rlrevell@joe-job•com>,
alsa-devel@alsa-project•org
Subject: Re: [Alsa-devel] Linux v2.6.18-rc4, snd-aoa link error
Date: Wed, 09 Aug 2006 14:29:38 +0200 [thread overview]
Message-ID: <44D9D532.9010200@sipsolutions.net> (raw)
In-Reply-To: <s5h7j1idrvf.wl%tiwai@suse.de>
Takashi Iwai wrote:
>> Yeah, I really should know :) But I'm not sure at the moment, and the
>> powermac I own is a few hundred kilometers away...
>>
>
> Don't worry, we can wait :)
>
Maybe someone on linuxppc-dev can quickly check? Does a G5 use
I2C_POWERMAC for access to the codecs? I think it does, but there are
other I2C busses as well.
>> That looks good to me, and should get rid of the build failure. However,
>> if one doesn't configure I2C_POWERMAC, no codec will ever be found at
>> runtime.
>>
>
> Yes, that's my concern, too.
>
I'm not sure how much we should force the users to a sensible
configuration ;) But I suppose selecting I2C_POWERMAC is fine for all
relevant machines for now.
johannes
next parent reply other threads:[~2006-08-09 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0608061127070.5167@g5.osdl.org>
[not found] ` <20060808194651.GA29482@aepfle.de>
[not found] ` <1155067429.26338.96.camel@mindpipe>
[not found] ` <s5hoduudypc.wl%tiwai@suse.de>
[not found] ` <44D9B1BE.9070600@sipsolutions.net>
[not found] ` <s5hk65idwia.wl%tiwai@suse.de>
[not found] ` <44D9C8E5.10109@sipsolutions.net>
[not found] ` <s5h7j1idrvf.wl%tiwai@suse.de>
2006-08-09 12:29 ` Johannes Berg [this message]
2006-08-09 12:31 ` [Alsa-devel] Linux v2.6.18-rc4, snd-aoa link error Takashi Iwai
2006-08-09 12:38 ` Johannes Berg
2006-08-09 12:52 ` Takashi Iwai
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=44D9D532.9010200@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=rlrevell@joe-job$(echo .)com \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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