From: Ralf Baechle <ralf@linux-mips.org>
To: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org, Nathan Sullivan <nathan.sullivan@ni.com>
Subject: Re: [PATCH 4/4] MIPS: NI 169445: Fix lack of ITS root node
Date: Tue, 8 Aug 2017 06:32:33 +0200 [thread overview]
Message-ID: <20170808043233.GG3509@linux-mips.org> (raw)
In-Reply-To: <20170807223724.19408-5-paul.burton@imgtec.com>
On Mon, Aug 07, 2017 at 03:37:24PM -0700, Paul Burton wrote:
> For some reason the root node was missing in the NI 169445 flattened
> image tree source, leading to the following build error when attempting
> to generate the flattened image tree binary:
>
> ITB arch/mips/boot/vmlinux.gz.itb
> Error: arch/mips/boot/vmlinux.gz.its:90.1-2 syntax error
> FATAL ERROR: Unable to parse input tree
> /usr/bin/mkimage: Can't read arch/mips/boot/vmlinux.gz.itb.tmp: Invalid argument
> make[1]: *** [arch/mips/boot/Makefile:165: arch/mips/boot/vmlinux.gz.itb] Error 255
> make: *** [arch/mips/Makefile:371: vmlinux.gz.itb] Error 2
>
> Fix this by adding in the root node.
My bad, I messed this up when fixing a merge conflict in
arch/mips/generic/vmlinux.its.S. I fixed the original
commit instead.
Thanks,
Ralf
prev parent reply other threads:[~2017-08-08 4:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 22:37 [PATCH 0/4] MIPS: Split generic board ITS source, fix NI 169445 build Paul Burton
2017-08-07 22:37 ` Paul Burton
2017-08-07 22:37 ` [PATCH 1/4] MIPS: Allow platform to specify multiple its.S files Paul Burton
2017-08-07 22:37 ` Paul Burton
2017-08-07 22:37 ` [PATCH 2/4] MIPS: generic: Move Boston FIT image source to its own file Paul Burton
2017-08-07 22:37 ` Paul Burton
2017-08-07 22:37 ` [PATCH 3/4] MIPS: generic: Move NI 169445 " Paul Burton
2017-08-07 22:37 ` Paul Burton
2017-08-07 22:37 ` [PATCH 4/4] MIPS: NI 169445: Fix lack of ITS root node Paul Burton
2017-08-07 22:37 ` Paul Burton
2017-08-08 4:32 ` Ralf Baechle [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=20170808043233.GG3509@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=nathan.sullivan@ni.com \
--cc=paul.burton@imgtec.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 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.