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 config KERNEL_LINUX_INSTALL
23 default y if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
25 if KERNEL_LINUX_INSTALL
29 prompt "Linux kernel version"
30 # Don't remove next line
31 # CT_INSERT_VERSION_BELOW
41 config KERNEL_V_2_6_39_4
45 config KERNEL_V_2_6_38_8
49 config KERNEL_V_2_6_37_6
53 config KERNEL_V_2_6_36_4
57 config KERNEL_V_2_6_35_14
59 prompt "2.6.35.14 (longterm)"
61 The Linux 2.6.35 tree is a "longterm" maintenance branch.
63 It is intended to fill the niche for users who are not using distribution
64 kernels but want to use a regression-free kernel for a longer time.
66 Critical bug fixes to later 2.6 releases are often ported to this branch
67 which makes 2.6.35 a very useful base for many embedded developers seeking
68 stable APIs or those who do not need the latest bleeding edge features.
70 ... and no, this kernel has not undergone any specific QA testing.
72 See the original announcement by Andi Kleen in the following mailing
74 http://marc.info/?l=linux-kernel&m=129136895415202&w=4
76 config KERNEL_V_2_6_34_10
80 config KERNEL_V_2_6_33_17
84 This is primarily for the use of those people who are stuck using the
85 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
86 is welcome to use this one as well.
88 config KERNEL_V_2_6_32_44
90 prompt "2.6.32.44 (longterm)"
92 The Linux 2.6.32 tree is a "longterm" maintenance branch.
94 It is intended to fill the niche for users who are not using distribution
95 kernels but want to use a regression-free kernel for a longer time.
97 Critical bug fixes to later 2.6 releases are often ported to this branch
98 which makes 2.6.32 a very useful base for many embedded developers seeking
99 stable APIs or those who do not need the latest bleeding edge features.
101 ... and no, this kernel has not undergone any specific QA testing.
103 See the original announcement by Greg Kroah-Hartman in the following
105 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
107 config KERNEL_V_2_6_31_14
111 config KERNEL_V_2_6_27_59
113 prompt "2.6.27.59 (longterm)"
115 The Linux 2.6.27 tree is a "longterm" maintenance branch.
117 It is intended to fill the niche for users who are not using distribution
118 kernels but want to use a regression-free kernel for a longer time.
120 Critical bug fixes to later 2.6 releases are often ported to this branch
121 which makes 2.6.27 a very useful base for many embedded developers seeking
122 stable APIs or those who do not need the latest bleeding edge features.
124 ... and no, this kernel has not undergone any specific QA testing.
126 See the original announcement by Adrian Bunk in the following mailing list
128 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
130 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
131 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
133 config KERNEL_LINUX_CUSTOM
135 prompt "custom tarball"
137 Use a local tarball of a complete kernel source tree.
139 config KERNEL_LINUX_CUSTOM_TARBALL
141 prompt "Path to custom tarball"
142 depends on KERNEL_LINUX_CUSTOM
144 Enter here the path to the tarball of your full kernel tree.
148 config KERNEL_VERSION
150 # Don't remove next line
151 # CT_INSERT_VERSION_STRING_BELOW
152 default "3.0.1" if KERNEL_V_3_0_1
153 default "3.0" if KERNEL_V_3_0
154 default "2.6.39.4" if KERNEL_V_2_6_39_4
155 default "2.6.38.8" if KERNEL_V_2_6_38_8
156 default "2.6.37.6" if KERNEL_V_2_6_37_6
157 default "2.6.36.4" if KERNEL_V_2_6_36_4
158 default "2.6.35.14" if KERNEL_V_2_6_35_14
159 default "2.6.34.10" if KERNEL_V_2_6_34_10
160 default "2.6.33.17" if KERNEL_V_2_6_33_17
161 default "2.6.32.44" if KERNEL_V_2_6_32_44
162 default "2.6.31.14" if KERNEL_V_2_6_31_14
163 default "2.6.27.59" if KERNEL_V_2_6_27_59
165 endif # KERNEL_LINUX_INSTALL
167 if KERNEL_LINUX_USE_CUSTOM_HEADERS
169 config KERNEL_LINUX_CUSTOM_PATH
171 prompt "Path to custom headers directory/tarball"
173 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
175 config KERNEL_LINUX_CUSTOM_IS_TARBALL
177 prompt "This is a tarball"
179 If you say 'n' here, the path above is expected to point to a directory
180 containing readily prepared headers
182 If you say 'y' here, then the path above is expected to point to a
183 tarball of such a directory.
185 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
186 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
188 Now, passing a tarball around is easier than passing a directory, so
189 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
190 say 'y' here, and enter the path to this tarball below.
192 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS