From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LXo3c-00080y-IU for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:45:36 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LXo3Z-00080k-60 for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:45:36 -0500 Received: from [199.232.76.173] (port=51370 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXo3Z-00080h-14 for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:45:33 -0500 Received: from mail.gmx.net ([213.165.64.20]:50598) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LXo3Y-0005nl-Aj for qemu-devel@nongnu.org; Thu, 12 Feb 2009 21:45:32 -0500 Message-ID: <4994DED9.6020803@gmx.net> Date: Fri, 13 Feb 2009 03:45:45 +0100 From: Carl-Daniel Hailfinger MIME-Version: 1.0 Subject: DTS syntax and DTC patches (was: 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> <20090213021704.GA10476@yookeroo.seuss> In-Reply-To: <20090213021704.GA10476@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: Coreboot , Markus Armbruster , Hollis Blanchard , devicetree-discuss@ozlabs.org, qemu-devel@nongnu.org [Adding the coreboot mailing list to CC. It's moderated for non-subscribers, but it won't take long for legitimate mails to be approved.] On 13.02.2009 03:17, David Gibson wrote: > On Fri, Feb 13, 2009 at 03:11:20AM +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. >> > > Hrm.. it would be nice if you'd co-ordinated with Jon and I about > this. Then we could have at least the bits which make sense in > upstream dtc... > Probably the biggest obstacle for a full merge right now is that the coreboot v3 DTC is rather old and has been extended not only for a more readable DTS syntax variant, but also for additional output modes (C header and C code). We (coreboot developers) are interested in reducing our diff with upstream DTC in order to improve maintainability of our DTC code. Regards, Carl-Daniel