From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEnCW-0005ih-Ei for qemu-devel@nongnu.org; Thu, 11 Jun 2009 12:32:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEnCR-0005Zk-51 for qemu-devel@nongnu.org; Thu, 11 Jun 2009 12:32:27 -0400 Received: from [199.232.76.173] (port=42585 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEnCQ-0005ZD-Uw for qemu-devel@nongnu.org; Thu, 11 Jun 2009 12:32:22 -0400 Received: from mail2.shareable.org ([80.68.89.115]:38458) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MEnCQ-0002N3-D6 for qemu-devel@nongnu.org; Thu, 11 Jun 2009 12:32:22 -0400 Date: Thu, 11 Jun 2009 17:32:17 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 3/4] Stellaris machine config Message-ID: <20090611163217.GA12367@shareable.org> References: <20090610173803.4674.82538.stgit@wren.home> <20090610173829.4674.2315.stgit@wren.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: M P Cc: Paul Brook , qemu-devel@nongnu.org M P wrote: > So now, with qdev, it's all official, /every value, constant, and > bitfield/ is hard coded, in hex, into a different non-code file, with > no way of derivating or overloading from. [...] > In fact, > the stellaris share /a lot/ between themselves, and there is not a > single shared line between your two stellaris boards definition file. This is a good point. I guess FDT is missing a "#include" equivalent, and possibly name constants. That isn't surprising given FDT's original use, to pass an entire machine description to a running kernel. But for QEMU, some way to give names to, say, a standard SoC or a basic board, or a PC without peripherals, and then refer to them in another FDT tree, would be useful. Whether it's done in QEMU itself or by preprocessing doesn't matter. Preprocessing would have the advantage that it would output FDTs that could, maybe, be passed to the guest kernel and just work. Or maybe QEMU can have a tree preprocessor built in. -- Jamie