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
41 config KERNEL_V_3_2_24
45 config KERNEL_V_3_1_10
49 config KERNEL_V_3_0_38
53 config KERNEL_V_2_6_39_4
57 config KERNEL_V_2_6_38_8
61 config KERNEL_V_2_6_37_6
65 config KERNEL_V_2_6_36_4
69 config KERNEL_V_2_6_33_20
73 This is primarily for the use of those people who are stuck using the
74 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
75 is welcome to use this one as well.
77 config KERNEL_V_2_6_32_59
79 prompt "2.6.32.59 (longterm)"
81 The Linux 2.6.32 tree is a "longterm" maintenance branch.
83 It is intended to fill the niche for users who are not using distribution
84 kernels but want to use a regression-free kernel for a longer time.
86 Critical bug fixes to later 2.6 releases are often ported to this branch
87 which makes 2.6.32 a very useful base for many embedded developers seeking
88 stable APIs or those who do not need the latest bleeding edge features.
90 ... and no, this kernel has not undergone any specific QA testing.
92 See the original announcement by Greg Kroah-Hartman in the following
94 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
96 config KERNEL_V_2_6_31_14
100 config KERNEL_V_2_6_27_62
102 prompt "2.6.27.62 (longterm)"
104 The Linux 2.6.27 tree is a "longterm" maintenance branch.
106 It is intended to fill the niche for users who are not using distribution
107 kernels but want to use a regression-free kernel for a longer time.
109 Critical bug fixes to later 2.6 releases are often ported to this branch
110 which makes 2.6.27 a very useful base for many embedded developers seeking
111 stable APIs or those who do not need the latest bleeding edge features.
113 ... and no, this kernel has not undergone any specific QA testing.
115 See the original announcement by Adrian Bunk in the following mailing list
117 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
119 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
120 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
122 config KERNEL_LINUX_CUSTOM
124 prompt "custom tarball or directory"
126 Use a local tarball or local kernel directory of a complete kernel source tree.
128 config KERNEL_LINUX_CUSTOM_LOCATION
130 prompt "Path to custom source, tarball or directory"
131 depends on KERNEL_LINUX_CUSTOM
133 Enter here the path to the tarball of your full kernel tree or
138 config KERNEL_VERSION
140 # Don't remove next line
141 # CT_INSERT_VERSION_STRING_BELOW
142 default "3.5" if KERNEL_V_3_5
143 default "3.4.7" if KERNEL_V_3_4_7
144 default "3.3.8" if KERNEL_V_3_3_8
145 default "3.2.24" if KERNEL_V_3_2_24
146 default "3.1.10" if KERNEL_V_3_1_10
147 default "3.0.38" if KERNEL_V_3_0_38
148 default "2.6.39.4" if KERNEL_V_2_6_39_4
149 default "2.6.38.8" if KERNEL_V_2_6_38_8
150 default "2.6.37.6" if KERNEL_V_2_6_37_6
151 default "2.6.36.4" if KERNEL_V_2_6_36_4
152 default "2.6.33.20" if KERNEL_V_2_6_33_20
153 default "2.6.32.59" if KERNEL_V_2_6_32_59
154 default "2.6.31.14" if KERNEL_V_2_6_31_14
155 default "2.6.27.62" if KERNEL_V_2_6_27_62
156 default "custom" if KERNEL_LINUX_CUSTOM
158 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
160 if KERNEL_LINUX_USE_CUSTOM_HEADERS
162 config KERNEL_LINUX_CUSTOM_PATH
164 prompt "Path to custom headers directory/tarball"
166 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
168 config KERNEL_LINUX_CUSTOM_IS_TARBALL
170 prompt "This is a tarball"
172 If you say 'n' here, the path above is expected to point to a directory
173 containing readily prepared headers
175 If you say 'y' here, then the path above is expected to point to a
176 tarball of such a directory.
178 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
179 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
181 Now, passing a tarball around is easier than passing a directory, so
182 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
183 say 'y' here, and enter the path to this tarball below.
185 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS