From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 17 Jul 2015 23:16:32 +0200 Subject: [Buildroot] [RFC/PATCH] linux: remove the zImage before rebuild In-Reply-To: <55A94E20.2000506@mentor.com> References: <1411773774-7712-1-git-send-email-guido@vanguardiasur.com.ar> <55A926DC.9010803@mentor.com> <20150717163442.GA6466@fox> <20150717194128.7c22974b@free-electrons.com> <55A94E20.2000506@mentor.com> Message-ID: <20150717231632.05928653@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Fri, 17 Jul 2015 11:49:04 -0700, Hollis Blanchard wrote: > A bit of a tangent now, but I am trying to write a recipe for another > bootwrapper, which prepends a little code to a zImage/DTB combo. Right > now, it basically boils down to this: > > define BOOT_WRAPPER_ARM_BUILD_CMDS > > $(MAKE) CROSS_COMPILE=$(TARGET_CROSS) DTBIMAGE=$(BINARIES_DIR)/zImage -C $(@D) > > endef > > > Practically speaking, I think the bootwrapper is only really useful in > the BR2_LINUX_KERNEL_APPENDED_ZIMAGE case, and I can enforce that via > Kconfig dependencies, so I can assume the kernel name is "zImage". > > If your idea above is implemented, would I need to duplicate the > linux.mk logic around BR2_LINUX_KERNEL_USE_INTREE_DTS, > BR2_LINUX_KERNEL_INTREE_DTS_NAME, BR2_LINUX_KERNEL_USE_CUSTOM_DTS, and > BR2_LINUX_KERNEL_CUSTOM_DTS_PATH? Or is there a better way to do this? We already have a similar case in the boot-wrapper-aarch64 package. I am indeed not sure how that would work with appended DTB and multiple zImage generated. Needs some thought, indeed. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com