summaryrefslogtreecommitdiff
path: root/config/kernel/linux.in
blob: e6e739b0be169dc870ef413f99e006dce3a0a683 (plain)
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
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
# Linux kernel options

# Linux kernel options

config KERNEL_linux
    select KERNEL_SUPPORTS_SHARED_LIBS
    help
      Build a toolchain targeting systems running Linux as a kernel.

choice
    bool
    prompt "Get kernel headers from:"

config KERNEL_LINUX_INSTALL
    bool
    prompt "kernel's 'headers_install'"
    help
      This will make use of the new headers_install rule in recent kernels.
      This is most probably what you want to use.

if KERNEL_LINUX_INSTALL

config KERNEL_LINUX_INSTALL_CHECK
    bool
    prompt "Check installed headers"
    default y
    help
      If you are in doubt that installed headers are buggy, say 'Y'
      here to have an extra check passed onto the headers.

choice
    bool
    prompt "Linux kernel version"
# Don't remove next line
# CT_INSERT_VERSION_BELOW

config KERNEL_V_2_6_32_3
    bool
    prompt "2.6.32.3"

config KERNEL_V_2_6_32_2
    bool
    prompt "2.6.32.2"

config KERNEL_V_2_6_32_1
    bool
    prompt "2.6.32.1"

config KERNEL_V_2_6_32
    bool
    prompt "2.6.32"

config KERNEL_V_2_6_31_11
    bool
    prompt "2.6.31.11"

config KERNEL_V_2_6_31_9
    bool
    prompt "2.6.31.9"

config KERNEL_V_2_6_31_8
    bool
    prompt "2.6.31.8"

config KERNEL_V_2_6_31_7
    bool
    prompt "2.6.31.7"

config KERNEL_V_2_6_31_6
    bool
    prompt "2.6.31.6"

config KERNEL_V_2_6_31_5
    bool
    prompt "2.6.31.5"

config KERNEL_V_2_6_31_4
    bool
    prompt "2.6.31.4"

config KERNEL_V_2_6_31_3
    bool
    prompt "2.6.31.3"

config KERNEL_V_2_6_31_2
    bool
    prompt "2.6.31.2"

config KERNEL_V_2_6_31_1
    bool
    prompt "2.6.31.1"

config KERNEL_V_2_6_31
    bool
    prompt "2.6.31"

config KERNEL_V_2_6_30_10
    bool
    prompt "2.6.30.10"

config KERNEL_V_2_6_30_9
    bool
    prompt "2.6.30.9"

config KERNEL_V_2_6_30_8
    bool
    prompt "2.6.30.8"

config KERNEL_V_2_6_30_7
    bool
    prompt "2.6.30.7"

config KERNEL_V_2_6_30_6
    bool
    prompt "2.6.30.6"

config KERNEL_V_2_6_30_5
    bool
    prompt "2.6.30.5"

config KERNEL_V_2_6_30_4
    bool
    prompt "2.6.30.4"

config KERNEL_V_2_6_30_3
    bool
    prompt "2.6.30.3"

config KERNEL_V_2_6_30_2
    bool
    prompt "2.6.30.2"

config KERNEL_V_2_6_30_1
    bool
    prompt "2.6.30.1"

config KERNEL_V_2_6_30
    bool
    prompt "2.6.30"

config KERNEL_V_2_6_29_6
    bool
    prompt "2.6.29.6 (OBSOLETE)"
    depends on OBSOLETE

config KERNEL_V_2_6_28_10
    bool
    prompt "2.6.28.10 (OBSOLETE)"
    depends on OBSOLETE

config KERNEL_V_2_6_27_43
    bool
    prompt "2.6.27.43 (long-term stable)"
    help
      The Linux 2.6.27 tree is the current "long-term stable" 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=2

endchoice

config KERNEL_VERSION
    string
# Don't remove next line
# CT_INSERT_VERSION_STRING_BELOW
    default "2.6.32.3" if KERNEL_V_2_6_32_3
    default "2.6.32.2" if KERNEL_V_2_6_32_2
    default "2.6.32.1" if KERNEL_V_2_6_32_1
    default "2.6.32" if KERNEL_V_2_6_32
    default "2.6.31.11" if KERNEL_V_2_6_31_11
    default "2.6.31.9" if KERNEL_V_2_6_31_9
    default "2.6.31.8" if KERNEL_V_2_6_31_8
    default "2.6.31.7" if KERNEL_V_2_6_31_7
    default "2.6.31.6" if KERNEL_V_2_6_31_6
    default "2.6.31.5" if KERNEL_V_2_6_31_5
    default "2.6.31.4" if KERNEL_V_2_6_31_4
    default "2.6.31.3" if KERNEL_V_2_6_31_3
    default "2.6.31.2" if KERNEL_V_2_6_31_2
    default "2.6.31.1" if KERNEL_V_2_6_31_1
    default "2.6.31" if KERNEL_V_2_6_31
    default "2.6.30.10" if KERNEL_V_2_6_30_10
    default "2.6.30.9" if KERNEL_V_2_6_30_9
    default "2.6.30.8" if KERNEL_V_2_6_30_8
    default "2.6.30.7" if KERNEL_V_2_6_30_7
    default "2.6.30.6" if KERNEL_V_2_6_30_6
    default "2.6.30.5" if KERNEL_V_2_6_30_5
    default "2.6.30.4" if KERNEL_V_2_6_30_4
    default "2.6.30.3" if KERNEL_V_2_6_30_3
    default "2.6.30.2" if KERNEL_V_2_6_30_2
    default "2.6.30.1" if KERNEL_V_2_6_30_1
    default "2.6.30" if KERNEL_V_2_6_30
    default "2.6.29.6" if KERNEL_V_2_6_29_6
    default "2.6.28.10" if KERNEL_V_2_6_28_10
    default "2.6.27.43" if KERNEL_V_2_6_27_43

choice
    bool
    prompt "Kernel verbosity:"
    default KERNEL_LINUX_VERBOSITY_0

config KERNEL_LINUX_VERBOSITY_0
    bool
    prompt "Simplified"
    help
      Print simplified command lines.

config KERNEL_LINUX_VERBOSITY_1
    bool
    prompt "Full commands"
    help
      Print full command lines.

config KERNEL_LINUX_VERBOSITY_2
    bool
    prompt "Exec reasons"
    help
      Print the reasons why a make target is rebuild.

endchoice

config KERNEL_LINUX_VERBOSE_LEVEL
    int
    default 0 if KERNEL_LINUX_VERBOSITY_0
    default 1 if KERNEL_LINUX_VERBOSITY_1
    default 2 if KERNEL_LINUX_VERBOSITY_2

endif

config KERNEL_LINUX_USE_CUSTOM_HEADERS
    bool
    prompt "Use custom headers"
    help
      If you have some kernel headers lying around, you can enter the path
      below.

if KERNEL_LINUX_USE_CUSTOM_HEADERS

config KERNEL_LINUX_CUSTOM_IS_TARBALL
    bool
    prompt "This is a tarball"
    default n
    help
      If you say 'n' here, the path below is expected to point to a directory
      containing readily prepared headers
      
      If you say 'y' here, then the path below 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.

config KERNEL_LINUX_CUSTOM_PATH
    string
    prompt "Path to custom headers directory/tarball"
    help
      See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.

endif # KERNEL_LINUX_USE_CUSTOM_DIR

endchoice