[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] Machine description as data

From: David Gibson
Subject: Re: [Qemu-devel] [RFC] Machine description as data
Date: Fri, 13 Feb 2009 12:05:50 +1100
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Feb 12, 2009 at 07:29:12PM +0100, Markus Armbruster wrote:
> "M. Warner Losh" <address@hidden> writes:
> > However, every board that's being produced for powerpc has the DTB at
> > least available.  It has to be, or (recent?) Linux kernels flat out
> > won't work.  This suggests that it might be a good idea to look at
> > this format.
> >
> > There's DTS and DTB.  One is the source, the other is the binary
> > created from the source.  I'd recommend that qemu actually use the DTB
> > rather than the DTS to implement things.  This way one could have a
> > nicer syntax like the above and generate the DTB, or one could use the
> > DTS provided by a vendor if there was a more specific board they
> > wanted qemu to emulate.
> As far as I know, dtc can decompile DTB into DTS.

That's correct.  However, like many decompilation processes,
converting dts->dtb->dts is usually a lossy process to some extent.
dts has multiple ways to represent some things for readability
reasons, which don't affect the content of the compiled tree.

> I'm not a fan of DTS syntax either, but if we choose FDT, then inventing
> an alternative syntax seems rather pointless to me.

If you have suggestions for improving dts that don't involve
completely breaking compatibility with existing trees, we might be
able to incorporate them into dtc to make everyone's life easier.

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_!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]