3 ## select KERNEL_SUPPORTS_SHARED_LIBS
5 ## help Build a toolchain targeting systems running Linux as a kernel.
7 config KERNEL_LINUX_USE_CUSTOM_HEADERS
9 prompt "Use pre-installed headers tree (OBSOLETE)"
12 If you have some pre-installed kernel headers lying around, you can
13 enter the path to these headers, below, they will be copied from
14 there, and into the toolchain's sysroot.
17 This will *not* let you use a complete kernel tree!
18 If you want to use your own full kernel tree, then you want to say 'N'
19 here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
21 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
25 prompt "Linux kernel version"
26 # Don't remove next line
27 # CT_INSERT_VERSION_BELOW
37 config KERNEL_V_3_6_11
45 config KERNEL_V_3_4_24
53 config KERNEL_V_3_2_36
57 config KERNEL_V_3_1_10
61 config KERNEL_V_3_0_57
65 config KERNEL_V_2_6_39_4
69 config KERNEL_V_2_6_38_8
73 config KERNEL_V_2_6_37_6
77 config KERNEL_V_2_6_36_4
81 config KERNEL_V_2_6_33_20
85 This is primarily for the use of those people who are stuck using the
86 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
87 is welcome to use this one as well.
89 config KERNEL_V_2_6_32_60
91 prompt "2.6.32.60 (longterm)"
93 The Linux 2.6.32 tree is a "longterm" maintenance branch.
95 It is intended to fill the niche for users who are not using distribution
96 kernels but want to use a regression-free kernel for a longer time.
98 Critical bug fixes to later 2.6 releases are often ported to this branch
99 which makes 2.6.32 a very useful base for many embedded developers seeking
100 stable APIs or those who do not need the latest bleeding edge features.
102 ... and no, this kernel has not undergone any specific QA testing.
104 See the original announcement by Greg Kroah-Hartman in the following
106 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
108 config KERNEL_V_2_6_31_14
112 config KERNEL_V_2_6_27_62
114 prompt "2.6.27.62 (longterm)"
116 The Linux 2.6.27 tree is a "longterm" maintenance branch.
118 It is intended to fill the niche for users who are not using distribution
119 kernels but want to use a regression-free kernel for a longer time.
121 Critical bug fixes to later 2.6 releases are often ported to this branch
122 which makes 2.6.27 a very useful base for many embedded developers seeking
123 stable APIs or those who do not need the latest bleeding edge features.
125 ... and no, this kernel has not undergone any specific QA testing.
127 See the original announcement by Adrian Bunk in the following mailing list
129 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
131 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
132 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
134 config KERNEL_LINUX_CUSTOM
136 prompt "custom tarball or directory"
138 Use a local tarball or local kernel directory of a complete kernel source tree.
140 config KERNEL_LINUX_CUSTOM_LOCATION
142 prompt "Path to custom source, tarball or directory"
143 depends on KERNEL_LINUX_CUSTOM
145 Enter here the path to the tarball of your full kernel tree or
150 config KERNEL_VERSION
152 # Don't remove next line
153 # CT_INSERT_VERSION_STRING_BELOW
154 default "3.7.1" if KERNEL_V_3_7_1
155 default "3.7" if KERNEL_V_3_7
156 default "3.6.11" if KERNEL_V_3_6_11
157 default "3.5.7" if KERNEL_V_3_5_7
158 default "3.4.24" if KERNEL_V_3_4_24
159 default "3.3.8" if KERNEL_V_3_3_8
160 default "3.2.36" if KERNEL_V_3_2_36
161 default "3.1.10" if KERNEL_V_3_1_10
162 default "3.0.57" if KERNEL_V_3_0_57
163 default "2.6.39.4" if KERNEL_V_2_6_39_4
164 default "2.6.38.8" if KERNEL_V_2_6_38_8
165 default "2.6.37.6" if KERNEL_V_2_6_37_6
166 default "2.6.36.4" if KERNEL_V_2_6_36_4
167 default "2.6.33.20" if KERNEL_V_2_6_33_20
168 default "2.6.32.60" if KERNEL_V_2_6_32_60
169 default "2.6.31.14" if KERNEL_V_2_6_31_14
170 default "2.6.27.62" if KERNEL_V_2_6_27_62
171 default "custom" if KERNEL_LINUX_CUSTOM
173 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
175 if KERNEL_LINUX_USE_CUSTOM_HEADERS
177 config KERNEL_LINUX_CUSTOM_PATH
179 prompt "Path to custom headers directory/tarball"
181 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
183 config KERNEL_LINUX_CUSTOM_IS_TARBALL
185 prompt "This is a tarball"
187 If you say 'n' here, the path above is expected to point to a directory
188 containing readily prepared headers
190 If you say 'y' here, then the path above is expected to point to a
191 tarball of such a directory.
193 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
194 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
196 Now, passing a tarball around is easier than passing a directory, so
197 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
198 say 'y' here, and enter the path to this tarball below.
200 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS