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
49 config KERNEL_V_3_2_16
53 config KERNEL_V_3_1_10
57 config KERNEL_V_3_0_30
61 config KERNEL_V_2_6_39_4
65 config KERNEL_V_2_6_38_8
69 config KERNEL_V_2_6_37_6
73 config KERNEL_V_2_6_36_4
77 config KERNEL_V_2_6_33_20
81 This is primarily for the use of those people who are stuck using the
82 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
83 is welcome to use this one as well.
85 config KERNEL_V_2_6_32_59
87 prompt "2.6.32.59 (longterm)"
89 The Linux 2.6.32 tree is a "longterm" maintenance branch.
91 It is intended to fill the niche for users who are not using distribution
92 kernels but want to use a regression-free kernel for a longer time.
94 Critical bug fixes to later 2.6 releases are often ported to this branch
95 which makes 2.6.32 a very useful base for many embedded developers seeking
96 stable APIs or those who do not need the latest bleeding edge features.
98 ... and no, this kernel has not undergone any specific QA testing.
100 See the original announcement by Greg Kroah-Hartman in the following
102 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
104 config KERNEL_V_2_6_31_14
108 config KERNEL_V_2_6_27_62
110 prompt "2.6.27.62 (longterm)"
112 The Linux 2.6.27 tree is a "longterm" maintenance branch.
114 It is intended to fill the niche for users who are not using distribution
115 kernels but want to use a regression-free kernel for a longer time.
117 Critical bug fixes to later 2.6 releases are often ported to this branch
118 which makes 2.6.27 a very useful base for many embedded developers seeking
119 stable APIs or those who do not need the latest bleeding edge features.
121 ... and no, this kernel has not undergone any specific QA testing.
123 See the original announcement by Adrian Bunk in the following mailing list
125 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
127 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
128 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
130 config KERNEL_LINUX_CUSTOM
132 prompt "custom tarball or directory"
134 Use a local tarball or local kernel directory of a complete kernel source tree.
136 config KERNEL_LINUX_CUSTOM_LOCATION
138 prompt "Path to custom source, tarball or directory"
139 depends on KERNEL_LINUX_CUSTOM
141 Enter here the path to the tarball of your full kernel tree or
146 config KERNEL_VERSION
148 # Don't remove next line
149 # CT_INSERT_VERSION_STRING_BELOW
150 default "3.3.4" if KERNEL_V_3_3_4
151 default "3.3.3" if KERNEL_V_3_3_3
152 default "3.3.2" if KERNEL_V_3_3_2
153 default "3.3.1" if KERNEL_V_3_3_1
154 default "3.3" if KERNEL_V_3_3
155 default "3.2.16" if KERNEL_V_3_2_16
156 default "3.1.10" if KERNEL_V_3_1_10
157 default "3.0.30" if KERNEL_V_3_0_30
158 default "2.6.39.4" if KERNEL_V_2_6_39_4
159 default "2.6.38.8" if KERNEL_V_2_6_38_8
160 default "2.6.37.6" if KERNEL_V_2_6_37_6
161 default "2.6.36.4" if KERNEL_V_2_6_36_4
162 default "2.6.33.20" if KERNEL_V_2_6_33_20
163 default "2.6.32.59" if KERNEL_V_2_6_32_59
164 default "2.6.31.14" if KERNEL_V_2_6_31_14
165 default "2.6.27.62" if KERNEL_V_2_6_27_62
166 default "custom" if KERNEL_LINUX_CUSTOM
168 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
170 if KERNEL_LINUX_USE_CUSTOM_HEADERS
172 config KERNEL_LINUX_CUSTOM_PATH
174 prompt "Path to custom headers directory/tarball"
176 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
178 config KERNEL_LINUX_CUSTOM_IS_TARBALL
180 prompt "This is a tarball"
182 If you say 'n' here, the path above is expected to point to a directory
183 containing readily prepared headers
185 If you say 'y' here, then the path above is expected to point to a
186 tarball of such a directory.
188 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
189 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
191 Now, passing a tarball around is easier than passing a directory, so
192 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
193 say 'y' here, and enter the path to this tarball below.
195 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS