From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/10] New, simpler, infrastructure for building the Linux kernel
Date: Sun, 20 Jun 2010 15:35:08 +0200 [thread overview]
Message-ID: <20100620153508.4e7e2a28@surf> (raw)
In-Reply-To: <87hbkyajnf.fsf@macbook.be.48ers.dk>
On Sat, 19 Jun 2010 21:48:20 +0200
Peter Korsgaard <jacmet@uclibc.org> wrote:
> Well, "stable" has different meanings to different people. When I think
> of stable in regard to kernels, I think of the stable at kernel.org
> releases (E.G. 2.6.x.y).
Ah, I see. For me, 2.6.x versions are also stable versions, by
oppposition with -rc versions. But ok, I've changed this.
> Thomas> I could add another option to say ? same version as kernel headers ?.
> Thomas> However, I'd prefer to keep the "BR2_LINUX_KERNEL_2_6_34" option as it
> Thomas> is: remember that in the external toolchain case, ? same version as
> Thomas> kernel headers ? doesn't make sense.
>
> Ok. You could hide the option if !internal toolchain.
Sure, done.
> Well, only add it if you need the text string for something (E.G. the
> make target). If you prefer doing it in make, then that's fine as well -
> It's not something that needs to change often.
>
> In general I think it makes sense to keep these things in Kconfig when
> you need to keep several lines in sync, and otherwise don't need to
> change anything in .mk files (E.G. when adding new kernel headers,
> busybox versions, ..).
Ok. I haven't changed this part for now.
> The point is that it isn't consistent. We don't do this for
> uclibc/busybox, and you don't do it for defconfigs in the kernel tree
> (which often are also slightly outdated).
Ok, I got rid of it.
> Thomas> make uImage only builds the uImage kernel image. make with no arguments
> Thomas> builds the default kernel image (zImage in the ARM case) and also
> Thomas> builds the modules.
>
> This seems platform/arch specific. On PPC, the default image is
> typically uImage, so make with no arguments builds uImage and modules.
>
> Does this mean that the existing advanced linux support is broken on
> ARM/uImage when using a modular kernel? - There it looks like it just
> calls 'make uImage'. I always use a nonmodular kernel, so I never
> noticed.
The current advanced thing does "make modules ; make modules_install"
when CONFIG_MODULES is enabled.
> Thomas> make uImage
> Thomas> make modules
>
> Probably better to do make; make <format> (where format is uImage/zImage/bzImage/..)
Isn't this what I'm doing already ?
Regards,
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:[~2010-06-20 13:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 18:50 [Buildroot] [pull request] Pull request for branch linux-cleanup Thomas Petazzoni
2010-06-13 18:50 ` [Buildroot] [PATCH 01/10] New, simpler, infrastructure for building the Linux kernel Thomas Petazzoni
2010-06-18 19:30 ` Peter Korsgaard
2010-06-19 14:13 ` Thomas Petazzoni
2010-06-19 19:48 ` Peter Korsgaard
2010-06-20 13:35 ` Thomas Petazzoni [this message]
2010-06-20 17:51 ` Peter Korsgaard
2010-06-20 19:22 ` Thomas Petazzoni
2010-06-20 21:08 ` Peter Korsgaard
2010-06-13 18:50 ` [Buildroot] [PATCH 02/10] Remove old Linux infrastructure Thomas Petazzoni
2010-06-13 18:50 ` [Buildroot] [PATCH 03/10] iso9660: take into account the linux changes Thomas Petazzoni
2010-06-18 19:32 ` Peter Korsgaard
2010-06-13 18:50 ` [Buildroot] [PATCH 04/10] module-init-tools: remove support for cross-depmod Thomas Petazzoni
2010-06-13 18:50 ` [Buildroot] [PATCH 05/10] module-init-tools: bump version + convert to autotools Thomas Petazzoni
2010-06-18 19:34 ` Peter Korsgaard
2010-06-13 18:50 ` [Buildroot] [PATCH 06/10] linux: Add dependency on host-module-init-tools Thomas Petazzoni
2010-06-13 18:50 ` [Buildroot] [PATCH 07/10] Add generic functions to enable/set/disable options in kconfig files Thomas Petazzoni
2010-06-13 18:50 ` [Buildroot] [PATCH 08/10] linux: adjust kernel config according to the Buildroot configuration Thomas Petazzoni
2010-06-18 19:43 ` Peter Korsgaard
2010-06-19 14:24 ` Thomas Petazzoni
2010-06-19 17:45 ` Peter Korsgaard
[not found] ` <AANLkTincS1TpfzFUHCVgD5kr8csXcHUuaQzjzOSabD6N@mail.gmail.com>
2010-06-20 7:06 ` Peter Korsgaard
2010-06-13 18:50 ` [Buildroot] [PATCH 09/10] linux: add support for linux26-{menuconfig, xconfig, gconfig} targets Thomas Petazzoni
2010-06-13 18:50 ` [Buildroot] [PATCH 10/10] linux: add support for initramfs Thomas Petazzoni
2010-06-14 1:50 ` [Buildroot] [pull request] Pull request for branch linux-cleanup Paul Jones
2010-06-18 6:46 ` Thomas Petazzoni
2010-06-20 13:37 ` Thomas Petazzoni
2010-06-20 13:51 ` Thomas Petazzoni
2010-06-20 17:52 ` Peter Korsgaard
2010-06-20 19:22 ` Thomas Petazzoni
2010-06-22 20:15 ` Thomas Petazzoni
2010-06-23 9:29 ` Peter Korsgaard
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=20100620153508.4e7e2a28@surf \
--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