From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1O0Czm-0001KP-TQ
	for qemu-devel@nongnu.org; Fri, 09 Apr 2010 08:07:34 -0400
Received: from [140.186.70.92] (port=51084 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1O0Czk-0001J3-A2
	for qemu-devel@nongnu.org; Fri, 09 Apr 2010 08:07:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <paul@codesourcery.com>) id 1O0Czi-00054S-R0
	for qemu-devel@nongnu.org; Fri, 09 Apr 2010 08:07:32 -0400
Received: from mx20.gnu.org ([199.232.41.8]:37396)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <paul@codesourcery.com>) id 1O0Czi-00054O-PH
	for qemu-devel@nongnu.org; Fri, 09 Apr 2010 08:07:30 -0400
Received: from mail.codesourcery.com ([38.113.113.100])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1O0Czi-0004Zw-DG
	for qemu-devel@nongnu.org; Fri, 09 Apr 2010 08:07:30 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/7] QEMU patches to generate FDT from
	qdevs
Date: Fri, 9 Apr 2010 13:07:22 +0100
References: <20100407040129.20274.44284.stgit@angua>
In-Reply-To: <20100407040129.20274.44284.stgit@angua>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201004091307.22473.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Grant Likely <grant.likely@secretlab.ca>, devicetree-discuss@lists.ozlabs.org, jeremy.kerr@canonical.com

> Hi everyone,
> 
> This is an experimental set of patches for populating the flattened
> device tree (fdt) data from the actual set of qdevs in the platform.
> I'm not expecting this to get merged anytime soon, but I wanted to get
> it out there to solicit comments.  My target for this is testing
> device tree support on ARM.

I think you need to convert some more interesting machines before it's 
possible to tell whether this is a sane setup. When investigating FDTs for 
creation of machine I found it's easy to invent something that can handle the 
simple integrator/cp board, but it all starts to fall apart when you encounter 
more complicated boards. In particular things like PCI, USB, I2C, etc. and 
strange bus configurations when you have both on-chip and external devices.

Paul