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