From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LY4Re-00062w-Tk for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:15:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LY4Rd-00060q-8a for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:15:30 -0500 Received: from [199.232.76.173] (port=47585 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LY4Rd-00060g-4M for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:15:29 -0500 Received: from mail.gmx.net ([213.165.64.20]:47633) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LY4Rc-00012C-JX for qemu-devel@nongnu.org; Fri, 13 Feb 2009 15:15:29 -0500 Message-ID: <4995D4EE.8030703@gmx.net> Date: Fri, 13 Feb 2009 21:15:42 +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> <4994D6C8.5050004@gmx.net> <1234555452.2323.5.camel@ld0161-tx32> In-Reply-To: <1234555452.2323.5.camel@ld0161-tx32> Content-Type: text/plain; charset=UTF-8 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: Jon Loeliger Cc: devicetree-discuss , Markus Armbruster , Hollis Blanchard , qemu-devel@nongnu.org On 13.02.2009 21:04, Jon Loeliger wrote: > On Fri, 2009-02-13 at 03:11 +0100, Carl-Daniel Hailfinger wrote: > >> 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. >> > > As would the proposed language enhancements I suggested. > Do you have a pointer to the archives for that? Regards, Carl-Daniel -- http://www.hailfinger.org/