From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 3/4] Use embedded libfdt in the bootwrapper
Date: Thu, 08 Nov 2007 16:50:11 -0600 [thread overview]
Message-ID: <473392A3.4010203@freescale.com> (raw)
In-Reply-To: <20071108224051.GB18592@localhost.localdomain>
David Gibson wrote:
>> 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, good -- I was looking in libfdt itself, not the wrapper. Now if
only we could get something similar into u-boot... maybe libfdt proper
could accept an optional realloc() function pointer in fdt_init(), and
eliminate the need for the caller to provide such a wrapper?
-Scott
next prev parent reply other threads:[~2007-11-08 22:50 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 4/4] Kill flatdevtree.c David Gibson
2007-11-08 14:27 ` Jon Loeliger
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
2007-11-08 22:50 ` Scott Wood [this message]
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: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=473392A3.4010203@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.