From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5516] New: appended device tree blobs on uImage fails
Date: Fri, 7 Sep 2012 14:59:38 +0000 (UTC) [thread overview]
Message-ID: <bug-5516-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5516
Summary: appended device tree blobs on uImage fails
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: richard.genoud at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
The version impacted is 2012.08 (it's not in the list)
the commit 978928e4acb0ee4e335eaf4bf8feca895f372418 adds the ability to append
device tree blobs.
This works great with zImage.
BUT, with uImage there's a problem:
in linux.mk, the line :
cat $(KERNEL_ARCH_PATH)/boot/$(KERNEL_DTS_NAME).dtb >>
$(KERNEL_ARCH_PATH)/boot/zImage
is all right, but after that, the line :
$(TARGET_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) uImage
erases the zImage that has been just done.
that's because in the kernel, the uImage rule is :
$(obj)/uImage: $(obj)/zImage FORCE
@$(check_for_multiple_loadaddr)
$(call if_changed,uimage)
@echo ' Image $@ is ready'
=> so if we do a make uImage, zImage is overwritten.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-09-07 14:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 14:59 bugzilla at busybox.net [this message]
2012-10-03 11:40 ` [Buildroot] [Bug 5516] appended device tree blobs on uImage fails bugzilla at busybox.net
2012-10-03 13:25 ` bugzilla at busybox.net
2012-10-03 14:23 ` bugzilla at busybox.net
2012-10-03 14:32 ` bugzilla at busybox.net
2012-10-03 14:52 ` bugzilla at busybox.net
2012-10-04 20:47 ` bugzilla at busybox.net
2012-10-04 20:48 ` bugzilla at busybox.net
2012-10-05 6:46 ` bugzilla at busybox.net
2012-10-09 8:12 ` bugzilla at busybox.net
2013-05-21 23:17 ` bugzilla at busybox.net
2013-05-21 23:53 ` bugzilla at busybox.net
2013-05-22 9:40 ` bugzilla at busybox.net
2013-05-22 9:42 ` bugzilla at busybox.net
2013-05-22 10:37 ` bugzilla at busybox.net
2013-05-22 13:34 ` bugzilla at busybox.net
2013-05-23 16:19 ` bugzilla at busybox.net
2013-05-27 15:14 ` bugzilla at busybox.net
2013-08-01 16:02 ` bugzilla at busybox.net
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=bug-5516-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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