Re: FDT for Microblaze and PPC405

Re: FDT for Microblaze and PPC405

[Grant Likely]

On 9/11/07, Michal Simek <Monstr@seznam.cz> wrote:
> Hi Grant,

(Adding linuxppc-dev mailing list to CC list because we're discussing
FDT issues)

> I made EDK repository file for generation dts file from Xilinx design. I sent it to Wolfgang and Steve this week.
> It is in the same config file as I use for configuration Microblaze for U-BOOT. If you want I can send you this repository files.

Yes, please do.

> And I start with redesigning Linux kernel for Microblaze. I ported some peripherals as timer and intc etc.
> But for some peripherals I need better configuration.
>
> I have no time to read information about fdt. Can you tell me what labels I can use?

Steve has already done a bunch of work in this direction on
microblaze, I would converse with him.

>
> 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.

>
> 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/*

Cheers,
g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

Re: FDT for Microblaze and PPC405

[David Gibson]

On Tue, Sep 11, 2007 at 11:09:07AM -0600, Grant Likely wrote:
> On 9/11/07, Michal Simek <Monstr@seznam.cz> 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

Re: FDT for Microblaze and PPC405

[Michal Simek]

Hi David and Grant

>> > 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.

OK. Science is good for me because I am looking for theme for dissertation thesis
and FPGA based FDT can be good choice.

>> > 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.

OK. I will make the first draft and send it to list for review but it will be
only part of patch rely on with ppc405 because we don't have microblaze kernel code.

Michal Simek

Re: FDT for Microblaze and PPC405

[Michal Simek]

Hi,
I made EDK tcl script for generation DTS test scructure for FDT. Script 
support Microblaze and PowerPC 405.
Script was primary built for generation U-BOOT configs files for Microblaze.
For Microblaze can you generate both files (FDT and U-BOOT).
For PowerPC can you generate only DTS file. Generation U-BOOT configs files 
aren't supported yet. Script ends after generation DTS.
Script has 2.00.a mark.
It is available at www.monstr.eu.

Cheers,
Michal Simek


> On 9/11/07, Michal Simek <Monstr@seznam.cz> wrote:
>> Hi Grant,
>
> (Adding linuxppc-dev mailing list to CC list because we're discussing
> FDT issues)
>
>> I made EDK repository file for generation dts file from Xilinx design. I 
>> sent it to Wolfgang and Steve this week.
>> It is in the same config file as I use for configuration Microblaze for 
>> U-BOOT. If you want I can send you this repository files.
>
> Yes, please do.
>
>> And I start with redesigning Linux kernel for Microblaze. I ported some 
>> peripherals as timer and intc etc.
>> But for some peripherals I need better configuration.
>>
>> I have no time to read information about fdt. Can you tell me what labels 
>> I can use?
>
> Steve has already done a bunch of work in this direction on
> microblaze, I would converse with him.
>
>>
>> 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.
>
>>
>> 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/*
>
> Cheers,
> g.
>
>
> -- 
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.485 / Virus Database: 269.13.15/1002 - Release Date: 
> 11.9.2007 05:46
>
> 

FDT for Microblaze and PPC405

[Michal Simek]

Hi,
I made EDK tcl script for generation DTS test scructure for FDT. Script
support Microblaze and PowerPC 405.
Script was primary built for generation U-BOOT configs files for Microblaze.
For Microblaze can you generate both files (FDT and U-BOOT).
For PowerPC can you generate only DTS file. Generation U-BOOT configs files
aren't supported yet. Script ends after generation DTS.
Script has 2.00.a mark.
It is available at www.monstr.eu.

Cheers,
Michal Simek