From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sipsolutions.net (crystal.sipsolutions.net [195.210.38.204]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 7669667BA2 for ; Wed, 9 Aug 2006 22:29:56 +1000 (EST) Message-ID: <44D9D532.9010200@sipsolutions.net> Date: Wed, 09 Aug 2006 14:29:38 +0200 From: Johannes Berg MIME-Version: 1.0 To: Takashi Iwai Subject: Re: [Alsa-devel] Linux v2.6.18-rc4, snd-aoa link error References: <20060808194651.GA29482@aepfle.de> <1155067429.26338.96.camel@mindpipe> <44D9B1BE.9070600@sipsolutions.net> <44D9C8E5.10109@sipsolutions.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-dev@ozlabs.org, Lee Revell , alsa-devel@alsa-project.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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