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_2_14
41 config KERNEL_V_3_1_10
45 config KERNEL_V_3_0_27
49 config KERNEL_V_2_6_39_4
53 config KERNEL_V_2_6_38_8
57 config KERNEL_V_2_6_37_6
61 config KERNEL_V_2_6_36_4
65 config KERNEL_V_2_6_33_20
69 This is primarily for the use of those people who are stuck using the
70 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
71 is welcome to use this one as well.
73 config KERNEL_V_2_6_32_59
75 prompt "2.6.32.59 (longterm)"
77 The Linux 2.6.32 tree is a "longterm" maintenance branch.
79 It is intended to fill the niche for users who are not using distribution
80 kernels but want to use a regression-free kernel for a longer time.
82 Critical bug fixes to later 2.6 releases are often ported to this branch
83 which makes 2.6.32 a very useful base for many embedded developers seeking
84 stable APIs or those who do not need the latest bleeding edge features.
86 ... and no, this kernel has not undergone any specific QA testing.
88 See the original announcement by Greg Kroah-Hartman in the following
90 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
92 config KERNEL_V_2_6_31_14
96 config KERNEL_V_2_6_27_62
98 prompt "2.6.27.62 (longterm)"
100 The Linux 2.6.27 tree is a "longterm" maintenance branch.
102 It is intended to fill the niche for users who are not using distribution
103 kernels but want to use a regression-free kernel for a longer time.
105 Critical bug fixes to later 2.6 releases are often ported to this branch
106 which makes 2.6.27 a very useful base for many embedded developers seeking
107 stable APIs or those who do not need the latest bleeding edge features.
109 ... and no, this kernel has not undergone any specific QA testing.
111 See the original announcement by Adrian Bunk in the following mailing list
113 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
115 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
116 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
118 config KERNEL_LINUX_CUSTOM
120 prompt "custom tarball or directory"
122 Use a local tarball or local kernel directory of a complete kernel source tree.
124 config KERNEL_LINUX_CUSTOM_LOCATION
126 prompt "Path to custom source, tarball or directory"
127 depends on KERNEL_LINUX_CUSTOM
129 Enter here the path to the tarball of your full kernel tree or
134 config KERNEL_VERSION
136 # Don't remove next line
137 # CT_INSERT_VERSION_STRING_BELOW
138 default "3.3.1" if KERNEL_V_3_3_1
139 default "3.3" if KERNEL_V_3_3
140 default "3.2.14" if KERNEL_V_3_2_14
141 default "3.1.10" if KERNEL_V_3_1_10
142 default "3.0.27" if KERNEL_V_3_0_27
143 default "2.6.39.4" if KERNEL_V_2_6_39_4
144 default "2.6.38.8" if KERNEL_V_2_6_38_8
145 default "2.6.37.6" if KERNEL_V_2_6_37_6
146 default "2.6.36.4" if KERNEL_V_2_6_36_4
147 default "2.6.33.20" if KERNEL_V_2_6_33_20
148 default "2.6.32.59" if KERNEL_V_2_6_32_59
149 default "2.6.31.14" if KERNEL_V_2_6_31_14
150 default "2.6.27.62" if KERNEL_V_2_6_27_62
151 default "custom" if KERNEL_LINUX_CUSTOM
153 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
155 if KERNEL_LINUX_USE_CUSTOM_HEADERS
157 config KERNEL_LINUX_CUSTOM_PATH
159 prompt "Path to custom headers directory/tarball"
161 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
163 config KERNEL_LINUX_CUSTOM_IS_TARBALL
165 prompt "This is a tarball"
167 If you say 'n' here, the path above is expected to point to a directory
168 containing readily prepared headers
170 If you say 'y' here, then the path above is expected to point to a
171 tarball of such a directory.
173 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
174 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
176 Now, passing a tarball around is easier than passing a directory, so
177 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
178 say 'y' here, and enter the path to this tarball below.
180 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS