From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Torbjörn Andersson" <tobbe.tt@home.se>,
"Paul Brook" <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Machine description, an alternativ using XML
Date: Thu, 26 Feb 2009 16:14:42 -0600 [thread overview]
Message-ID: <49A71452.7000103@codemonkey.ws> (raw)
In-Reply-To: <200902261606.06841.paul@codesourcery.com>
Paul Brook wrote:
>> <OBJECT name="pic" class="pl190">
>> <ATTRIBUTE name="pic"> <value obj_ref=":cpu"/> </ATTRIBUTE>
>> <ATTRIBUTE name="memmap"> <value obj_ref=":memmap"/> </ATTRIBUTE>
>> <ATTRIBUTE name="base"> <value integer="0xc0010000"/> </ATTRIBUTE>
>> </OBJECT>
>> <MACHINE/>
>>
>
> It looks like you're just using XML to encapsulate simple <key,value> pairs,
> which IMHO is completely the wrong way to use XML. Qemu already has to know
> about things like IO regions, IRQs, bus bindings. XML gives you the power to
> describe these things properly, rather than relying on clumsy naming
> conventions.
>
I'm really don't want to see this get furthered rat holed. Since we all
seemed relatively happy with the device tree as a configuration file,
can we agree to that firmly and avoid this discussion?
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-02-26 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 6:49 [Qemu-devel] Machine description, an alternativ using XML Torbjörn Andersson
2009-02-26 16:06 ` Paul Brook
2009-02-26 20:26 ` SV: " Torbjörn Andersson
2009-02-26 22:14 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-26 9:36 Jamie Lokier
2009-02-26 12:01 ` Torbjörn Andersson
2009-02-26 13:24 ` Steve Fosdick
2009-02-26 18:48 ` Andreas Färber
2009-02-26 21:47 ` Jamie Lokier
2009-02-26 19:41 ` Blue Swirl
2009-02-26 13:09 Jamie Lokier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49A71452.7000103@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=tobbe.tt@home.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.