Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] board: add support for ARC AXS101 and AXS103 Software Development Platforms
Date: Tue, 4 Aug 2015 13:37:04 +0000	[thread overview]
Message-ID: <1438695423.22313.22.camel@synopsys.com> (raw)
In-Reply-To: <20150804152428.0c0d4de7@free-electrons.com>

Hi Thomas,

On Tue, 2015-08-04 at 15:24 +0200, Thomas Petazzoni wrote:
> Dear Alexey Brodkin,

> > > Please force the version of the kernel headers, so that they match the
> > > kernel being built.
> > 
> > Well you see the problem here is we do need yet to be released Linux v4.2
> > because that's where both boards are finally exist.
> > 
> > So once v4.2 is released (in a couple of weeks now) and Buildroot is updated
> > I would assume v4.2 headers will become default version, right?
> > So then we're golden and there's no need to update these defconfigs.
> 
> You're wrong. After 4.2 becomes the default version, 4.3 will become
> the default version. And then your defconfigs are broken.

Hw, I do understand your concern with implicitly specified version of
kernel/headers but what I meant if I use "make savedefconfig" it eliminates
versions if they match today's defaults.

For example if today I select
--------->8---------
BR2_LINUX_KERNEL_VERSION="4.1.3"
BR2_DEFAULT_KERNEL_HEADERS="4.1.3"
--------->8---------

Then defconfig generated by "make savedefconfig" will be:
--------->8---------
BR2_arcle=y
BR2_TARGET_GENERIC_HOSTNAME="axs101"
BR2_TARGET_GENERIC_ISSUE="Welcome to the ARC Software Development Platform"
BR2_SYSTEM_DHCP="eth0"
BR2_ROOTFS_OVERLAY="board/synopsys/axs10x/fs-overlay"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_DEFCONFIG="axs101"
BR2_TARGET_ROOTFS_INITRAMFS=y
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="axs101"
--------->8---------

Note there's no version of kernel/headers.

So now if I understood you correctly you propose to insert:
--------->8---------
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.2-rc5"
BR2_DEFAULT_KERNEL_HEADERS="4.1.3"
--------->8---------

in defconfigs today and later once v4.2 is released change defconfigs
like that:
--------->8---------
BR2_LINUX_KERNEL_VERSION="4.2.0"
BR2_DEFAULT_KERNEL_HEADERS="4.2.0"
--------->8---------

Right?

-Alexey

  reply	other threads:[~2015-08-04 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 12:00 [Buildroot] [PATCH] board: add support for ARC AXS101 and AXS103 Software Development Platforms Alexey Brodkin
2015-08-04 12:57 ` Thomas Petazzoni
2015-08-04 13:17   ` Alexey Brodkin
2015-08-04 13:24     ` Thomas Petazzoni
2015-08-04 13:37       ` Alexey Brodkin [this message]
2015-08-04 13:55         ` Thomas Petazzoni
2015-08-04 14:12           ` Alexey Brodkin

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=1438695423.22313.22.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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