1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
|
# Linux kernel options
## select KERNEL_SUPPORTS_SHARED_LIBS
##
## help Build a toolchain targeting systems running Linux as a kernel.
config KERNEL_LINUX_USE_CUSTOM_HEADERS
bool
prompt "Use pre-installed headers tree (OBSOLETE)"
depends on OBSOLETE
help
If you have some pre-installed kernel headers lying around, you can
enter the path to these headers, below, they will be copied from
there, and into the toolchain's sysroot.
Note:
This will *not* let you use a complete kernel tree!
If you want to use your own full kernel tree, then you want to say 'N'
here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
choice
bool
prompt "Linux kernel version"
# Don't remove next line
# CT_INSERT_VERSION_BELOW
config KERNEL_V_3_19
bool
prompt "3.19.1"
config KERNEL_V_3_18
bool
prompt "3.18.9"
config KERNEL_V_3_17
bool
prompt "3.17.8"
config KERNEL_V_3_16
bool
prompt "3.16.7"
config KERNEL_V_3_15
bool
prompt "3.15.10"
config KERNEL_V_3_14
bool
prompt "3.14.35 (longterm)"
config KERNEL_V_3_13
bool
prompt "3.13.11"
config KERNEL_V_3_12
bool
prompt "3.12.38 (longterm)"
config KERNEL_V_3_11
bool
prompt "3.11.10"
config KERNEL_V_3_10
bool
prompt "3.10.71 (longterm)"
config KERNEL_V_3_9
bool
prompt "3.9.11"
config KERNEL_V_3_8
bool
prompt "3.8.13"
config KERNEL_V_3_7
bool
prompt "3.7.10"
config KERNEL_V_3_6
bool
prompt "3.6.11"
config KERNEL_V_3_5
bool
prompt "3.5.7"
config KERNEL_V_3_4
bool
prompt "3.4.106 (longterm)"
config KERNEL_V_3_3
bool
prompt "3.3.8"
config KERNEL_V_3_2
bool
prompt "3.2.68 (longterm)"
config KERNEL_V_3_1
bool
prompt "3.1.10"
config KERNEL_V_3_0
bool
prompt "3.0.101"
config KERNEL_V_2_6_39
bool
prompt "2.6.39.4"
config KERNEL_V_2_6_38
bool
prompt "2.6.38.8"
config KERNEL_V_2_6_37
bool
prompt "2.6.37.6"
config KERNEL_V_2_6_36
bool
prompt "2.6.36.4"
config KERNEL_V_2_6_33
bool
prompt "2.6.33.20"
help
This is primarily for the use of those people who are stuck using the
.33-rt kernel. Anyone else who really wants to use the .33 kernel tree
is welcome to use this one as well.
config KERNEL_V_2_6_32
bool
prompt "2.6.32.65 (longterm)"
help
The Linux 2.6.32 tree is a "longterm" maintenance branch.
It is intended to fill the niche for users who are not using distribution
kernels but want to use a regression-free kernel for a longer time.
Critical bug fixes to later 2.6 releases are often ported to this branch
which makes 2.6.32 a very useful base for many embedded developers seeking
stable APIs or those who do not need the latest bleeding edge features.
... and no, this kernel has not undergone any specific QA testing.
See the original announcement by Greg Kroah-Hartman in the following
mailing list entry:
http://marc.info/?l=linux-kernel&m=126384198403392&w=4
config KERNEL_V_2_6_31
bool
prompt "2.6.31.14"
config KERNEL_V_2_6_27
bool
prompt "2.6.27.62 (longterm)"
help
The Linux 2.6.27 tree is a "longterm" maintenance branch.
It is intended to fill the niche for users who are not using distribution
kernels but want to use a regression-free kernel for a longer time.
Critical bug fixes to later 2.6 releases are often ported to this branch
which makes 2.6.27 a very useful base for many embedded developers seeking
stable APIs or those who do not need the latest bleeding edge features.
... and no, this kernel has not undergone any specific QA testing.
See the original announcement by Adrian Bunk in the following mailing list
entry:
http://marc.info/?l=linux-kernel&m=122375909403298&w=4
It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
http://marc.info/?l=linux-kernel&m=129133701916793&w=4
config KERNEL_LINUX_CUSTOM
bool
prompt "custom tarball or directory"
help
Use a local tarball or local kernel directory of a complete kernel source tree.
config KERNEL_LINUX_CUSTOM_LOCATION
string
prompt "Path to custom source, tarball or directory"
depends on KERNEL_LINUX_CUSTOM
help
Enter here the path to the tarball of your full kernel tree or
kernel directory
endchoice
config KERNEL_VERSION
string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
default "3.19.1" if KERNEL_V_3_19
default "3.18.9" if KERNEL_V_3_18
default "3.17.8" if KERNEL_V_3_17
default "3.16.7" if KERNEL_V_3_16
default "3.15.10" if KERNEL_V_3_15
default "3.14.35" if KERNEL_V_3_14
default "3.13.11" if KERNEL_V_3_13
default "3.12.38" if KERNEL_V_3_12
default "3.11.10" if KERNEL_V_3_11
default "3.10.71" if KERNEL_V_3_10
default "3.9.11" if KERNEL_V_3_9
default "3.8.13" if KERNEL_V_3_8
default "3.7.10" if KERNEL_V_3_7
default "3.6.11" if KERNEL_V_3_6
default "3.5.7" if KERNEL_V_3_5
default "3.4.106" if KERNEL_V_3_4
default "3.3.8" if KERNEL_V_3_3
default "3.2.68" if KERNEL_V_3_2
default "3.1.10" if KERNEL_V_3_1
default "3.0.101" if KERNEL_V_3_0
default "2.6.39.4" if KERNEL_V_2_6_39
default "2.6.38.8" if KERNEL_V_2_6_38
default "2.6.37.6" if KERNEL_V_2_6_37
default "2.6.36.4" if KERNEL_V_2_6_36
default "2.6.33.20" if KERNEL_V_2_6_33
default "2.6.32.65" if KERNEL_V_2_6_32
default "2.6.31.14" if KERNEL_V_2_6_31
default "2.6.27.62" if KERNEL_V_2_6_27
default "custom" if KERNEL_LINUX_CUSTOM
endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
if KERNEL_LINUX_USE_CUSTOM_HEADERS
config KERNEL_LINUX_CUSTOM_PATH
string
prompt "Path to custom headers directory/tarball"
help
See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
config KERNEL_LINUX_CUSTOM_IS_TARBALL
bool
prompt "This is a tarball"
help
If you say 'n' here, the path above is expected to point to a directory
containing readily prepared headers
If you say 'y' here, then the path above is expected to point to a
tarball of such a directory.
Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
Now, passing a tarball around is easier than passing a directory, so
if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
say 'y' here, and enter the path to this tarball below.
endif # KERNEL_LINUX_USE_CUSTOM_HEADERS
|