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_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_33_20
61 This is primarily for the use of those people who are stuck using the
62 .33-rt kernel. Anyone else who really wants to use the .33 kernel tree
63 is welcome to use this one as well.
65 config KERNEL_V_2_6_32_48
67 prompt "2.6.32.48 (longterm)"
69 The Linux 2.6.32 tree is a "longterm" maintenance branch.
71 It is intended to fill the niche for users who are not using distribution
72 kernels but want to use a regression-free kernel for a longer time.
74 Critical bug fixes to later 2.6 releases are often ported to this branch
75 which makes 2.6.32 a very useful base for many embedded developers seeking
76 stable APIs or those who do not need the latest bleeding edge features.
78 ... and no, this kernel has not undergone any specific QA testing.
80 See the original announcement by Greg Kroah-Hartman in the following
82 http://marc.info/?l=linux-kernel&m=126384198403392&w=4
84 config KERNEL_V_2_6_31_14
88 config KERNEL_V_2_6_27_57
90 prompt "2.6.27.57 (longterm)"
92 The Linux 2.6.27 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.27 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 Adrian Bunk in the following mailing list
105 http://marc.info/?l=linux-kernel&m=122375909403298&w=4
107 It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
108 http://marc.info/?l=linux-kernel&m=129133701916793&w=4
110 config KERNEL_LINUX_CUSTOM
112 prompt "custom tarball or directory"
114 Use a local tarball or local kernel directory of a complete kernel source tree.
116 config KERNEL_LINUX_CUSTOM_LOCATION
118 prompt "Path to custom source, tarball or directory"
119 depends on KERNEL_LINUX_CUSTOM
121 Enter here the path to the tarball of your full kernel tree or
126 config KERNEL_VERSION
128 # Don't remove next line
129 # CT_INSERT_VERSION_STRING_BELOW
130 default "3.1.1" if KERNEL_V_3_1_1
131 default "3.1" if KERNEL_V_3_1
132 default "3.0.9" if KERNEL_V_3_0_9
133 default "2.6.39.4" if KERNEL_V_2_6_39_4
134 default "2.6.38.8" if KERNEL_V_2_6_38_8
135 default "2.6.37.6" if KERNEL_V_2_6_37_6
136 default "2.6.36.4" if KERNEL_V_2_6_36_4
137 default "2.6.33.20" if KERNEL_V_2_6_33_20
138 default "2.6.32.48" if KERNEL_V_2_6_32_48
139 default "2.6.31.14" if KERNEL_V_2_6_31_14
140 default "2.6.27.57" if KERNEL_V_2_6_27_57
141 default "custom" if KERNEL_LINUX_CUSTOM
143 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
145 if KERNEL_LINUX_USE_CUSTOM_HEADERS
147 config KERNEL_LINUX_CUSTOM_PATH
149 prompt "Path to custom headers directory/tarball"
151 See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
153 config KERNEL_LINUX_CUSTOM_IS_TARBALL
155 prompt "This is a tarball"
157 If you say 'n' here, the path above is expected to point to a directory
158 containing readily prepared headers
160 If you say 'y' here, then the path above is expected to point to a
161 tarball of such a directory.
163 Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
164 say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
166 Now, passing a tarball around is easier than passing a directory, so
167 if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
168 say 'y' here, and enter the path to this tarball below.
170 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS