config/kernel/linux.in
author Arnaud Lacombe <lacombar@gmail.com>
Mon Aug 02 21:38:32 2010 +0200 (2010-08-02)
changeset 2062 11348ef5f0ac
parent 2011 ab0543fc0ef0
child 2063 57d5da4e4d25
permissions -rw-r--r--
kernel/linux: 2.6.32.17, 2.6.33.7, 2.6.34.2 and 2.6.35 are out !

Signed-off-by: Arnaud Lacombe <lacombar@gmail.com>
[Yann E. MORIN: also add latest 2.6.27.49]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
     1 # Linux kernel options
     2 
     3 # Linux kernel options
     4 
     5 config KERNEL_linux
     6     select KERNEL_SUPPORTS_SHARED_LIBS
     7     help
     8       Build a toolchain targeting systems running Linux as a kernel.
     9 
    10 choice
    11     bool
    12     prompt "Get kernel headers from:"
    13 
    14 config KERNEL_LINUX_INSTALL
    15     bool
    16     prompt "kernel's 'headers_install'"
    17     help
    18       This will make use of the new headers_install rule in recent kernels.
    19       This is most probably what you want to use.
    20 
    21 if KERNEL_LINUX_INSTALL
    22 
    23 choice
    24     bool
    25     prompt "Linux kernel version"
    26 # Don't remove next line
    27 # CT_INSERT_VERSION_BELOW
    28 
    29 config KERNEL_V_2_6_35
    30     bool
    31     prompt "2.6.35"
    32 
    33 config KERNEL_V_2_6_34_2
    34     bool
    35     prompt "2.6.34.2"
    36 
    37 config KERNEL_V_2_6_34_1
    38     bool
    39     prompt "2.6.34.1"
    40 
    41 config KERNEL_V_2_6_34
    42     bool
    43     prompt "2.6.34"
    44 
    45 config KERNEL_V_2_6_33_7
    46     bool
    47     prompt "2.6.33.7"
    48 
    49 config KERNEL_V_2_6_33_6
    50     bool
    51     prompt "2.6.33.6"
    52 
    53 config KERNEL_V_2_6_33_5
    54     bool
    55     prompt "2.6.33.5"
    56 
    57 config KERNEL_V_2_6_33_4
    58     bool
    59     prompt "2.6.33.4"
    60 
    61 config KERNEL_V_2_6_33_3
    62     bool
    63     prompt "2.6.33.3"
    64 
    65 config KERNEL_V_2_6_33_2
    66     bool
    67     prompt "2.6.33.2"
    68 
    69 config KERNEL_V_2_6_33_1
    70     bool
    71     prompt "2.6.33.1"
    72 
    73 config KERNEL_V_2_6_33
    74     bool
    75     prompt "2.6.33"
    76 
    77 config KERNEL_V_2_6_32_17
    78     bool
    79     prompt "2.6.32.17"
    80 
    81 config KERNEL_V_2_6_31_14
    82     bool
    83     prompt "2.6.31.14"
    84 
    85 config KERNEL_V_2_6_30_10
    86     bool
    87     prompt "2.6.30.10"
    88 
    89 config KERNEL_V_2_6_27_49
    90     bool
    91     prompt "2.6.27.49 (long-term stable)"
    92     help
    93       The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
    94       It is intended to fill the niche for users who are not using distribution
    95       kernels but want to use a regression-free kernel for a longer time.
    96       
    97       Critical bug fixes to later 2.6 releases are often ported to this branch
    98       which makes 2.6.27 a very useful base for many embedded developers seeking
    99       stable APIs or those who do not need the latest bleeding edge features.
   100       
   101       ... and no, this kernel has not undergone any specific QA testing.
   102       
   103       See the original announcement by Adrian Bunk in the following mailing list
   104       entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
   105 
   106 config KERNEL_LINUX_CUSTOM
   107     bool
   108     prompt "custom tarball"
   109     help
   110       Use a local tarball of a complete kernel source tree.
   111 
   112 config KERNEL_LINUX_CUSTOM_TARBALL
   113     string
   114     prompt "Path to custom tarball"
   115     depends on KERNEL_LINUX_CUSTOM
   116     help
   117       Enter here the path to the tarball of your full kernel tree.
   118 
   119 endchoice
   120 
   121 config KERNEL_VERSION
   122     string
   123 # Don't remove next line
   124 # CT_INSERT_VERSION_STRING_BELOW
   125     default "2.6.35" if KERNEL_V_2_6_35
   126     default "2.6.34.2" if KERNEL_V_2_6_34_2
   127     default "2.6.34.1" if KERNEL_V_2_6_34_1
   128     default "2.6.34" if KERNEL_V_2_6_34
   129     default "2.6.33.7" if KERNEL_V_2_6_33_7
   130     default "2.6.33.6" if KERNEL_V_2_6_33_6
   131     default "2.6.33.5" if KERNEL_V_2_6_33_5
   132     default "2.6.33.4" if KERNEL_V_2_6_33_4
   133     default "2.6.33.3" if KERNEL_V_2_6_33_3
   134     default "2.6.33.2" if KERNEL_V_2_6_33_2
   135     default "2.6.33.1" if KERNEL_V_2_6_33_1
   136     default "2.6.33" if KERNEL_V_2_6_33
   137     default "2.6.32.17" if KERNEL_V_2_6_32_17
   138     default "2.6.31.14" if KERNEL_V_2_6_31_14
   139     default "2.6.30.10" if KERNEL_V_2_6_30_10
   140     default "2.6.27.49" if KERNEL_V_2_6_27_49
   141 
   142 choice
   143     bool
   144     prompt "Kernel verbosity:"
   145     default KERNEL_LINUX_VERBOSITY_0
   146 
   147 config KERNEL_LINUX_VERBOSITY_0
   148     bool
   149     prompt "Simplified"
   150     help
   151       Print simplified command lines.
   152 
   153 config KERNEL_LINUX_VERBOSITY_1
   154     bool
   155     prompt "Full commands"
   156     help
   157       Print full command lines.
   158 
   159 config KERNEL_LINUX_VERBOSITY_2
   160     bool
   161     prompt "Exec reasons"
   162     help
   163       Print the reasons why a make target is rebuild.
   164 
   165 endchoice
   166 
   167 config KERNEL_LINUX_VERBOSE_LEVEL
   168     int
   169     default 0 if KERNEL_LINUX_VERBOSITY_0
   170     default 1 if KERNEL_LINUX_VERBOSITY_1
   171     default 2 if KERNEL_LINUX_VERBOSITY_2
   172 
   173 config KERNEL_LINUX_INSTALL_CHECK
   174     bool
   175     prompt "Check installed headers"
   176     default y
   177     help
   178       If you are in doubt that installed headers are buggy, say 'Y'
   179       here to have an extra check passed onto the headers.
   180 
   181 endif # KERNEL_LINUX_INSTALL
   182 
   183 config KERNEL_LINUX_USE_CUSTOM_HEADERS
   184     bool
   185     prompt "pre-installed headers tree"
   186     help
   187       If you have some pre-installed kernel headers lying around, you can
   188       enter the path to these headers, below, they will be copied from
   189       there, and into the toolchain's sysroot.
   190       
   191       Note:
   192       This will *not* let you use a complete kernel tree!
   193       If you want to use your own full kernel tree, then you want to
   194       say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
   195 
   196 if KERNEL_LINUX_USE_CUSTOM_HEADERS
   197 
   198 config KERNEL_LINUX_CUSTOM_IS_TARBALL
   199     bool
   200     prompt "This is a tarball"
   201     default n
   202     help
   203       If you say 'n' here, the path below is expected to point to a directory
   204       containing readily prepared headers
   205       
   206       If you say 'y' here, then the path below is expected to point to a
   207       tarball of such a directory.
   208       
   209       Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
   210       say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
   211       
   212       Now, passing a tarball around is easier than passing a directory, so
   213       if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
   214       say 'y' here, and enter the path to this tarball below.
   215 
   216 config KERNEL_LINUX_CUSTOM_PATH
   217     string
   218     prompt "Path to custom headers directory/tarball"
   219     help
   220       See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
   221 
   222 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS
   223 
   224 endchoice