yann@448
|
1 |
# Linux kernel options
|
yann@448
|
2 |
|
yann@861
|
3 |
config KERNEL_linux
|
yann@1500
|
4 |
select KERNEL_SUPPORTS_SHARED_LIBS
|
yann@861
|
5 |
help
|
yann@861
|
6 |
Build a toolchain targeting systems running Linux as a kernel.
|
yann@861
|
7 |
|
yann@1345
|
8 |
choice
|
yann@1345
|
9 |
bool
|
yann@1345
|
10 |
prompt "Get kernel headers from:"
|
yann@1345
|
11 |
|
yann@1345
|
12 |
config KERNEL_LINUX_INSTALL
|
yann@1345
|
13 |
bool
|
yann@1345
|
14 |
prompt "kernel's 'headers_install'"
|
yann@1345
|
15 |
help
|
yann@1345
|
16 |
This will make use of the new headers_install rule in recent kernels.
|
yann@1345
|
17 |
This is most probably what you want to use.
|
yann@1345
|
18 |
|
yann@1345
|
19 |
if KERNEL_LINUX_INSTALL
|
yann@1345
|
20 |
|
yann@1345
|
21 |
choice
|
yann@1345
|
22 |
bool
|
yann@1345
|
23 |
prompt "Linux kernel version"
|
yann@1535
|
24 |
# Don't remove next line
|
yann@1535
|
25 |
# CT_INSERT_VERSION_BELOW
|
yann@1345
|
26 |
|
yann@2221
|
27 |
config KERNEL_V_2_6_36_2
|
yann@2221
|
28 |
bool
|
yann@2221
|
29 |
prompt "2.6.36.2"
|
yann@2221
|
30 |
|
yann@2200
|
31 |
config KERNEL_V_2_6_36_1
|
yann@2200
|
32 |
bool
|
yann@2200
|
33 |
prompt "2.6.36.1"
|
yann@2200
|
34 |
|
yann@2158
|
35 |
config KERNEL_V_2_6_36
|
yann@2158
|
36 |
bool
|
yann@2158
|
37 |
prompt "2.6.36"
|
yann@2158
|
38 |
|
yann@2221
|
39 |
config KERNEL_V_2_6_35_10
|
yann@2135
|
40 |
bool
|
yann@2221
|
41 |
prompt "2.6.35.10 (longterm)"
|
yann@2222
|
42 |
help
|
yann@2221
|
43 |
The Linux 2.6.35 tree is a "longterm" maintenance branch.
|
yann@2221
|
44 |
|
yann@2221
|
45 |
It is intended to fill the niche for users who are not using distribution
|
yann@2221
|
46 |
kernels but want to use a regression-free kernel for a longer time.
|
yann@2221
|
47 |
|
yann@2221
|
48 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
yann@2221
|
49 |
which makes 2.6.35 a very useful base for many embedded developers seeking
|
yann@2221
|
50 |
stable APIs or those who do not need the latest bleeding edge features.
|
yann@2221
|
51 |
|
yann@2221
|
52 |
... and no, this kernel has not undergone any specific QA testing.
|
yann@2221
|
53 |
|
yann@2221
|
54 |
See the original announcement by Andi Kleen in the following mailing
|
yann@2221
|
55 |
list entry:
|
yann@2221
|
56 |
http://marc.info/?l=linux-kernel&m=129136895415202&w=4
|
yann@2135
|
57 |
|
yann@2135
|
58 |
config KERNEL_V_2_6_34_7
|
lacombar@2062
|
59 |
bool
|
yann@2135
|
60 |
prompt "2.6.34.7"
|
lacombar@2062
|
61 |
|
lacombar@2062
|
62 |
config KERNEL_V_2_6_33_7
|
lacombar@2062
|
63 |
bool
|
lacombar@2062
|
64 |
prompt "2.6.33.7"
|
lacombar@2062
|
65 |
|
yann@2221
|
66 |
config KERNEL_V_2_6_32_27
|
yann@1790
|
67 |
bool
|
yann@2221
|
68 |
prompt "2.6.32.27 (longterm)"
|
yann@2136
|
69 |
help
|
yann@2221
|
70 |
The Linux 2.6.32 tree is a "longterm" maintenance branch.
|
yann@2221
|
71 |
|
yann@2136
|
72 |
It is intended to fill the niche for users who are not using distribution
|
yann@2136
|
73 |
kernels but want to use a regression-free kernel for a longer time.
|
yann@2136
|
74 |
|
yann@2136
|
75 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
yann@2136
|
76 |
which makes 2.6.32 a very useful base for many embedded developers seeking
|
yann@2136
|
77 |
stable APIs or those who do not need the latest bleeding edge features.
|
yann@2136
|
78 |
|
yann@2136
|
79 |
... and no, this kernel has not undergone any specific QA testing.
|
yann@2136
|
80 |
|
yann@2136
|
81 |
See the original announcement by Greg Kroah-Hartman in the following
|
yann@2136
|
82 |
mailing list entry:
|
yann@2221
|
83 |
http://marc.info/?l=linux-kernel&m=126384198403392&w=4
|
yann@1665
|
84 |
|
js@2011
|
85 |
config KERNEL_V_2_6_31_14
|
jocke@1702
|
86 |
bool
|
js@2011
|
87 |
prompt "2.6.31.14"
|
yann@1534
|
88 |
|
yann@2221
|
89 |
config KERNEL_V_2_6_27_57
|
yann@1534
|
90 |
bool
|
yann@2221
|
91 |
prompt "2.6.27.57 (longterm)"
|
jocke@1702
|
92 |
help
|
yann@2221
|
93 |
The Linux 2.6.27 tree is a "longterm" maintenance branch.
|
yann@2221
|
94 |
|
jocke@1702
|
95 |
It is intended to fill the niche for users who are not using distribution
|
jocke@1702
|
96 |
kernels but want to use a regression-free kernel for a longer time.
|
jocke@1702
|
97 |
|
jocke@1702
|
98 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
jocke@1702
|
99 |
which makes 2.6.27 a very useful base for many embedded developers seeking
|
jocke@1702
|
100 |
stable APIs or those who do not need the latest bleeding edge features.
|
jocke@1702
|
101 |
|
jocke@1702
|
102 |
... and no, this kernel has not undergone any specific QA testing.
|
jocke@1702
|
103 |
|
jocke@1702
|
104 |
See the original announcement by Adrian Bunk in the following mailing list
|
yann@2136
|
105 |
entry:
|
yann@2221
|
106 |
http://marc.info/?l=linux-kernel&m=122375909403298&w=4
|
yann@2221
|
107 |
|
yann@2221
|
108 |
It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
|
yann@2221
|
109 |
http://marc.info/?l=linux-kernel&m=129133701916793&w=4
|
yann@1534
|
110 |
|
yann@1990
|
111 |
config KERNEL_LINUX_CUSTOM
|
yann@1990
|
112 |
bool
|
yann@1990
|
113 |
prompt "custom tarball"
|
yann@1990
|
114 |
help
|
yann@1990
|
115 |
Use a local tarball of a complete kernel source tree.
|
yann@1990
|
116 |
|
yann@1990
|
117 |
config KERNEL_LINUX_CUSTOM_TARBALL
|
yann@1990
|
118 |
string
|
yann@1990
|
119 |
prompt "Path to custom tarball"
|
yann@1990
|
120 |
depends on KERNEL_LINUX_CUSTOM
|
yann@1990
|
121 |
help
|
yann@1990
|
122 |
Enter here the path to the tarball of your full kernel tree.
|
yann@1990
|
123 |
|
yann@1345
|
124 |
endchoice
|
yann@1345
|
125 |
|
yann@1345
|
126 |
config KERNEL_VERSION
|
yann@1345
|
127 |
string
|
yann@1535
|
128 |
# Don't remove next line
|
yann@1535
|
129 |
# CT_INSERT_VERSION_STRING_BELOW
|
yann@2221
|
130 |
default "2.6.36.2" if KERNEL_V_2_6_36_2
|
yann@2200
|
131 |
default "2.6.36.1" if KERNEL_V_2_6_36_1
|
yann@2158
|
132 |
default "2.6.36" if KERNEL_V_2_6_36
|
yann@2221
|
133 |
default "2.6.35.10" if KERNEL_V_2_6_35_10
|
yann@2135
|
134 |
default "2.6.34.7" if KERNEL_V_2_6_34_7
|
lacombar@2062
|
135 |
default "2.6.33.7" if KERNEL_V_2_6_33_7
|
yann@2221
|
136 |
default "2.6.32.27" if KERNEL_V_2_6_32_26
|
js@2011
|
137 |
default "2.6.31.14" if KERNEL_V_2_6_31_14
|
yann@2221
|
138 |
default "2.6.27.57" if KERNEL_V_2_6_27_57
|
yann@1345
|
139 |
|
yann@1345
|
140 |
choice
|
yann@1345
|
141 |
bool
|
yann@1345
|
142 |
prompt "Kernel verbosity:"
|
yann@1345
|
143 |
default KERNEL_LINUX_VERBOSITY_0
|
yann@1345
|
144 |
|
yann@1345
|
145 |
config KERNEL_LINUX_VERBOSITY_0
|
yann@1345
|
146 |
bool
|
yann@1345
|
147 |
prompt "Simplified"
|
yann@1345
|
148 |
help
|
yann@1345
|
149 |
Print simplified command lines.
|
yann@1345
|
150 |
|
yann@1345
|
151 |
config KERNEL_LINUX_VERBOSITY_1
|
yann@1345
|
152 |
bool
|
yann@1345
|
153 |
prompt "Full commands"
|
yann@1345
|
154 |
help
|
yann@1345
|
155 |
Print full command lines.
|
yann@1345
|
156 |
|
yann@1345
|
157 |
config KERNEL_LINUX_VERBOSITY_2
|
yann@1345
|
158 |
bool
|
yann@1345
|
159 |
prompt "Exec reasons"
|
yann@1345
|
160 |
help
|
yann@1345
|
161 |
Print the reasons why a make target is rebuild.
|
yann@1345
|
162 |
|
yann@1345
|
163 |
endchoice
|
yann@1345
|
164 |
|
yann@1345
|
165 |
config KERNEL_LINUX_VERBOSE_LEVEL
|
yann@1345
|
166 |
int
|
yann@1345
|
167 |
default 0 if KERNEL_LINUX_VERBOSITY_0
|
yann@1345
|
168 |
default 1 if KERNEL_LINUX_VERBOSITY_1
|
yann@1345
|
169 |
default 2 if KERNEL_LINUX_VERBOSITY_2
|
yann@1345
|
170 |
|
yann@1989
|
171 |
config KERNEL_LINUX_INSTALL_CHECK
|
yann@1989
|
172 |
bool
|
yann@1989
|
173 |
prompt "Check installed headers"
|
yann@1989
|
174 |
default y
|
yann@1989
|
175 |
help
|
yann@1989
|
176 |
If you are in doubt that installed headers are buggy, say 'Y'
|
yann@1989
|
177 |
here to have an extra check passed onto the headers.
|
yann@1989
|
178 |
|
yann@1989
|
179 |
endif # KERNEL_LINUX_INSTALL
|
yann@1345
|
180 |
|
yann@1345
|
181 |
config KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@1345
|
182 |
bool
|
yann@1990
|
183 |
prompt "pre-installed headers tree"
|
yann@1345
|
184 |
help
|
yann@1990
|
185 |
If you have some pre-installed kernel headers lying around, you can
|
yann@1990
|
186 |
enter the path to these headers, below, they will be copied from
|
yann@1990
|
187 |
there, and into the toolchain's sysroot.
|
yann@1990
|
188 |
|
yann@1990
|
189 |
Note:
|
yann@1990
|
190 |
This will *not* let you use a complete kernel tree!
|
yann@1990
|
191 |
If you want to use your own full kernel tree, then you want to
|
yann@1990
|
192 |
say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
|
yann@1345
|
193 |
|
yann@1345
|
194 |
if KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@1345
|
195 |
|
yann@1345
|
196 |
config KERNEL_LINUX_CUSTOM_IS_TARBALL
|
yann@1345
|
197 |
bool
|
yann@1345
|
198 |
prompt "This is a tarball"
|
yann@1345
|
199 |
default n
|
yann@1345
|
200 |
help
|
yann@1345
|
201 |
If you say 'n' here, the path below is expected to point to a directory
|
yann@1345
|
202 |
containing readily prepared headers
|
yann@1345
|
203 |
|
yann@1345
|
204 |
If you say 'y' here, then the path below is expected to point to a
|
yann@1345
|
205 |
tarball of such a directory.
|
yann@1345
|
206 |
|
yann@1345
|
207 |
Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
|
yann@1345
|
208 |
say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
|
yann@1345
|
209 |
|
yann@1345
|
210 |
Now, passing a tarball around is easier than passing a directory, so
|
yann@1345
|
211 |
if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
|
yann@1345
|
212 |
say 'y' here, and enter the path to this tarball below.
|
yann@1345
|
213 |
|
yann@1345
|
214 |
config KERNEL_LINUX_CUSTOM_PATH
|
yann@1345
|
215 |
string
|
yann@1345
|
216 |
prompt "Path to custom headers directory/tarball"
|
yann@1345
|
217 |
help
|
yann@1345
|
218 |
See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
|
yann@1345
|
219 |
|
yann@1989
|
220 |
endif # KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@1345
|
221 |
|
yann@1345
|
222 |
endchoice
|