From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 1/2] libfdt: Add some utilities to manipulate the reserved memory map.
Date: Sun, 15 Apr 2007 08:23:49 -0400 [thread overview]
Message-ID: <46221955.3050201@gmail.com> (raw)
In-Reply-To: <20070415034214.GC8130@dellserver.lan>
Hello All,
I've published two more patches for fdt handling and pushed them to the
u-boot-fdt repository. This now handles ramdisks well, including
modifying the reserved map entries in the blob (required some new libfdt
routines).
I have not tried a multi-image (blob embedded), but have the same
handling code as passing in the blob as the 2nd parameter so it should
work OK. If someone could test this or send me a RTFM pointer on how to
create a multi-image, I would appreciate it.
The only remaining issue is my poorly executed changes for setting the
MAC addresses.
Wolfgang: This should be good to pull, but it wouldn't hurt to wait for
a little for code review. Also, I'll try to get the mac address fix in
in the next day or two.
Best regards,
gvb
prev parent reply other threads:[~2007-04-15 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 3:42 [U-Boot-Users] [PATCH 1/2] libfdt: Add some utilities to manipulate the reserved memory map Jerry Van Baren
2007-04-15 12:23 ` Jerry Van Baren [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=46221955.3050201@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.denx.de \
/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