qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Paul Brook <paul@codesourcery.com>
Cc: devicetree-discuss@lists.ozlabs.org, qemu-devel@nongnu.org,
	jeremy.kerr@canonical.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/7] QEMU patches to generate FDT from qdevs
Date: Fri, 9 Apr 2010 08:47:35 -0600	[thread overview]
Message-ID: <h2ofa686aa41004090747w2422cedasb6f4b51633637816@mail.gmail.com> (raw)
In-Reply-To: <201004091307.22473.paul@codesourcery.com>

On Fri, Apr 9, 2010 at 6:07 AM, Paul Brook <paul@codesourcery.com> 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.  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.

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.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2010-04-09 14:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07  4:09 [Qemu-devel] [RFC PATCH 0/7] QEMU patches to generate FDT from qdevs Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 1/7] devicetree: Add 8k instead of double dtb size when reserving extra memory Grant Likely
2010-04-09 12:00   ` Paul Brook
2010-04-09 14:55     ` Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 2/7] devicetree: auto-populate the device tree with qdev data Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 3/7] devicetree: add helper for determining IRQ properties in the device tree Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 4/7] devicetree: Add sysbus fdt populate hooks Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 5/7] devicetree: Add helper to register devices with an fdt_populate hook Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 6/7] devicetree: Add fdt_populate hook to pl011 device Grant Likely
2010-04-07  4:10 ` [Qemu-devel] [RFC PATCH 7/7] devicetree: Add fdt_populate hook to smc91x device Grant Likely
2010-04-07  7:01 ` [Qemu-devel] Re: [RFC PATCH 0/7] QEMU patches to generate FDT from qdevs Jeremy Kerr
2010-04-07 20:58   ` Grant Likely
2010-04-07 19:10 ` [Qemu-devel] " Blue Swirl
2010-04-07 20:57   ` Grant Likely
2010-04-09 12:07 ` Paul Brook
2010-04-09 14:47   ` Grant Likely [this message]
2010-04-09 15:57     ` Paul Brook
2010-04-09 16:35       ` Grant Likely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=h2ofa686aa41004090747w2422cedasb6f4b51633637816@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jeremy.kerr@canonical.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).