crosstool-ng/config/kernel/linux.in

# Linux kernel options

# Linux kernel options

config KERNEL_linux
    select KERNEL_SUPPORTS_SHARED_LIBS
    help
      Build a toolchain targeting systems running Linux as a kernel.

choice
    bool
    prompt "Get kernel headers from:"

config KERNEL_LINUX_INSTALL
    bool
    prompt "kernel's 'headers_install'"
    help
      This will make use of the new headers_install rule in recent kernels.
      This is most probably what you want to use.

if KERNEL_LINUX_INSTALL

config KERNEL_LINUX_INSTALL_CHECK
    bool
    prompt "Check installed headers"
    default y
    help
      If you are in doubt that installed headers are buggy, say 'Y'
      here to have an extra check passed onto the headers.

choice
    bool
    prompt "Linux kernel version"
# Don't remove next line
# CT_INSERT_VERSION_BELOW

config KERNEL_V_2_6_31_5
    bool
    prompt "2.6.31.5"

config KERNEL_V_2_6_31_4
    bool
    prompt "2.6.31.4"

config KERNEL_V_2_6_31_3
    bool
    prompt "2.6.31.3"

config KERNEL_V_2_6_31_2
    bool
    prompt "2.6.31.2"

config KERNEL_V_2_6_31_1
    bool
    prompt "2.6.31.1"

config KERNEL_V_2_6_31
    bool
    prompt "2.6.31"

config KERNEL_V_3_6_30_9
    bool
    prompt "3.6.30.9"

config KERNEL_V_3_6_30_8
    bool
    prompt "3.6.30.8"

config KERNEL_V_3_6_30_7
    bool
    prompt "3.6.30.7"

config KERNEL_V_2_6_30_6
    bool
    prompt "2.6.30.6"

config KERNEL_V_2_6_30_5
    bool
    prompt "2.6.30.5"

config KERNEL_V_2_6_30_4
    bool
    prompt "2.6.30.4"

config KERNEL_V_2_6_30_3
    bool
    prompt "2.6.30.3"

config KERNEL_V_2_6_30_2
    bool
    prompt "2.6.30.2"

config KERNEL_V_2_6_30_1
    bool
    prompt "2.6.30.1"

config KERNEL_V_2_6_30
    bool
    prompt "2.6.30"

config KERNEL_V_2_6_29_6
    bool
    prompt "2.6.29.6"

config KERNEL_V_2_6_28_10
    bool
    prompt "2.6.28.10"

config KERNEL_V_2_6_27_38
    bool
    prompt "2.6.27.38 (long-term stable)"

endchoice

config KERNEL_VERSION
    string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
    default "2.6.31.5" if KERNEL_V_2_6_31_5
    default "2.6.31.4" if KERNEL_V_2_6_31_4
    default "2.6.31.3" if KERNEL_V_2_6_31_3
    default "2.6.31.2" if KERNEL_V_2_6_31_2
    default "2.6.31.1" if KERNEL_V_2_6_31_1
    default "2.6.31" if KERNEL_V_2_6_31
    default "3.6.30.9" if KERNEL_V_3_6_30_9
    default "3.6.30.8" if KERNEL_V_3_6_30_8
    default "3.6.30.7" if KERNEL_V_3_6_30_7
    default "2.6.30.6" if KERNEL_V_2_6_30_6
    default "2.6.30.5" if KERNEL_V_2_6_30_5
    default "2.6.30.4" if KERNEL_V_2_6_30_4
    default "2.6.30.3" if KERNEL_V_2_6_30_3
    default "2.6.30.2" if KERNEL_V_2_6_30_2
    default "2.6.30.1" if KERNEL_V_2_6_30_1
    default "2.6.30" if KERNEL_V_2_6_30
    default "2.6.29.6" if KERNEL_V_2_6_29_6
    default "2.6.28.10" if KERNEL_V_2_6_28_10
    default "2.6.27.38" if KERNEL_V_2_6_27_38

choice
    bool
    prompt "Kernel verbosity:"
    default KERNEL_LINUX_VERBOSITY_0

config KERNEL_LINUX_VERBOSITY_0
    bool
    prompt "Simplified"
    help
      Print simplified command lines.

config KERNEL_LINUX_VERBOSITY_1
    bool
    prompt "Full commands"
    help
      Print full command lines.

config KERNEL_LINUX_VERBOSITY_2
    bool
    prompt "Exec reasons"
    help
      Print the reasons why a make target is rebuild.

endchoice

config KERNEL_LINUX_VERBOSE_LEVEL
    int
    default 0 if KERNEL_LINUX_VERBOSITY_0
    default 1 if KERNEL_LINUX_VERBOSITY_1
    default 2 if KERNEL_LINUX_VERBOSITY_2

endif

config KERNEL_LINUX_USE_CUSTOM_HEADERS
    bool
    prompt "Use custom headers"
    help
      If you have some kernel headers lying around, you can enter the path
      below.

if KERNEL_LINUX_USE_CUSTOM_HEADERS

config KERNEL_LINUX_CUSTOM_IS_TARBALL
    bool
    prompt "This is a tarball"
    default n
    help
      If you say 'n' here, the path below is expected to point to a directory
      containing readily prepared headers
      
      If you say 'y' here, then the path below is expected to point to a
      tarball of such a directory.
      
      Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
      say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
      
      Now, passing a tarball around is easier than passing a directory, so
      if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
      say 'y' here, and enter the path to this tarball below.

config KERNEL_LINUX_CUSTOM_PATH
    string
    prompt "Path to custom headers directory/tarball"
    help
      See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.

endif # KERNEL_LINUX_USE_CUSTOM_DIR

endchoice