Device Tree tool [was RE: [PATCH] Consolidate XILINX_VIRTEXboardsupport]

[Stephen Neuendorffer]

I don't have an EDK script.  I'm currently using a hacked version of 
Grant's gen_mhs_devtree.py script, and then I modified the resulting
device
tree in an effort to get things working.  In the long term, I think
having
an EDK script will be necessary to ensure that all of the information is
in the device tree.

Michal: what do you need from me?

Steve

> -----Original Message-----
> From: Michal Simek [mailto:Monstr at seznam.cz] 
> Sent: Tuesday, August 14, 2007 11:42 PM
> To: Stephen Neuendorffer
> Cc: Grant Likely; microblaze-uclinux at itee.uq.edu.au; 
> linuxppc-embedded at ozlabs.org
> Subject: RE: Device Tree tool [was RE: [PATCH] Consolidate 
> XILINX_VIRTEXboardsupport]
> 
> Hi,
> 
> >I've managed to get the first step working: a microblaze system
> >advertising of_devices in 2.6 using a flat device tree.  
> 
> It's great news.
> 
> >Is there a concensus on how microblaze systems should get booted?
> >Currently,
> >I'm linking the device tree directly into the kernel itself, 
> loading the
> >whole
> >mess using SystemAce and the start address jumps directly into the
> >kernel, which
> >is quite a bit different than the way powerpc works.  It's certainly
> >simpler:
> >maybe too simple.  At the same time, replicating
> >the complexity of arch/powerpc with separate boot code may 
> or may not be
> >worth it...
> >Any thoughts?
> 
> Microblaze can be boot via U-BOOT. U-BOOT supports FDT for 
> some PowerPC boards.
> I would like to help with this part of bootloader code. 
> 
> Do you have any EDK script for generation FDT? 
> 
> Best regards,
> Michal Simek
> 
>