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
45 config KERNEL_V_3_6_11
53 config KERNEL_V_3_4_26
61 config KERNEL_V_3_2_37
65 config KERNEL_V_3_1_10
69 config KERNEL_V_3_0_59
73 config KERNEL_V_2_6_39_4
77 config KERNEL_V_2_6_38_8
81 config KERNEL_V_2_6_37_6
85 config KERNEL_V_2_6_36_4
89 config KERNEL_V_2_6_33_20
93 This is primarily for the use of those people who are stuck using the
94 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
95 is welcome to use this one as well.
97 config KERNEL_V_2_6_32_60
99 prompt "2.6.32.60 (longterm)"
101 The Linux 2.6.32 tree is a "longterm" maintenance branch.
103 It is intended to fill the niche for users who are not using distribution
104 kernels but want to use a regression-free kernel for a longer time.
106 Critical bug fixes to later 2.6 releases are often ported to this branch
107 which makes 2.6.32 a very useful base for many embedded developers seeking
108 stable APIs or those who do not need the latest bleeding edge features.
110 ... and no, this kernel has not undergone any specific QA testing.
112 See the original announcement by Greg Kroah-Hartman in the following
114 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
116 config KERNEL_V_2_6_31_14
120 config KERNEL_V_2_6_27_62
122 prompt "2.6.27.62 (longterm)"
124 The Linux 2.6.27 tree is a "longterm" maintenance branch.
126 It is intended to fill the niche for users who are not using distribution
127 kernels but want to use a regression-free kernel for a longer time.
129 Critical bug fixes to later 2.6 releases are often ported to this branch
130 which makes 2.6.27 a very useful base for many embedded developers seeking
131 stable APIs or those who do not need the latest bleeding edge features.
133 ... and no, this kernel has not undergone any specific QA testing.
135 See the original announcement by Adrian Bunk in the following mailing list
137 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
139 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
140 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
142 config KERNEL_LINUX_CUSTOM
144 prompt "custom tarball or directory"
146 Use a local tarball or local kernel directory of a complete kernel source tree.
148 config KERNEL_LINUX_CUSTOM_LOCATION
150 prompt "Path to custom source, tarball or directory"
151 depends on KERNEL_LINUX_CUSTOM
153 Enter here the path to the tarball of your full kernel tree or
158 config KERNEL_VERSION
160 # Don't remove next line
161 # CT_INSERT_VERSION_STRING_BELOW
162 default "3.7.3" if KERNEL_V_3_7_3
163 default "3.7.2" if KERNEL_V_3_7_2
164 default "3.7.1" if KERNEL_V_3_7_1
165 default "3.7" if KERNEL_V_3_7
166 default "3.6.11" if KERNEL_V_3_6_11
167 default "3.5.7" if KERNEL_V_3_5_7
168 default "3.4.26" if KERNEL_V_3_4_26
169 default "3.3.8" if KERNEL_V_3_3_8
170 default "3.2.37" if KERNEL_V_3_2_37
171 default "3.1.10" if KERNEL_V_3_1_10
172 default "3.0.59" if KERNEL_V_3_0_59
173 default "2.6.39.4" if KERNEL_V_2_6_39_4
174 default "2.6.38.8" if KERNEL_V_2_6_38_8
175 default "2.6.37.6" if KERNEL_V_2_6_37_6
176 default "2.6.36.4" if KERNEL_V_2_6_36_4
177 default "2.6.33.20" if KERNEL_V_2_6_33_20
178 default "2.6.32.60" if KERNEL_V_2_6_32_60
179 default "2.6.31.14" if KERNEL_V_2_6_31_14
180 default "2.6.27.62" if KERNEL_V_2_6_27_62
181 default "custom" if KERNEL_LINUX_CUSTOM
183 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
185 if KERNEL_LINUX_USE_CUSTOM_HEADERS
187 config KERNEL_LINUX_CUSTOM_PATH
189 prompt "Path to custom headers directory/tarball"
191 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
193 config KERNEL_LINUX_CUSTOM_IS_TARBALL
195 prompt "This is a tarball"
197 If you say 'n' here, the path above is expected to point to a directory
198 containing readily prepared headers
200 If you say 'y' here, then the path above is expected to point to a
201 tarball of such a directory.
203 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
204 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
206 Now, passing a tarball around is easier than passing a directory, so
207 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
208 say 'y' here, and enter the path to this tarball below.
210 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS