linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 3/4] Use embedded libfdt in the bootwrapper
Date: Fri, 9 Nov 2007 09:40:51 +1100	[thread overview]
Message-ID: <20071108224051.GB18592@localhost.localdomain> (raw)
In-Reply-To: <20071108160839.GA4356@loki.buserror.net>

On Thu, Nov 08, 2007 at 10:08:39AM -0600, Scott Wood wrote:
> On Thu, Nov 08, 2007 at 02:36:03PM +1100, David Gibson wrote:
> > This patch incorporates libfdt (from the source embedded in an earlier
> > patch) into the wrapper.a library used by the bootwrapper.  This
> > includes adding a libfdt_env.h file, which the libfdt sources need in
> > order to integrate into the bootwrapper environment, and a
> > libfdt-wrapper.c which provides glue to connect the bootwrappers
> > abstract device tree callbacks to the libfdt functions.
> > 
> > In addition, this patch changes the various wrapper and platform files
> > to use libfdt functions instead of the older flatdevtree.c library.
> 
> Won't we need to change the dtc invocation in the wrapper to reserve some
> space now?
> 
> Speaking of which, it seems dtc still only supports setting the total size,
> as opposed to specifying the amount of additional space.  It's still a bit
> crappy having to guess how much space to add, but it's better than needing
> to know how big the dtb will be without additional space.
> 
> How hard would it be to get libfdt to dynamically allocate any extra space
> it needs?  This is a regression from the current flat device tree code...

Uh.. it already does.  Or rather, the shims in libfdt-wrapper.c do so,
when libfdt functions which can expand the tree report that they've
run out of room.

Ah... except that I haven't properly placed an fdt_open_into() with
possible expansion somewhere to make sure we can handle v16 or dtbs
with the blocks in unusual order.

I'll need to fix that before we merge.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-11-08 22:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  3:32 [0/4] Embed dtc and libfdt in the kernel David Gibson
2007-11-08  3:36 ` [PATCH 2/4] Use embedded dtc in kernel builds David Gibson
2007-11-08  3:36 ` [PATCH 3/4] Use embedded libfdt in the bootwrapper David Gibson
2007-11-08 16:08   ` Scott Wood
2007-11-08 22:40     ` David Gibson [this message]
2007-11-08 22:50       ` Scott Wood
2007-11-08 23:29         ` David Gibson
2007-11-09  0:52         ` Jerry Van Baren
2007-11-09 15:59           ` Scott Wood
2007-11-10  1:14             ` Jerry Van Baren
2007-11-08  3:36 ` [PATCH 4/4] Kill flatdevtree.c David Gibson
2007-11-08 14:27   ` Jon Loeliger
2007-11-08  3:38 ` [1/4] Merge dtc and libfdt upstream source David Gibson
  -- strict thread matches above, loose matches on Subject: below --
2007-11-12  4:11 [0/4] Embed dtc and libfdt in the kernel (spin the third) David Gibson
2007-11-12  4:15 ` [PATCH 3/4] Use embedded libfdt in the bootwrapper David Gibson
2007-12-03  4:30   ` David Gibson

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=20071108224051.GB18592@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.com \
    /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).