From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O0FV8-0002oN-7L for qemu-devel@nongnu.org; Fri, 09 Apr 2010 10:48:06 -0400 Received: from [140.186.70.92] (port=38656 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O0FV6-0002o5-5n for qemu-devel@nongnu.org; Fri, 09 Apr 2010 10:48:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O0FV4-0002qp-HO for qemu-devel@nongnu.org; Fri, 09 Apr 2010 10:48:04 -0400 Received: from mail-pv0-f173.google.com ([74.125.83.173]:54921) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O0FV4-0002qW-CU for qemu-devel@nongnu.org; Fri, 09 Apr 2010 10:48:02 -0400 Received: by pvd12 with SMTP id 12so1050969pvd.4 for ; Fri, 09 Apr 2010 07:48:00 -0700 (PDT) MIME-Version: 1.0 Sender: glikely@secretlab.ca In-Reply-To: <201004091307.22473.paul@codesourcery.com> References: <20100407040129.20274.44284.stgit@angua> <201004091307.22473.paul@codesourcery.com> From: Grant Likely Date: Fri, 9 Apr 2010 08:47:35 -0600 Message-ID: Subject: Re: [Qemu-devel] [RFC PATCH 0/7] QEMU patches to generate FDT from qdevs Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: devicetree-discuss@lists.ozlabs.org, qemu-devel@nongnu.org, jeremy.kerr@canonical.com On Fri, Apr 9, 2010 at 6:07 AM, Paul Brook wrote: >> 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. =A0My 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 fo= r > 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 enco= unter > more complicated boards. In particular things like PCI, USB, I2C, etc. an= d > strange bus configurations when you have both on-chip and external device= s. Certainly. What would be a good (preferably ARM) platform to look at? I'm fairly new to working with QEMU, so I'm not very familiar with the platforms that are available. g. --=20 Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.