From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from optimeas.de ([78.46.18.2])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <matthias.klein@optimeas.de>) id 1US2ef-0001Mc-BN
	for ptxdist@pengutronix.de; Tue, 16 Apr 2013 11:58:25 +0200
Received: from [127.0.0.1] (ip-109-90-243-32.unitymediagroup.de
	[109.90.243.32])
	by optimeas.de (Postfix) with ESMTPSA id C732F4207A56
	for <ptxdist@pengutronix.de>; Tue, 16 Apr 2013 11:58:19 +0200 (CEST)
Message-ID: <516D20BB.5000108@optimeas.de>
Date: Tue, 16 Apr 2013 11:58:19 +0200
From: Matthias Klein <matthias.klein@optimeas.de>
MIME-Version: 1.0
Subject: [ptxdist] Kernel headers version in OSELAS toolchain & kernel
 version in the BSP
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

Hello,

while reading the AppNote "Building Toolchain" I came across the section 
about the naming convention:

The last part (kernel-3.6) defines the kernel header in use for this 
toolchain. This is important, as applications
built with this toolchains must be ran at least on this kernel revision.

That means when I use the toolchain 
arm-cortexa8-linux-gnueabihf_gcc-4.7.3_glibc-2.16.0_binutils-2.22_kernel-3.6-sanitized 
from 2012.12.1
to build a BSP with a 3.4 kernel is wrong? I have done this without any 
problem so far.

What is the recommended approach if I run in such a version conflict?
- Use older toolchains which require a different kernel version?
- Or can I simply adjust / create a new config file for e.g. kernel 3.4 ?

In the ptxconfig file are 2 kernel versions. From the upper toolchain 
example:

PTXCONF_GLIBC_ENABLE_KERNEL="2.6.32"
and
PTXCONF_KERNEL_HEADERS_VERSION="3.6"

What is the difference ?

What speaks against using a very low kernel version for building the 
toolchain ?


Thanks for any tips!

Best regards,

Matthias


-- 
ptxdist mailing list
ptxdist@pengutronix.de