All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Building dtc etc. for packaging
Date: Tue, 11 Nov 2008 11:29:57 -0600	[thread overview]
Message-ID: <4919C115.8040107@genesi-usa.com> (raw)

For some of what we're doing with SUSE now I've determined we should really
be packaging the device tree compiler (and libfdt) so that we can install and
script it, along with some other stuff from U-Boot (not for this mail).

I was wondering if the recommended way would be to use the dtc found in
the kernel-source or to use the git repo at git.jdl.com to grab it and
build it. The one in the kernel is seemingly impossible to build without
some tweaking around (I can't find a target for make that does it) so
I also wonder about a hint here on what to do to create it from the
kernel source so we can pull it out for a local system install.

(the other tool we need is mkimage from U-Boot, I noticed Debian uses this
same command name inside jigdo etc. too, sigh.. also you can't build the
tools without the rest of U-Boot which is hard to envision doing just to
get one command out of it - "make tools/mkimage" doesn't work and I got
tired of reverse engineering the chickenscratch..)

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

             reply	other threads:[~2008-11-11 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 17:29 Matt Sealey [this message]
2008-11-11 18:00 ` Building dtc etc. for packaging Nate Case
2008-11-11 20:32 ` Simon Richter
2008-11-11 22:39 ` David Gibson
2008-11-11 23:10   ` Jon Loeliger

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=4919C115.8040107@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.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.