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_2_20
49 config KERNEL_V_3_1_10
53 config KERNEL_V_3_0_34
57 config KERNEL_V_2_6_39_4
61 config KERNEL_V_2_6_38_8
65 config KERNEL_V_2_6_37_6
69 config KERNEL_V_2_6_36_4
73 config KERNEL_V_2_6_33_20
77 This is primarily for the use of those people who are stuck using the
78 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
79 is welcome to use this one as well.
81 config KERNEL_V_2_6_32_59
83 prompt "2.6.32.59 (longterm)"
85 The Linux 2.6.32 tree is a "longterm" maintenance branch.
87 It is intended to fill the niche for users who are not using distribution
88 kernels but want to use a regression-free kernel for a longer time.
90 Critical bug fixes to later 2.6 releases are often ported to this branch
91 which makes 2.6.32 a very useful base for many embedded developers seeking
92 stable APIs or those who do not need the latest bleeding edge features.
94 ... and no, this kernel has not undergone any specific QA testing.
96 See the original announcement by Greg Kroah-Hartman in the following
98 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
100 config KERNEL_V_2_6_31_14
104 config KERNEL_V_2_6_27_62
106 prompt "2.6.27.62 (longterm)"
108 The Linux 2.6.27 tree is a "longterm" maintenance branch.
110 It is intended to fill the niche for users who are not using distribution
111 kernels but want to use a regression-free kernel for a longer time.
113 Critical bug fixes to later 2.6 releases are often ported to this branch
114 which makes 2.6.27 a very useful base for many embedded developers seeking
115 stable APIs or those who do not need the latest bleeding edge features.
117 ... and no, this kernel has not undergone any specific QA testing.
119 See the original announcement by Adrian Bunk in the following mailing list
121 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
123 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
124 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
126 config KERNEL_LINUX_CUSTOM
128 prompt "custom tarball or directory"
130 Use a local tarball or local kernel directory of a complete kernel source tree.
132 config KERNEL_LINUX_CUSTOM_LOCATION
134 prompt "Path to custom source, tarball or directory"
135 depends on KERNEL_LINUX_CUSTOM
137 Enter here the path to the tarball of your full kernel tree or
142 config KERNEL_VERSION
144 # Don't remove next line
145 # CT_INSERT_VERSION_STRING_BELOW
146 default "3.4.2" if KERNEL_V_3_4_2
147 default "3.4.1" if KERNEL_V_3_4_1
148 default "3.4" if KERNEL_V_3_4
149 default "3.3.8" if KERNEL_V_3_3_8
150 default "3.2.20" if KERNEL_V_3_2_20
151 default "3.1.10" if KERNEL_V_3_1_10
152 default "3.0.34" if KERNEL_V_3_0_34
153 default "2.6.39.4" if KERNEL_V_2_6_39_4
154 default "2.6.38.8" if KERNEL_V_2_6_38_8
155 default "2.6.37.6" if KERNEL_V_2_6_37_6
156 default "2.6.36.4" if KERNEL_V_2_6_36_4
157 default "2.6.33.20" if KERNEL_V_2_6_33_20
158 default "2.6.32.59" if KERNEL_V_2_6_32_59
159 default "2.6.31.14" if KERNEL_V_2_6_31_14
160 default "2.6.27.62" if KERNEL_V_2_6_27_62
161 default "custom" if KERNEL_LINUX_CUSTOM
163 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
165 if KERNEL_LINUX_USE_CUSTOM_HEADERS
167 config KERNEL_LINUX_CUSTOM_PATH
169 prompt "Path to custom headers directory/tarball"
171 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
173 config KERNEL_LINUX_CUSTOM_IS_TARBALL
175 prompt "This is a tarball"
177 If you say 'n' here, the path above is expected to point to a directory
178 containing readily prepared headers
180 If you say 'y' here, then the path above is expected to point to a
181 tarball of such a directory.
183 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
184 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
186 Now, passing a tarball around is easier than passing a directory, so
187 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
188 say 'y' here, and enter the path to this tarball below.
190 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS