From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Loeliger Date: Mon, 03 Mar 2008 08:29:27 -0600 Subject: [U-Boot-Users] [PATCH 5/8] [new uImage] Add libfdt support to mkimage In-Reply-To: <47C9BD4B.3090902@gmail.com> References: <20080229231920.8049.35680.stgit@hekate.izotz.org> <20080229231949.8049.60884.stgit@hekate.izotz.org> <47C9BD4B.3090902@gmail.com> Message-ID: <47CC0B47.2030900@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Jerry Van Baren wrote: > Marian Balakowicz wrote: >> From: Bartlomiej Sieka >> >> Signed-off-by: Bartlomiej Sieka >> --- >> >> Makefile | 3 +++ >> include/libfdt_env.h | 4 ++++ >> libfdt/fdt.c | 4 ++++ >> libfdt/fdt_ro.c | 4 ++++ >> libfdt/fdt_rw.c | 4 ++++ >> libfdt/fdt_strerror.c | 4 ++++ >> libfdt/fdt_wip.c | 4 ++++ >> tools/.gitignore | 7 +++++++ >> tools/Makefile | 51 ++++++++++++++++++++++++++++++++++++++++++++++--- >> tools/fdt_host.h | 28 +++++++++++++++++++++++++++ >> tools/mkimage.h | 1 + >> 11 files changed, 111 insertions(+), 3 deletions(-) >> create mode 100644 tools/fdt_host.h > > Arrrr, I'm not wild about this, but I cannot suggest a better way. :-( > > All these (trivial) touches to libfdt/* are annoying and could cause > patch tracking of the dtc/libfdt source to break. I guess that is the > risk we live with unless or until someone comes up with a better way. :-( > > Best regards, > gvb > Well, the obvious approach would be to format up the patches and submit them to the linuxppc-dev at ozlabs.org list along with an explanation as to why the libfdt changes are needed, make sure they are compatible with the kernel code as well. We'll see how badly Gibson chokes, and if the libfdt maintainer takes 'em. :-) jdl