config/kernel/linux.in
changeset 2009 7e19c1de65cd
parent 1989 f357bc3abfa6
child 2011 ab0543fc0ef0
     1.1 --- a/config/kernel/linux.in	Tue Jun 15 20:04:01 2010 +0200
     1.2 +++ b/config/kernel/linux.in	Sat Jul 03 01:15:28 2010 +0200
     1.3 @@ -83,6 +83,19 @@
     1.4        See the original announcement by Adrian Bunk in the following mailing list
     1.5        entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
     1.6  
     1.7 +config KERNEL_LINUX_CUSTOM
     1.8 +    bool
     1.9 +    prompt "custom tarball"
    1.10 +    help
    1.11 +      Use a local tarball of a complete kernel source tree.
    1.12 +
    1.13 +config KERNEL_LINUX_CUSTOM_TARBALL
    1.14 +    string
    1.15 +    prompt "Path to custom tarball"
    1.16 +    depends on KERNEL_LINUX_CUSTOM
    1.17 +    help
    1.18 +      Enter here the path to the tarball of your full kernel tree.
    1.19 +
    1.20  endchoice
    1.21  
    1.22  config KERNEL_VERSION
    1.23 @@ -144,10 +157,16 @@
    1.24  
    1.25  config KERNEL_LINUX_USE_CUSTOM_HEADERS
    1.26      bool
    1.27 -    prompt "custom, and/or pre-installed, headers tree"
    1.28 +    prompt "pre-installed headers tree"
    1.29      help
    1.30 -      If you have some kernel headers lying around, you can enter the path
    1.31 -      below.
    1.32 +      If you have some pre-installed kernel headers lying around, you can
    1.33 +      enter the path to these headers, below, they will be copied from
    1.34 +      there, and into the toolchain's sysroot.
    1.35 +      
    1.36 +      Note:
    1.37 +      This will *not* let you use a complete kernel tree!
    1.38 +      If you want to use your own full kernel tree, then you want to
    1.39 +      say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
    1.40  
    1.41  if KERNEL_LINUX_USE_CUSTOM_HEADERS
    1.42