From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] Add support for appended device tree blobs for arm
Date: Sat, 28 Jul 2012 21:29:51 +0200 [thread overview]
Message-ID: <20120728212951.1671073f@skate> (raw)
In-Reply-To: <5013FBFE.5030702@mind.be>
Le Sat, 28 Jul 2012 16:49:34 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> > @@ -66,10 +73,14 @@ LINUX_IMAGE_NAME=vmImage
> > else
> > LINUX_IMAGE_NAME=uImage
> > endif
> > +else ifeq ($(BR2_LINUX_KERNEL_APPENDED_UIMAGE),y)
> > +LINUX_IMAGE_NAME=uImage
> > else ifeq ($(BR2_LINUX_KERNEL_BZIMAGE),y)
> > LINUX_IMAGE_NAME=bzImage
> > else ifeq ($(BR2_LINUX_KERNEL_ZIMAGE),y)
> > LINUX_IMAGE_NAME=zImage
> > +else ifeq ($(BR2_LINUX_KERNEL_APPENDED_ZIMAGE),y)
> > +LINUX_IMAGE_NAME=zImage
> > else ifeq ($(BR2_LINUX_KERNEL_VMLINUX_BIN),y)
> > LINUX_IMAGE_NAME=vmlinux.bin
> > else ifeq ($(BR2_LINUX_KERNEL_VMLINUX),y)
>
> I think this whole blob should move to Config.in, like we
> do it for many other strings... But that's of course unrelated
> to this patch.
I don't necessarily agree here. Generally speaking my preference is to
not use too much kconfig to define a bunch of strings when those are
not related to visible options.
> ifeq ($(BR2_LINUX_KERNEL_APPENDED_DTB),y)
> define LINUX_APPEND_DTB
> cat ...
> ifeq ($(BR2_LINUX_KERNEL_APPENDED_UIMAGE),y)
> $(MAKE) ... uImage
> endif
> endef
> endif
>
> (I'm not sure if you can still use an ifeq inside a define.)
No, you can't, and it's a shame :-(
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-28 19:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 12:27 [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 1/6] Revert "Microblaze: build kernel with device tree" Maxime Ripard
[not found] ` <CAEBucnCan1vRHv4GkhYXGHnrb3Nrtg0rOtwiLY_fTuARuV0W2g@mail.gmail.com>
2012-07-18 7:23 ` Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 2/6] Rework support for the device tree Maxime Ripard
2012-07-27 19:45 ` Arnout Vandecappelle
2012-07-17 12:27 ` [Buildroot] [PATCH 3/6] Factorize the u-boot images code Maxime Ripard
2012-07-28 14:36 ` Arnout Vandecappelle
2012-07-17 12:27 ` [Buildroot] [PATCH 4/6] Add support for appended device tree blobs for arm Maxime Ripard
2012-07-28 14:49 ` Arnout Vandecappelle
2012-07-28 19:29 ` Thomas Petazzoni [this message]
2012-07-29 15:16 ` Arnout Vandecappelle
2012-07-30 8:25 ` Fabio Porcedda
2012-07-30 8:31 ` Thomas Petazzoni
2012-07-30 10:10 ` Fabio Porcedda
2012-07-17 12:27 ` [Buildroot] [PATCH 5/6] Add cuImage(powerpc) and simpleImage(microblaze) as Linux kernel images variants Maxime Ripard
2012-07-17 12:27 ` [Buildroot] [PATCH 6/6] Update s6lx9 microblaze default configuration Maxime Ripard
2012-07-27 16:06 ` [Buildroot] [PATCHv3 0/6] Add some support for device tree kernels Fabio Porcedda
2012-07-27 18:59 ` Maxime Ripard
2012-07-30 8:33 ` Fabio Porcedda
2012-07-30 9:38 ` Maxime Ripard
2012-07-30 10:09 ` Fabio Porcedda
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 12:32 [Buildroot] [PATCHv4 " Maxime Ripard
2012-07-30 12:32 ` [Buildroot] [PATCH 4/6] Add support for appended device tree blobs for arm Maxime Ripard
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=20120728212951.1671073f@skate \
--to=thomas.petazzoni@free-electrons.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