From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Machine config files Date: Fri, 14 Nov 2008 14:11:32 -0600 Message-ID: <491DDB74.5070701@codemonkey.ws> References: <200811140332.14093.paul@codesourcery.com> <491DD188.6000603@codemonkey.ws> <200811141351.40613.hollisb@us.ibm.com> Reply-To: qemu-devel@nongnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200811141351.40613.hollisb@us.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Hollis Blanchard Cc: devicetree-discuss@ozlabs.org, qemu-devel@nongnu.org List-Id: devicetree@vger.kernel.org Hollis Blanchard wrote: > We do; PLB, OPB, and EBC are all on-chip busses found on IBM PowerPC SoCs. For > example, you can see devices representing the UARTs and PCI controller in our > bamboo.dts file. Qemu only modifies the device tree at runtime with > information not known until then (memory size, clock frequency, etc). > Yes, but you don't build the machine based on the device tree. What would be useful would be to be able to simply write a device tree description and that would fully represent the board such that you didn't need a ppc440_bamboo.c file at all. So what I'm getting at is, what is preventing us from being able to do this today? Regards, Anthony Liguori