From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] linux: don't build appended DTB image in place and support multiple images
Date: Tue, 20 Oct 2015 07:22:33 +0200 [thread overview]
Message-ID: <87oafu15d2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1445202302-2720-4-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sun, 18 Oct 2015 23:05:02 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> Currently, the linux.mk logic for appended DTB image does the
> appending of the DTB in place, directly at the end of the zImage using
> a >> sign. This is incorrect because if you run "make linux-rebuild"
> multiple times, you get the DTB appended over and over again to the
> image.
> Since keeping the 'zImage' or 'uImage' name for the appended DTB image
> is not very clear, this commit moves to using the 'zImage.<dtb>' and
> 'uImage.<dtb>' format. This way, we can clearly distinguish the
> original image from the appended one.
> In addition, this naming scheme easily allows to generate *multiple*
> appended DTB images: from one zImage, you can generate multiple
> zImage.<dtb> for several DTBs, and then generate (if requested) the
> corresponding uImage.<dtb>.
> To achieve this, this commit:
> - Changes the definition of LINUX_APPENDED_DTB to iterate over
> $(KERNEL_DTS_NAME), and generate a zImage.<dtb> image for each of
> them.
> - Changes the addition of LINUX_APPENDED_DTB for appended uImage to
> also iterate over $(KERNEL_DTS_NAME).
> - Provide a different implementation of LINUX_INSTALL_IMAGE which
> installs all the appended DTB images (but not the bare image)
> - Remove the checks that verified that only one DT name is passed
> when appended DTB is used, since we now support generating multiple
> DT images.
> Some of the tested configuration:
Thanks for the testing!
> - Appended uImage with several DTBs:
> BR2_LINUX_KERNEL_DEFCONFIG="mvebu_v7"
> BR2_LINUX_KERNEL_APPENDED_UIMAGE=y
> BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x200000"
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="armada-xp-matrix armada-xp-gp armada-370-mirabox"
> Contents of output/images:
> uImage.armada-370-mirabox uImage.armada-xp-gp uImage.armada-xp-matrix
Don't we have readme's and u-boot boot scripts expecting uImage instead
of uImage.<dtb>? I guess if nothing else we need to update the readme's
to tell people to rename the file when copying to the sd card or
whatever.
Other than that the series look good to me!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-10-20 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 21:04 [Buildroot] [PATCH 0/3] linux: Fix appended DTB image generation Thomas Petazzoni
2015-10-18 21:05 ` [Buildroot] [PATCH 1/3] linux: de-duplicate DTB and Linux image installation Thomas Petazzoni
2015-10-18 21:05 ` [Buildroot] [PATCH 2/3] linux: only install the DTBs when not in appended DTB mode Thomas Petazzoni
2015-10-18 21:05 ` [Buildroot] [PATCH 3/3] linux: don't build appended DTB image in place and support multiple images Thomas Petazzoni
2015-10-20 5:22 ` Peter Korsgaard [this message]
2015-12-20 14:26 ` [Buildroot] [PATCH 0/3] linux: Fix appended DTB image generation Thomas Petazzoni
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=87oafu15d2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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