qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, kvm-ppc@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 4/4] IBM PowerPC 440EP Bamboo reference board emulation
Date: Tue, 16 Dec 2008 09:14:52 -0600	[thread overview]
Message-ID: <1229440492.31337.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20081216104753.GC20364@volta.aurel32.net>

On Tue, 2008-12-16 at 11:47 +0100, Aurelien Jarno wrote:
> On Mon, Dec 15, 2008 at 06:17:32PM -0600, Hollis Blanchard wrote:
> > Since most IO devices are integrated into the 440EP chip, "Bamboo support"
> > mostly entails implementing the -kernel, -initrd, and -append options.
> > 
> > These options are implemented by loading the guest as if u-boot had done it,
> > i.e. loading a flat device tree, updating it to hold initrd addresses, ram
> > size, and command line, and passing the FDT address in r3.
> > 
> > Since we use it with KVM, we enable the virtio block driver and include hooks
> > necessary for KVM support.
> > 
> > Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
> > ---
> > Made comment more specific.
> > ---
> >  Makefile             |    2 +-
> >  Makefile.target      |    2 +-
> >  hw/boards.h          |    1 +
> >  hw/ppc440_bamboo.c   |  190 ++++++++++++++++++++++++++++++++++++++++
> >  pc-bios/bamboo.dtb   |  Bin 0 -> 3163 bytes
> >  pc-bios/bamboo.dts   |  234 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> I guess the .dtb file is generated from the .dts. Could you give us more
> details about that? When the tools need to generate the dtb file are
> installed on the build machine, we may want to generate the .dtb during
> the build process.

The dtb file ("device tree binary") is generated from the dts ("device
tree source") by a tool called dtc, the device tree compiler.[1]

dtc is available in major distributions: in Fedora the package name is
"dtc"; in Debian it is "device-tree-compiler" (available in testing and
unstable).

[1] http://git.jdl.com/gitweb/?p=dtc.git;a=summary

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2008-12-16 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  0:17 [Qemu-devel] KVM PowerPC support v3 Hollis Blanchard
2008-12-16  0:17 ` [Qemu-devel] [PATCH 1/4] Implement device tree support needed for Bamboo emulation Hollis Blanchard
2008-12-16  0:17   ` [Qemu-devel] [PATCH 2/4] Enable KVM for ppcemb Hollis Blanchard
2008-12-16  0:17   ` [Qemu-devel] [PATCH 3/4] PowerPC 440EP SoC emulation Hollis Blanchard
2008-12-16 10:45     ` Aurelien Jarno
2008-12-16 15:37       ` Hollis Blanchard
2008-12-16  0:17   ` [Qemu-devel] [PATCH 4/4] IBM PowerPC 440EP Bamboo reference board emulation Hollis Blanchard
2008-12-16 10:47     ` Aurelien Jarno
2008-12-16 15:14       ` Hollis Blanchard [this message]
2008-12-16 10:44 ` [Qemu-devel] KVM PowerPC support v3 Aurelien Jarno

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=1229440492.31337.21.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=kvm-ppc@vger.kernel.org \
    --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).