From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 12 Sep 2007 12:03:39 +1000 From: David Gibson To: Grant Likely Subject: Re: FDT for Microblaze and PPC405 Message-ID: <20070912020339.GC16001@localhost.localdomain> References: <2057.3992-23959-31980099-1189527824@seznam.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: linuxppc-dev , Michal Simek List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Sep 11, 2007 at 11:09:07AM -0600, Grant Likely wrote: > On 9/11/07, Michal Simek wrote: > > For example emaclite driver needs information about turning on/off ping pong buffer... > > > > I would like to make this properly. > > FDT design is just as much art as it is science. It takes taste and > judgement to desgin a nice set of bindings. Your best option is to > draft something and post it to the linuxppc-embedded mailing list for > review. Yes, this is the preferred procedure, for now. > > And second question is on early console logs and timers setting. I read about aliases in FDT. I think that aliases can cover this setting. > > For example my design contain 4 serial line and I would like to know which serial line is set on early console. > > You use the chosen node for this. In the chosen node, you add a > property called "linux,stdout-path" which holds the path to your > console. You can look at examples under arch/powerpc/boot/dts/* Yes. Currently we don't use /aliases in the flat device tree. This is possibly a mistake, and something I'm thinking about changing. But, for now, linux,stdout-path in /chosen is the way to do this. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson