yann@1345
|
1 |
# Linux kernel options
|
yann@1345
|
2 |
|
yann@448
|
3 |
# Linux kernel options
|
yann@448
|
4 |
|
yann@861
|
5 |
config KERNEL_linux
|
yann@1500
|
6 |
select KERNEL_SUPPORTS_SHARED_LIBS
|
yann@861
|
7 |
help
|
yann@861
|
8 |
Build a toolchain targeting systems running Linux as a kernel.
|
yann@861
|
9 |
|
yann@1345
|
10 |
choice
|
yann@1345
|
11 |
bool
|
yann@1345
|
12 |
prompt "Get kernel headers from:"
|
yann@1345
|
13 |
|
yann@1345
|
14 |
config KERNEL_LINUX_INSTALL
|
yann@1345
|
15 |
bool
|
yann@1345
|
16 |
prompt "kernel's 'headers_install'"
|
yann@1345
|
17 |
help
|
yann@1345
|
18 |
This will make use of the new headers_install rule in recent kernels.
|
yann@1345
|
19 |
This is most probably what you want to use.
|
yann@1345
|
20 |
|
yann@1345
|
21 |
if KERNEL_LINUX_INSTALL
|
yann@1345
|
22 |
|
yann@1345
|
23 |
config KERNEL_LINUX_INSTALL_CHECK
|
yann@1345
|
24 |
bool
|
yann@1345
|
25 |
prompt "Check installed headers"
|
yann@1345
|
26 |
default y
|
yann@1345
|
27 |
help
|
yann@1345
|
28 |
If you are in doubt that installed headers are buggy, say 'Y'
|
yann@1345
|
29 |
here to have an extra check passed onto the headers.
|
yann@1345
|
30 |
|
yann@1345
|
31 |
choice
|
yann@1345
|
32 |
bool
|
yann@1345
|
33 |
prompt "Linux kernel version"
|
yann@1535
|
34 |
# Don't remove next line
|
yann@1535
|
35 |
# CT_INSERT_VERSION_BELOW
|
yann@1345
|
36 |
|
yann@1790
|
37 |
config KERNEL_V_2_6_32_7
|
yann@1790
|
38 |
bool
|
yann@1790
|
39 |
prompt "2.6.32.7"
|
yann@1790
|
40 |
|
yann@1790
|
41 |
config KERNEL_V_2_6_32_6
|
yann@1790
|
42 |
bool
|
yann@1790
|
43 |
prompt "2.6.32.6"
|
yann@1790
|
44 |
|
yann@1790
|
45 |
config KERNEL_V_2_6_32_5
|
yann@1790
|
46 |
bool
|
yann@1790
|
47 |
prompt "2.6.32.5"
|
yann@1790
|
48 |
|
yann@1790
|
49 |
config KERNEL_V_2_6_32_4
|
yann@1790
|
50 |
bool
|
yann@1790
|
51 |
prompt "2.6.32.4"
|
yann@1790
|
52 |
|
jocke@1702
|
53 |
config KERNEL_V_2_6_32_3
|
jocke@1702
|
54 |
bool
|
jocke@1702
|
55 |
prompt "2.6.32.3"
|
jocke@1702
|
56 |
|
yann@1665
|
57 |
config KERNEL_V_2_6_32_2
|
yann@1665
|
58 |
bool
|
yann@1665
|
59 |
prompt "2.6.32.2"
|
yann@1665
|
60 |
|
yann@1665
|
61 |
config KERNEL_V_2_6_32_1
|
yann@1665
|
62 |
bool
|
yann@1665
|
63 |
prompt "2.6.32.1"
|
yann@1665
|
64 |
|
yann@1665
|
65 |
config KERNEL_V_2_6_32
|
yann@1665
|
66 |
bool
|
yann@1665
|
67 |
prompt "2.6.32"
|
yann@1665
|
68 |
|
yann@1790
|
69 |
config KERNEL_V_2_6_31_12
|
jocke@1702
|
70 |
bool
|
yann@1790
|
71 |
prompt "2.6.31.12"
|
yann@1534
|
72 |
|
yann@1665
|
73 |
config KERNEL_V_2_6_30_10
|
yann@1665
|
74 |
bool
|
yann@1665
|
75 |
prompt "2.6.30.10"
|
yann@1665
|
76 |
|
yann@1534
|
77 |
config KERNEL_V_2_6_29_6
|
yann@1534
|
78 |
bool
|
yann@1615
|
79 |
prompt "2.6.29.6 (OBSOLETE)"
|
yann@1615
|
80 |
depends on OBSOLETE
|
yann@1534
|
81 |
|
yann@1534
|
82 |
config KERNEL_V_2_6_28_10
|
yann@1534
|
83 |
bool
|
yann@1615
|
84 |
prompt "2.6.28.10 (OBSOLETE)"
|
yann@1615
|
85 |
depends on OBSOLETE
|
yann@1534
|
86 |
|
yann@1790
|
87 |
config KERNEL_V_2_6_27_45
|
yann@1534
|
88 |
bool
|
yann@1790
|
89 |
prompt "2.6.27.45 (long-term stable)"
|
jocke@1702
|
90 |
help
|
jocke@1702
|
91 |
The Linux 2.6.27 tree is the current "long-term stable" maintenance branch.
|
jocke@1702
|
92 |
It is intended to fill the niche for users who are not using distribution
|
jocke@1702
|
93 |
kernels but want to use a regression-free kernel for a longer time.
|
jocke@1702
|
94 |
|
jocke@1702
|
95 |
Critical bug fixes to later 2.6 releases are often ported to this branch
|
jocke@1702
|
96 |
which makes 2.6.27 a very useful base for many embedded developers seeking
|
jocke@1702
|
97 |
stable APIs or those who do not need the latest bleeding edge features.
|
jocke@1702
|
98 |
|
jocke@1702
|
99 |
... and no, this kernel has not undergone any specific QA testing.
|
jocke@1702
|
100 |
|
jocke@1702
|
101 |
See the original announcement by Adrian Bunk in the following mailing list
|
jocke@1702
|
102 |
entry: http://marc.info/?l=linux-kernel&m=122375909403298&w=2
|
yann@1534
|
103 |
|
yann@1345
|
104 |
endchoice
|
yann@1345
|
105 |
|
yann@1345
|
106 |
config KERNEL_VERSION
|
yann@1345
|
107 |
string
|
yann@1535
|
108 |
# Don't remove next line
|
yann@1535
|
109 |
# CT_INSERT_VERSION_STRING_BELOW
|
yann@1790
|
110 |
default "2.6.32.7" if KERNEL_V_2_6_32_7
|
yann@1790
|
111 |
default "2.6.32.6" if KERNEL_V_2_6_32_6
|
yann@1790
|
112 |
default "2.6.32.5" if KERNEL_V_2_6_32_5
|
yann@1790
|
113 |
default "2.6.32.4" if KERNEL_V_2_6_32_4
|
jocke@1702
|
114 |
default "2.6.32.3" if KERNEL_V_2_6_32_3
|
yann@1665
|
115 |
default "2.6.32.2" if KERNEL_V_2_6_32_2
|
yann@1665
|
116 |
default "2.6.32.1" if KERNEL_V_2_6_32_1
|
yann@1665
|
117 |
default "2.6.32" if KERNEL_V_2_6_32
|
yann@1790
|
118 |
default "2.6.31.12" if KERNEL_V_2_6_31_12
|
yann@1665
|
119 |
default "2.6.30.10" if KERNEL_V_2_6_30_10
|
yann@1534
|
120 |
default "2.6.29.6" if KERNEL_V_2_6_29_6
|
yann@1534
|
121 |
default "2.6.28.10" if KERNEL_V_2_6_28_10
|
yann@1790
|
122 |
default "2.6.27.45" if KERNEL_V_2_6_27_45
|
yann@1345
|
123 |
|
yann@1345
|
124 |
choice
|
yann@1345
|
125 |
bool
|
yann@1345
|
126 |
prompt "Kernel verbosity:"
|
yann@1345
|
127 |
default KERNEL_LINUX_VERBOSITY_0
|
yann@1345
|
128 |
|
yann@1345
|
129 |
config KERNEL_LINUX_VERBOSITY_0
|
yann@1345
|
130 |
bool
|
yann@1345
|
131 |
prompt "Simplified"
|
yann@1345
|
132 |
help
|
yann@1345
|
133 |
Print simplified command lines.
|
yann@1345
|
134 |
|
yann@1345
|
135 |
config KERNEL_LINUX_VERBOSITY_1
|
yann@1345
|
136 |
bool
|
yann@1345
|
137 |
prompt "Full commands"
|
yann@1345
|
138 |
help
|
yann@1345
|
139 |
Print full command lines.
|
yann@1345
|
140 |
|
yann@1345
|
141 |
config KERNEL_LINUX_VERBOSITY_2
|
yann@1345
|
142 |
bool
|
yann@1345
|
143 |
prompt "Exec reasons"
|
yann@1345
|
144 |
help
|
yann@1345
|
145 |
Print the reasons why a make target is rebuild.
|
yann@1345
|
146 |
|
yann@1345
|
147 |
endchoice
|
yann@1345
|
148 |
|
yann@1345
|
149 |
config KERNEL_LINUX_VERBOSE_LEVEL
|
yann@1345
|
150 |
int
|
yann@1345
|
151 |
default 0 if KERNEL_LINUX_VERBOSITY_0
|
yann@1345
|
152 |
default 1 if KERNEL_LINUX_VERBOSITY_1
|
yann@1345
|
153 |
default 2 if KERNEL_LINUX_VERBOSITY_2
|
yann@1345
|
154 |
|
yann@1345
|
155 |
endif
|
yann@1345
|
156 |
|
yann@1345
|
157 |
config KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@1345
|
158 |
bool
|
yann@1345
|
159 |
prompt "Use custom headers"
|
yann@1345
|
160 |
help
|
yann@1345
|
161 |
If you have some kernel headers lying around, you can enter the path
|
yann@1345
|
162 |
below.
|
yann@1345
|
163 |
|
yann@1345
|
164 |
if KERNEL_LINUX_USE_CUSTOM_HEADERS
|
yann@1345
|
165 |
|
yann@1345
|
166 |
config KERNEL_LINUX_CUSTOM_IS_TARBALL
|
yann@1345
|
167 |
bool
|
yann@1345
|
168 |
prompt "This is a tarball"
|
yann@1345
|
169 |
default n
|
yann@1345
|
170 |
help
|
yann@1345
|
171 |
If you say 'n' here, the path below is expected to point to a directory
|
yann@1345
|
172 |
containing readily prepared headers
|
yann@1345
|
173 |
|
yann@1345
|
174 |
If you say 'y' here, then the path below is expected to point to a
|
yann@1345
|
175 |
tarball of such a directory.
|
yann@1345
|
176 |
|
yann@1345
|
177 |
Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
|
yann@1345
|
178 |
say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
|
yann@1345
|
179 |
|
yann@1345
|
180 |
Now, passing a tarball around is easier than passing a directory, so
|
yann@1345
|
181 |
if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
|
yann@1345
|
182 |
say 'y' here, and enter the path to this tarball below.
|
yann@1345
|
183 |
|
yann@1345
|
184 |
config KERNEL_LINUX_CUSTOM_PATH
|
yann@1345
|
185 |
string
|
yann@1345
|
186 |
prompt "Path to custom headers directory/tarball"
|
yann@1345
|
187 |
help
|
yann@1345
|
188 |
See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
|
yann@1345
|
189 |
|
yann@1345
|
190 |
endif # KERNEL_LINUX_USE_CUSTOM_DIR
|
yann@1345
|
191 |
|
yann@1345
|
192 |
endchoice
|