From: Paul Brook <paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
To: qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>,
CE Linux Developers List
<celinux-dev-VxL1A5FK7jA05z2xGA6PZHhyD016LWXt@public.gmane.org>
Subject: Re: [Qemu-devel] CELF Project Proposal - Device tree support for QEMU system emulation.
Date: Tue, 22 Dec 2009 12:45:48 +0000 [thread overview]
Message-ID: <200912221245.48495.paul@codesourcery.com> (raw)
In-Reply-To: <4B2A94BB.4020200-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
> http://thread.gmane.org/gmane.comp.emulators.qemu/44869
>
> I'm not sure why Paul never pushed it but I think he was able to create
> the syborg board purely from a device tree.
The patches referenced above include purely device-tree based Syborg and
Stellaris boards.
It works fairly nicely for some embedded boards, but gets fairly hairy when
you start considering more complex topologies/machines. I particular the PCI
OF/FDT bindings don't really fit what we need for qemu. Obviously full qdev
conversion is a prerequisite for device tree based configuration, and at that
time qdev was still in its infancy.
Part of the reason for posting that patch was to demonstrate the abstraction
layers required for the internal device model. Previous patches tended to be
based on the pre-existing PC commandline options, which IMO is a mistake.
Likewise if (like my implementation) you focus on embedded machines you risk
serious problems trying to extend to server class machines.
Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: devicetree-discuss@lists.ozlabs.org,
CE Linux Developers List <celinux-dev@tree.celinuxforum.org>
Subject: Re: [Qemu-devel] CELF Project Proposal - Device tree support for QEMU system emulation.
Date: Tue, 22 Dec 2009 12:45:48 +0000 [thread overview]
Message-ID: <200912221245.48495.paul@codesourcery.com> (raw)
In-Reply-To: <4B2A94BB.4020200@codemonkey.ws>
> http://thread.gmane.org/gmane.comp.emulators.qemu/44869
>
> I'm not sure why Paul never pushed it but I think he was able to create
> the syborg board purely from a device tree.
The patches referenced above include purely device-tree based Syborg and
Stellaris boards.
It works fairly nicely for some embedded boards, but gets fairly hairy when
you start considering more complex topologies/machines. I particular the PCI
OF/FDT bindings don't really fit what we need for qemu. Obviously full qdev
conversion is a prerequisite for device tree based configuration, and at that
time qdev was still in its infancy.
Part of the reason for posting that patch was to demonstrate the abstraction
layers required for the internal device model. Previous patches tended to be
based on the pre-existing PC commandline options, which IMO is a mistake.
Likewise if (like my implementation) you focus on embedded machines you risk
serious problems trying to extend to server class machines.
Paul
next prev parent reply other threads:[~2009-12-22 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 4:46 CELF Project Proposal - Device tree support for QEMU system emulation Rob Landley
2009-12-17 4:46 ` [Qemu-devel] " Rob Landley
2009-12-17 23:14 ` [Celinux-dev] " Tim Bird
2009-12-17 23:14 ` [Qemu-devel] " Tim Bird
[not found] ` <200912162246.42366.rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2009-12-17 20:29 ` [Qemu-devel] " Anthony Liguori
2009-12-17 20:29 ` Anthony Liguori
[not found] ` <4B2A94BB.4020200-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2009-12-22 12:45 ` Paul Brook [this message]
2009-12-22 12:45 ` Paul Brook
2009-12-22 18:54 ` Rob Landley
2009-12-19 10:54 ` Blue Swirl
2009-12-19 10:54 ` Blue Swirl
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=200912221245.48495.paul@codesourcery.com \
--to=paul-qd8j1lwmmjjtcj0u4l0sbw@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
--cc=celinux-dev-VxL1A5FK7jA05z2xGA6PZHhyD016LWXt@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.