From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LXnWI-0007jK-HO for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:11:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LXnWG-0007j5-2F for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:11:09 -0500 Received: from [199.232.76.173] (port=59361 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXnWF-0007j2-VB for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:11:07 -0500 Received: from mail.gmx.net ([213.165.64.20]:48718) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LXnWF-0003WD-D0 for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:11:07 -0500 Message-ID: <4994D6C8.5050004@gmx.net> Date: Fri, 13 Feb 2009 03:11:20 +0100 From: Carl-Daniel Hailfinger MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC] Machine description as data References: <87iqnh6kyv.fsf@pike.pond.sub.org> <1234378228.28751.79.camel@slate.austin.ibm.com> <20090212040138.GD31142@yookeroo.seuss> <87iqng0x3t.fsf@pike.pond.sub.org> <20090213004305.GB8104@yookeroo.seuss> In-Reply-To: <20090213004305.GB8104@yookeroo.seuss> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster , Hollis Blanchard , devicetree-discuss@ozlabs.org, qemu-devel@nongnu.org On 13.02.2009 01:43, David Gibson wrote: > On Thu, Feb 12, 2009 at 11:26:46AM +0100, Markus Armbruster wrote: > >> I didn't mean to say they are a bad idea for FDTs, just that they're on >> an awkward level of abstraction for QEMU configuration. There, I'd >> rather express a PCI address as "02:01.0" than as <0x00000220>. >> Translating text to binary is the machine's job, not the user's. >> > > Ah, I see what you mean. Hrm, there are several possibilities here, > we'll have to see which works out best for your purposes. > Using the DTC version included in the coreboot v3 sources would solve that problem and give you a readable PCI address representation. Regards, Carl-Daniel -- http://www.hailfinger.org/