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