From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by ozlabs.org (Postfix) with ESMTP id 3B901DDE0E for ; Tue, 8 Apr 2008 12:25:07 +1000 (EST) Received: by an-out-0708.google.com with SMTP id c37so391435anc.78 for ; Mon, 07 Apr 2008 19:25:05 -0700 (PDT) Message-ID: Date: Mon, 7 Apr 2008 20:25:05 -0600 From: "Grant Likely" Sender: glikely@secretlab.ca To: "Arnd Bergmann" Subject: Re: Question on mpc52xx_common.c In-Reply-To: <200804080414.42867.arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <47FAA0A8.7050602@genesi-usa.com> <200804080414.42867.arnd@arndb.de> Cc: linuxppc-dev@ozlabs.org, Detlev Zundel List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Apr 7, 2008 at 8:14 PM, Arnd Bergmann wrote: > On Tuesday 08 April 2008, Matt Sealey wrote: > > > Grant Likely wrote: > > > > > > Sure, why not? If the firmware has already set it up correctly and no > > > devices using it are in use, then the kernel should be okay. :-) > > > That said, I can't imagine choosing to not put the cdm node into the > > > device tree. > > > > *ahem* Efika. > > Maybe we should just give up on making the efika boot with its regular > device tree and instead add a boot wrapper that either fixes up the > data provided by its firmware or just adds a proper dt blob? Current kernels boot the Efika without any firmware scripts. prom_init.c is able to handle the few fixups that the kernel really wants to see. (So life is mostly happy in Efika land now. :-) Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.