blob: 9adeb7a9db082de7d5645ffdf06ebc4f28424c2c (
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
|
// -*- mode:doc; -*-
// vim: set syntax=asciidoc:
[[kernel-custom]]
Customizing the Linux kernel configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Linux kernel configuration can be customized using +make menuconfig+.
OpenADK uses a combination of Linux miniconfig feature and user defined
features to generate a valid Linux configuration for your target.
Some features and drivers are not selectable via +make menuconfig+, either
because your choosen target system does not have support for it or the
option is not implemented, yet. OpenADK uses some kind of abstraction
layer between the real full featured and complicated Linux kernel configuration
and you. It is not perfect and does include a lot of manual work in
+target/linux/config+, but it works in a acceptable way.
If you just want to view the Linux configuration, which is actually
used for your target, you can execute following command:
---------------
$ make kernelconfig
---------------
Any changes here will get lost and will not be used to generate a kernel for
your target. If you want to change the existing kernel configuration you need
to follow these steps.
The basic kernel configuration used for your choosen target is concatenated from
following two files:
+target/linux/kernel.config+ and +target/<arch>/kernel/<system>+.
So if you would like to change any basic stuff, just edit the files and recreate your
firmware via:
---------------
$ make
---------------
OpenADK automatically recognizes any change and will rebuild the kernel.
The base kernel configuration for your target generated by OpenADK is normally just enough to
bootup the system with support for your board, serial console, network card and boot medium.
(like a hard disk, sd card or flash partition)
If you need to enable some new optional drivers or features, which are not available in
+make menuconfig+, you need to dig in +target/linux/config+. There is the abstraction layer
for the real kernel configuration.
|
