From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <1162284176.25682.320.camel@localhost.localdomain> References: <200610292310.k9TNAHXZ013852@post.webmailer.de> <7BDB728E-0CC2-4940-9856-B496022F3482@kernel.crashing.org> <4546F7DE.6070104@bplan-gmbh.de> <1162280335.25682.302.camel@localhost.localdomain> <4547086D.2050808@bplan-gmbh.de> <1162284176.25682.320.camel@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3BDF1DB1-94A9-4538-A785-74D16827496D@kernel.crashing.org> From: Kumar Gala Subject: Re: [PATCH 1/2] Add MPC52xx Interrupt controller support for ARCH=powerpc Date: Tue, 31 Oct 2006 08:34:46 -0600 To: Benjamin Herrenschmidt Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org, sl@bplan-gmbh.de, sha@pengutronix.de List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Oct 31, 2006, at 2:42 AM, Benjamin Herrenschmidt wrote: > On Tue, 2006-10-31 at 09:25 +0100, Nicolas DET wrote: > >> Ok. By the way, the mbar is include as property in our OpenFrimware. >> Moreover, the G2CORE CPU has a new SPR 'MBAR' which is the >> MBAR ;-). It >> would maybe make sense to create a new file >> (arch/powerpc/sysdev/mpc52xx.c) which would contain chip specific >> code. >> >> Like mpc52xx_get_mbar(), mpc52xx_get_ipbfreq(), etc... >> >> I updated a bit the patches. I applied Dale requests. >> My kernel still compiles and boots. ;-) >> >> Should I post the new patches? > > Sure. > >> About the headers thingy. Should I split them directly in the >> patch, or >> this should be done by others later on? > > Don't bother that much about splitting the headers. I personally don't > mind. I think we should at least split out the interrupt stuff into a arch/ powerpc/sysdev/mpc52xx_pic.h, but we can make the change in the future. - k