From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: libfdt: Handle v16 and re-ordered trees for r/w
Date: Thu, 01 Nov 2007 08:08:01 -0500 [thread overview]
Message-ID: <E1InZmD-0003jL-Td@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 01 Nov 2007 11:37:31 +1100." <20071101003731.GG16119@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> Currently all the read/write functions in libfdt require that the
> given tree be v17, and further, that the tree has the memory
> reservation block, structure block and strings block stored in that
> physical order.
>
> This patch eases these constraints, by making fdt_open_int() reorder
> the blocks, and/or convert the tree to v17, so that it will then be
> ready for the other read-write functions.
>
> It also extends fdt_pack() to actually remove any gaps between blocks
> that might be present.
>
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>
Applied.
jdl
prev parent reply other threads:[~2007-11-01 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 0:37 libfdt: Handle v16 and re-ordered trees for r/w David Gibson
2007-11-01 13:08 ` Jon Loeliger [this message]
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=E1InZmD-0003jL-Td@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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