From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from yow.seanm.ca (toronto-hs-216-138-233-67.s-ip.magma.ca [216.138.233.67]) by ozlabs.org (Postfix) with SMTP id 6AAF9DDDFA for ; Wed, 4 Mar 2009 11:29:35 +1100 (EST) Date: Tue, 3 Mar 2009 19:29:32 -0500 From: Sean MacLennan To: "Andrew Morton" Subject: Re: "leds: Add openfirmware platform device support" breaks sparc Message-ID: <20090303192932.31705cf7@lappy.seanm.ca> In-Reply-To: <20090303160906.9b30b376.akpm@linux-foundation.org> References: <20090303160906.9b30b376.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linuxppc-dev@ozlabs.org, sparclinux@vger.kernel.org, Trent Piepho , Richard Purdie List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 3 Mar 2009 16:09:06 -0800 "Andrew Morton" wrote: > afacit that interface is powerpc-only. Yes it is. You might want a CONFIG_PPC with that. It has been..... uhhhh carry the two... longer than I want to admit since I worked on a sparc. Would GPIO based LEDS make sense on a sparc platform? Is sparc used much in the embedded world? If yes, the of_register_platform_driver is just a nice wrapper. It would be trivial to either change it to work on sparc, or add the wrapper to the sparc includes. Cheers, Sean