yann@448
|
1 |
# Linux kernel options
|
yann@448
|
2 |
|
yann@2444
|
3 |
## select KERNEL_SUPPORTS_SHARED_LIBS
|
yann@2444
|
4 |
##
|
yann@2444
|
5 |
## help Build a toolchain targeting systems running Linux as a kernel.
|
yann@2446
|
6 |
|
yann@2446
|
7 |
config KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@2446
|
8 |
bool
|
yann@2602
|
9 |
prompt "Use pre-installed headers tree (OBSOLETE)"
|
yann@2602
|
10 |
depends on OBSOLETE
|
yann@2446
|
11 |
help
|
yann@2446
|
12 |
If you have some pre-installed kernel headers lying around, you can
|
yann@2446
|
13 |
enter the path to these headers, below, they will be copied from
|
yann@2446
|
14 |
there, and into the toolchain's sysroot.
|
yann@2446
|
15 |
|
yann@2446
|
16 |
Note:
|
yann@2446
|
17 |
This will *not* let you use a complete kernel tree!
|
yann@2602
|
18 |
If you want to use your own full kernel tree, then you want to say 'N'
|
yann@2602
|
19 |
here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.
|
yann@2446
|
20 |
|
yann@2603
|
21 |
if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@2446
|
22 |
|
yann@2446
|
23 |
choice
|
yann@2446
|
24 |
bool
|
yann@2446
|
25 |
prompt "Linux kernel version"
|
yann@2446
|
26 |
# Don't remove next line
|
yann@2446
|
27 |
# CT_INSERT_VERSION_BELOW
|
yann@2446
|
28 |
|
yann@2649
|
29 |
config KERNEL_V_3_0_4
|
yann@2648
|
30 |
bool
|
yann@2649
|
31 |
prompt "3.0.4"
|
yann@2648
|
32 |
|
yann@2610
|
33 |
config KERNEL_V_3_0_3
|
yann@2610
|
34 |
bool
|
yann@2610
|
35 |
prompt "3.0.3"
|
yann@2610
|
36 |
|
yann@2610
|
37 |
config KERNEL_V_3_0_2
|
yann@2610
|
38 |
bool
|
yann@2610
|
39 |
prompt "3.0.2"
|
yann@2610
|
40 |
|
yann@2596
|
41 |
config KERNEL_V_3_0_1
|
yann@2596
|
42 |
bool
|
yann@2596
|
43 |
prompt "3.0.1"
|
yann@2596
|
44 |
|
yann@2568
|
45 |
config KERNEL_V_3_0
|
yann@2568
|
46 |
bool
|
yann@2568
|
47 |
prompt "3.0"
|
yann@2568
|
48 |
|
yann@2596
|
49 |
config KERNEL_V_2_6_39_4
|
yann@2566
|
50 |
bool
|
yann@2596
|
51 |
prompt "2.6.39.4"
|
yann@2473
|
52 |
|
bryanhundven@2513
|
53 |
config KERNEL_V_2_6_38_8
|
yann@2473
|
54 |
bool
|
bryanhundven@2513
|
55 |
prompt "2.6.38.8"
|
yann@2446
|
56 |
|
yann@2446
|
57 |
config KERNEL_V_2_6_37_6
|
yann@2446
|
58 |
bool
|
yann@2446
|
59 |
prompt "2.6.37.6"
|
yann@2446
|
60 |
|
yann@2446
|
61 |
config KERNEL_V_2_6_36_4
|
yann@2446
|
62 |
bool
|
yann@2446
|
63 |
prompt "2.6.36.4"
|
yann@2446
|
64 |
|
yann@2596
|
65 |
config KERNEL_V_2_6_35_14
|
yann@2446
|
66 |
bool
|
yann@2596
|
67 |
prompt "2.6.35.14 (longterm)"
|
yann@2446
|
68 |
help
|
yann@2446
|
69 |
The Linux 2.6.35 tree is a "longterm" maintenance branch.
|
yann@2446
|
70 |
|
yann@2446
|
71 |
It is intended to fill the niche for users who are not using distribution
|
yann@2446
|
72 |
kernels but want to use a regression-free kernel for a longer time.
|
yann@2446
|
73 |
|
yann@2446
|
74 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
yann@2446
|
75 |
which makes 2.6.35 a very useful base for many embedded developers seeking
|
yann@2446
|
76 |
stable APIs or those who do not need the latest bleeding edge features.
|
yann@2446
|
77 |
|
yann@2446
|
78 |
... and no, this kernel has not undergone any specific QA testing.
|
yann@2446
|
79 |
|
yann@2446
|
80 |
See the original announcement by Andi Kleen in the following mailing
|
yann@2446
|
81 |
list entry:
|
yann@2446
|
82 |
http://marc.info/?l=linux-kernel&m=129136895415202&w=4
|
yann@2446
|
83 |
|
bryanhundven@2517
|
84 |
config KERNEL_V_2_6_34_10
|
yann@2446
|
85 |
bool
|
bryanhundven@2517
|
86 |
prompt "2.6.34.10"
|
yann@2446
|
87 |
|
yann@2648
|
88 |
config KERNEL_V_2_6_33_19
|
yann@2446
|
89 |
bool
|
yann@2648
|
90 |
prompt "2.6.33.19"
|
yann@2596
|
91 |
help
|
yann@2596
|
92 |
This is primarily for the use of those people who are stuck using the
|
yann@2596
|
93 |
.33-rt kernel. Anyone else who really wants to use the .33 kernel tree
|
yann@2596
|
94 |
is welcome to use this one as well.
|
yann@2446
|
95 |
|
yann@2648
|
96 |
config KERNEL_V_2_6_32_46
|
yann@2446
|
97 |
bool
|
yann@2648
|
98 |
prompt "2.6.32.46 (longterm)"
|
yann@2446
|
99 |
help
|
yann@2446
|
100 |
The Linux 2.6.32 tree is a "longterm" maintenance branch.
|
yann@2446
|
101 |
|
yann@2446
|
102 |
It is intended to fill the niche for users who are not using distribution
|
yann@2446
|
103 |
kernels but want to use a regression-free kernel for a longer time.
|
yann@2446
|
104 |
|
yann@2446
|
105 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
yann@2446
|
106 |
which makes 2.6.32 a very useful base for many embedded developers seeking
|
yann@2446
|
107 |
stable APIs or those who do not need the latest bleeding edge features.
|
yann@2446
|
108 |
|
yann@2446
|
109 |
... and no, this kernel has not undergone any specific QA testing.
|
yann@2446
|
110 |
|
yann@2446
|
111 |
See the original announcement by Greg Kroah-Hartman in the following
|
yann@2446
|
112 |
mailing list entry:
|
yann@2446
|
113 |
http://marc.info/?l=linux-kernel&m=126384198403392&w=4
|
yann@2446
|
114 |
|
yann@2446
|
115 |
config KERNEL_V_2_6_31_14
|
yann@2446
|
116 |
bool
|
yann@2446
|
117 |
prompt "2.6.31.14"
|
yann@2446
|
118 |
|
yann@2473
|
119 |
config KERNEL_V_2_6_27_59
|
yann@2446
|
120 |
bool
|
yann@2473
|
121 |
prompt "2.6.27.59 (longterm)"
|
yann@2446
|
122 |
help
|
yann@2446
|
123 |
The Linux 2.6.27 tree is a "longterm" maintenance branch.
|
yann@2446
|
124 |
|
yann@2446
|
125 |
It is intended to fill the niche for users who are not using distribution
|
yann@2446
|
126 |
kernels but want to use a regression-free kernel for a longer time.
|
yann@2446
|
127 |
|
yann@2446
|
128 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
yann@2446
|
129 |
which makes 2.6.27 a very useful base for many embedded developers seeking
|
yann@2446
|
130 |
stable APIs or those who do not need the latest bleeding edge features.
|
yann@2446
|
131 |
|
yann@2446
|
132 |
... and no, this kernel has not undergone any specific QA testing.
|
yann@2446
|
133 |
|
yann@2446
|
134 |
See the original announcement by Adrian Bunk in the following mailing list
|
yann@2446
|
135 |
entry:
|
yann@2446
|
136 |
http://marc.info/?l=linux-kernel&m=122375909403298&w=4
|
yann@2446
|
137 |
|
yann@2446
|
138 |
It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
|
yann@2446
|
139 |
http://marc.info/?l=linux-kernel&m=129133701916793&w=4
|
yann@2446
|
140 |
|
yann@2446
|
141 |
config KERNEL_LINUX_CUSTOM
|
yann@2446
|
142 |
bool
|
sinseman44@2680
|
143 |
prompt "custom tarball or directory"
|
yann@2446
|
144 |
help
|
sinseman44@2680
|
145 |
Use a local tarball or local kernel directory of a complete kernel source tree.
|
yann@2446
|
146 |
|
sinseman44@2680
|
147 |
config KERNEL_LINUX_CUSTOM_LOCATION
|
yann@2446
|
148 |
string
|
sinseman44@2680
|
149 |
prompt "Path to custom source, tarball or directory"
|
yann@2446
|
150 |
depends on KERNEL_LINUX_CUSTOM
|
yann@2446
|
151 |
help
|
sinseman44@2680
|
152 |
Enter here the path to the tarball of your full kernel tree or
|
sinseman44@2680
|
153 |
kernel directory
|
yann@2446
|
154 |
|
yann@2446
|
155 |
endchoice
|
yann@2446
|
156 |
|
yann@2446
|
157 |
config KERNEL_VERSION
|
yann@2446
|
158 |
string
|
yann@2446
|
159 |
# Don't remove next line
|
yann@2446
|
160 |
# CT_INSERT_VERSION_STRING_BELOW
|
yann@2652
|
161 |
default "3.0.4" if KERNEL_V_3_0_4
|
yann@2610
|
162 |
default "3.0.3" if KERNEL_V_3_0_3
|
yann@2610
|
163 |
default "3.0.2" if KERNEL_V_3_0_2
|
yann@2596
|
164 |
default "3.0.1" if KERNEL_V_3_0_1
|
yann@2568
|
165 |
default "3.0" if KERNEL_V_3_0
|
yann@2596
|
166 |
default "2.6.39.4" if KERNEL_V_2_6_39_4
|
bryanhundven@2513
|
167 |
default "2.6.38.8" if KERNEL_V_2_6_38_8
|
yann@2446
|
168 |
default "2.6.37.6" if KERNEL_V_2_6_37_6
|
yann@2446
|
169 |
default "2.6.36.4" if KERNEL_V_2_6_36_4
|
yann@2596
|
170 |
default "2.6.35.14" if KERNEL_V_2_6_35_14
|
bryanhundven@2517
|
171 |
default "2.6.34.10" if KERNEL_V_2_6_34_10
|
yann@2648
|
172 |
default "2.6.33.19" if KERNEL_V_2_6_33_19
|
yann@2648
|
173 |
default "2.6.32.46" if KERNEL_V_2_6_32_46
|
yann@2446
|
174 |
default "2.6.31.14" if KERNEL_V_2_6_31_14
|
yann@2473
|
175 |
default "2.6.27.59" if KERNEL_V_2_6_27_59
|
yann@2603
|
176 |
default "custom" if KERNEL_LINUX_CUSTOM
|
yann@2446
|
177 |
|
yann@2603
|
178 |
endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@2446
|
179 |
|
yann@2446
|
180 |
if KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@2446
|
181 |
|
yann@2446
|
182 |
config KERNEL_LINUX_CUSTOM_PATH
|
yann@2446
|
183 |
string
|
yann@2446
|
184 |
prompt "Path to custom headers directory/tarball"
|
yann@2446
|
185 |
help
|
yann@2446
|
186 |
See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
|
yann@2446
|
187 |
|
yann@2446
|
188 |
config KERNEL_LINUX_CUSTOM_IS_TARBALL
|
yann@2446
|
189 |
bool
|
yann@2446
|
190 |
prompt "This is a tarball"
|
yann@2446
|
191 |
help
|
yann@2446
|
192 |
If you say 'n' here, the path above is expected to point to a directory
|
yann@2446
|
193 |
containing readily prepared headers
|
yann@2446
|
194 |
|
yann@2446
|
195 |
If you say 'y' here, then the path above is expected to point to a
|
yann@2446
|
196 |
tarball of such a directory.
|
yann@2446
|
197 |
|
yann@2446
|
198 |
Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
|
yann@2446
|
199 |
say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
|
yann@2446
|
200 |
|
yann@2446
|
201 |
Now, passing a tarball around is easier than passing a directory, so
|
yann@2446
|
202 |
if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
|
yann@2446
|
203 |
say 'y' here, and enter the path to this tarball below.
|
yann@2446
|
204 |
|
yann@2446
|
205 |
endif # KERNEL_LINUX_USE_CUSTOM_HEADERS
|