From c4933a400cc5911014d9cebb0a2a269c0a8747aa Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Thu, 17 Jun 2010 18:30:09 +0200 Subject: kernel/linux: allow headers from full custom source tree Accept a local tarball name as the source of the Linux kernel headers, rather than forcing the user to use either an upstream tarball, or a local pre-installed headers tree. --- config/kernel/linux.in | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) (limited to 'config/kernel') diff --git a/config/kernel/linux.in b/config/kernel/linux.in index d5afdf9a..da17dbbc 100644 --- a/config/kernel/linux.in +++ b/config/kernel/linux.in @@ -83,6 +83,19 @@ config KERNEL_V_2_6_27_47 See the original announcement by Adrian Bunk in the following mailing list entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2 +config KERNEL_LINUX_CUSTOM + bool + prompt "custom tarball" + help + Use a local tarball of a complete kernel source tree. + +config KERNEL_LINUX_CUSTOM_TARBALL + string + prompt "Path to custom tarball" + depends on KERNEL_LINUX_CUSTOM + help + Enter here the path to the tarball of your full kernel tree. + endchoice config KERNEL_VERSION @@ -144,10 +157,16 @@ endif # KERNEL_LINUX_INSTALL config KERNEL_LINUX_USE_CUSTOM_HEADERS bool - prompt "custom, and/or pre-installed, headers tree" + prompt "pre-installed headers tree" help - If you have some kernel headers lying around, you can enter the path - below. + If you have some pre-installed kernel headers lying around, you can + enter the path to these headers, below, they will be copied from + there, and into the toolchain's sysroot. + + Note: + This will *not* let you use a complete kernel tree! + If you want to use your own full kernel tree, then you want to + say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM. if KERNEL_LINUX_USE_CUSTOM_HEADERS -- cgit v1.2.3