From: Grant Likely <grant.likely@secretlab.ca>
To: qemu-devel@nongnu.org, devicetree-discuss@lists.ozlabs.org,
jeremy.kerr@canonical.com
Subject: [Qemu-devel] [RFC PATCH 0/7] QEMU patches to generate FDT from qdevs
Date: Tue, 06 Apr 2010 22:09:57 -0600 [thread overview]
Message-ID: <20100407040129.20274.44284.stgit@angua> (raw)
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.
The approach is by no means final, and there are still a number of
details to work out, but I've got it working well with the versatile
platform and I've got the kernel using fdt data to bind against the
smc91x device driver. I'll be posting my associated kernel patches
real-soon-now.
This series is based on Jeremy Kerr's device tree branch found here:
git://kernel.ubuntu.com/jk/dt/qemu.git
Cheers,
g.
---
Grant Likely (7):
devicetree: Add fdt_populate hook to smc91x device
devicetree: Add fdt_populate hook to pl011 device
devicetree: Add helper to register devices with an fdt_populate hook
devicetree: Add sysbus fdt populate hooks.
devicetree: add helper for determining IRQ properties in the device tree
devicetree: auto-populate the device tree with qdev data
devicetree: Add 8k instead of double dtb size when reserving extra memory
device_tree.c | 4 +-
hw/arm_boot.c | 3 +
hw/pl011.c | 29 ++++++++++--
hw/qdev.c | 139 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
hw/qdev.h | 9 ++++
hw/smc91c111.c | 20 ++++++++
hw/sysbus.c | 107 +++++++++++++++++++++++++++++++++++++++++++
hw/sysbus.h | 4 ++
8 files changed, 309 insertions(+), 6 deletions(-)
--
Signature
next reply other threads:[~2010-04-07 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 4:09 Grant Likely [this message]
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
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=20100407040129.20274.44284.stgit@angua \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jeremy.kerr@canonical.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).