1.1 --- a/config/kernel/linux.in.2 Thu Apr 28 18:57:24 2011 +0200
1.2 +++ b/config/kernel/linux.in.2 Mon Jun 27 21:03:40 2011 +0200
1.3 @@ -1,174 +1,9 @@
1.4 # Linux kernel options
1.5
1.6 -choice
1.7 - bool
1.8 - prompt "Get kernel headers from:"
1.9 -
1.10 -config KERNEL_LINUX_INSTALL
1.11 - bool
1.12 - prompt "kernel's 'headers_install'"
1.13 - help
1.14 - This will make use of the new headers_install rule in recent kernels.
1.15 - This is most probably what you want to use.
1.16 -
1.17 -config KERNEL_LINUX_USE_CUSTOM_HEADERS
1.18 - bool
1.19 - prompt "pre-installed headers tree"
1.20 - help
1.21 - If you have some pre-installed kernel headers lying around, you can
1.22 - enter the path to these headers, below, they will be copied from
1.23 - there, and into the toolchain's sysroot.
1.24 -
1.25 - Note:
1.26 - This will *not* let you use a complete kernel tree!
1.27 - If you want to use your own full kernel tree, then you want to
1.28 - say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
1.29 -
1.30 -endchoice
1.31 -
1.32 if KERNEL_LINUX_INSTALL
1.33
1.34 choice
1.35 bool
1.36 - prompt "Linux kernel version"
1.37 -# Don't remove next line
1.38 -# CT_INSERT_VERSION_BELOW
1.39 -
1.40 -config KERNEL_V_2_6_38_4
1.41 - bool
1.42 - prompt "2.6.38.4"
1.43 -
1.44 -config KERNEL_V_2_6_38_3
1.45 - bool
1.46 - prompt "2.6.38.3"
1.47 -
1.48 -config KERNEL_V_2_6_38_2
1.49 - bool
1.50 - prompt "2.6.38.2"
1.51 -
1.52 -config KERNEL_V_2_6_38_1
1.53 - bool
1.54 - prompt "2.6.38.1"
1.55 -
1.56 -config KERNEL_V_2_6_38
1.57 - bool
1.58 - prompt "2.6.38"
1.59 -
1.60 -config KERNEL_V_2_6_37_6
1.61 - bool
1.62 - prompt "2.6.37.6"
1.63 -
1.64 -config KERNEL_V_2_6_36_4
1.65 - bool
1.66 - prompt "2.6.36.4"
1.67 -
1.68 -config KERNEL_V_2_6_35_13
1.69 - bool
1.70 - prompt "2.6.35.13 (longterm)"
1.71 - help
1.72 - The Linux 2.6.35 tree is a "longterm" maintenance branch.
1.73 -
1.74 - It is intended to fill the niche for users who are not using distribution
1.75 - kernels but want to use a regression-free kernel for a longer time.
1.76 -
1.77 - Critical bug fixes to later 2.6 releases are often ported to this branch
1.78 - which makes 2.6.35 a very useful base for many embedded developers seeking
1.79 - stable APIs or those who do not need the latest bleeding edge features.
1.80 -
1.81 - ... and no, this kernel has not undergone any specific QA testing.
1.82 -
1.83 - See the original announcement by Andi Kleen in the following mailing
1.84 - list entry:
1.85 - http://marc.info/?l=linux-kernel&m=129136895415202&w=4
1.86 -
1.87 -config KERNEL_V_2_6_34_9
1.88 - bool
1.89 - prompt "2.6.34.9"
1.90 -
1.91 -config KERNEL_V_2_6_33_12
1.92 - bool
1.93 - prompt "2.6.33.12"
1.94 -
1.95 -config KERNEL_V_2_6_32_39
1.96 - bool
1.97 - prompt "2.6.32.39 (longterm)"
1.98 - help
1.99 - The Linux 2.6.32 tree is a "longterm" maintenance branch.
1.100 -
1.101 - It is intended to fill the niche for users who are not using distribution
1.102 - kernels but want to use a regression-free kernel for a longer time.
1.103 -
1.104 - Critical bug fixes to later 2.6 releases are often ported to this branch
1.105 - which makes 2.6.32 a very useful base for many embedded developers seeking
1.106 - stable APIs or those who do not need the latest bleeding edge features.
1.107 -
1.108 - ... and no, this kernel has not undergone any specific QA testing.
1.109 -
1.110 - See the original announcement by Greg Kroah-Hartman in the following
1.111 - mailing list entry:
1.112 - http://marc.info/?l=linux-kernel&m=126384198403392&w=4
1.113 -
1.114 -config KERNEL_V_2_6_31_14
1.115 - bool
1.116 - prompt "2.6.31.14"
1.117 -
1.118 -config KERNEL_V_2_6_27_58
1.119 - bool
1.120 - prompt "2.6.27.58 (longterm)"
1.121 - help
1.122 - The Linux 2.6.27 tree is a "longterm" maintenance branch.
1.123 -
1.124 - It is intended to fill the niche for users who are not using distribution
1.125 - kernels but want to use a regression-free kernel for a longer time.
1.126 -
1.127 - Critical bug fixes to later 2.6 releases are often ported to this branch
1.128 - which makes 2.6.27 a very useful base for many embedded developers seeking
1.129 - stable APIs or those who do not need the latest bleeding edge features.
1.130 -
1.131 - ... and no, this kernel has not undergone any specific QA testing.
1.132 -
1.133 - See the original announcement by Adrian Bunk in the following mailing list
1.134 - entry:
1.135 - http://marc.info/?l=linux-kernel&m=122375909403298&w=4
1.136 -
1.137 - It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
1.138 - http://marc.info/?l=linux-kernel&m=129133701916793&w=4
1.139 -
1.140 -config KERNEL_LINUX_CUSTOM
1.141 - bool
1.142 - prompt "custom tarball"
1.143 - help
1.144 - Use a local tarball of a complete kernel source tree.
1.145 -
1.146 -config KERNEL_LINUX_CUSTOM_TARBALL
1.147 - string
1.148 - prompt "Path to custom tarball"
1.149 - depends on KERNEL_LINUX_CUSTOM
1.150 - help
1.151 - Enter here the path to the tarball of your full kernel tree.
1.152 -
1.153 -endchoice
1.154 -
1.155 -config KERNEL_VERSION
1.156 - string
1.157 -# Don't remove next line
1.158 -# CT_INSERT_VERSION_STRING_BELOW
1.159 - default "2.6.38.4" if KERNEL_V_2_6_38_4
1.160 - default "2.6.38.3" if KERNEL_V_2_6_38_3
1.161 - default "2.6.38.2" if KERNEL_V_2_6_38_2
1.162 - default "2.6.38.1" if KERNEL_V_2_6_38_1
1.163 - default "2.6.38" if KERNEL_V_2_6_38
1.164 - default "2.6.37.6" if KERNEL_V_2_6_37_6
1.165 - default "2.6.36.4" if KERNEL_V_2_6_36_4
1.166 - default "2.6.35.13" if KERNEL_V_2_6_35_13
1.167 - default "2.6.34.9" if KERNEL_V_2_6_34_9
1.168 - default "2.6.33.12" if KERNEL_V_2_6_33_12
1.169 - default "2.6.32.39" if KERNEL_V_2_6_32_39
1.170 - default "2.6.31.14" if KERNEL_V_2_6_31_14
1.171 - default "2.6.27.58" if KERNEL_V_2_6_27_58
1.172 -
1.173 -choice
1.174 - bool
1.175 prompt "Kernel verbosity:"
1.176 default KERNEL_LINUX_VERBOSITY_0
1.177
1.178 @@ -207,31 +42,3 @@
1.179 here to have an extra check passed onto the headers.
1.180
1.181 endif # KERNEL_LINUX_INSTALL
1.182 -
1.183 -if KERNEL_LINUX_USE_CUSTOM_HEADERS
1.184 -
1.185 -config KERNEL_LINUX_CUSTOM_IS_TARBALL
1.186 - bool
1.187 - prompt "This is a tarball"
1.188 - default n
1.189 - help
1.190 - If you say 'n' here, the path below is expected to point to a directory
1.191 - containing readily prepared headers
1.192 -
1.193 - If you say 'y' here, then the path below is expected to point to a
1.194 - tarball of such a directory.
1.195 -
1.196 - Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
1.197 - say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
1.198 -
1.199 - Now, passing a tarball around is easier than passing a directory, so
1.200 - if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
1.201 - say 'y' here, and enter the path to this tarball below.
1.202 -
1.203 -config KERNEL_LINUX_CUSTOM_PATH
1.204 - string
1.205 - prompt "Path to custom headers directory/tarball"
1.206 - help
1.207 - See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
1.208 -
1.209 -endif # KERNEL_LINUX_USE_CUSTOM_HEADERS