From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 1E2BEDDF55 for ; Thu, 25 Sep 2008 18:34:46 +1000 (EST) Subject: Re: MPC5200 PCI interrupt routing From: Benjamin Herrenschmidt To: Juergen Beisert In-Reply-To: <200809250951.15941.jbe@pengutronix.de> References: <200809221556.34353.jbe@pengutronix.de> <20080924181542.GA9690@secretlab.ca> <1222291345.8277.92.camel@pasglop> <200809250951.15941.jbe@pengutronix.de> Content-Type: text/plain Date: Thu, 25 Sep 2008 18:34:40 +1000 Message-Id: <1222331680.8277.181.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > But how to deal with platform specific things like (in this case) unknown > external clock or usage of the internal clock generator (= how to setup the > frequency divider)? You can always use the platform feature hacks like I do on powermac but we should definitely find something better. Maybe some hook in the OF wrapper ? Ben.