diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-12-18 15:09:46 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-01-16 15:59:06 +0000 |
| commit | 716306ad2bf313ff490dd131650c718218134be0 (patch) | |
| tree | 8e289f603cc69086e7b4188dc116756c61ccc38b /documentation/kernel-dev/kernel-dev-common.xml | |
| parent | 74d43d3a11113c8d8183d95e8b6215ee164784f6 (diff) | |
| download | poky-716306ad2bf313ff490dd131650c718218134be0.tar.gz | |
kernel-dev: Re-write of the "Changing the Configuration" section.
(From yocto-docs rev: 22f1f167c3c55b392ad8fd9e3d2e965183a2d884)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev/kernel-dev-common.xml')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 53 |
1 files changed, 51 insertions, 2 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index fe134cc916..fbe43213e2 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml | |||
| @@ -143,7 +143,7 @@ Project Board Support Package Developer's Guide. | |||
| 143 | SRC_URI += "file://0002-first-change.patch" | 143 | SRC_URI += "file://0002-first-change.patch" |
| 144 | SRC_URI += "file://0003-first-change.patch" | 144 | SRC_URI += "file://0003-first-change.patch" |
| 145 | </literallayout> | 145 | </literallayout> |
| 146 | Then next time you run BitBake to build the Linux kernel, BitBake | 146 | The next time you run BitBake to build the Linux kernel, BitBake |
| 147 | detects the change in the recipe and fetches and applies the patches | 147 | detects the change in the recipe and fetches and applies the patches |
| 148 | before building the kernel. | 148 | before building the kernel. |
| 149 | </para> | 149 | </para> |
| @@ -173,7 +173,55 @@ apply the patches before rebuilding the Linux kernel. | |||
| 173 | <title>Changing the Configuration</title> | 173 | <title>Changing the Configuration</title> |
| 174 | 174 | ||
| 175 | <para> | 175 | <para> |
| 176 | Making wholesale or incremental changes to the Linux kernel config can be made | 176 | You can make wholesale or incremental changes to the Linux |
| 177 | kernel <filename>.config</filename> file by including a | ||
| 178 | <filename>defconfig</filename> or by specifying | ||
| 179 | configuration fragments in the <filename>SRC_URI</filename>. | ||
| 180 | </para> | ||
| 181 | |||
| 182 | <para> | ||
| 183 | If you have a complete Linux kernel <filename>.config</filename> | ||
| 184 | file you want to use, copy it to the | ||
| 185 | <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-FILES'><filename>FILES</filename></ulink><filename>}</filename> | ||
| 186 | directory within your layer and name it "defconfig". | ||
| 187 | Then, add the following line to your linux-yocto | ||
| 188 | <filename>.bbappend</filename> file in your layer: | ||
| 189 | <literallayout class='monospaced'> | ||
| 190 | SRC_URI += "file://defconfig" | ||
| 191 | </literallayout> | ||
| 192 | </para> | ||
| 193 | |||
| 194 | <para> | ||
| 195 | Generally speaking, the preferred approach is to determine the | ||
| 196 | incremental change you want to make and add that as a fragment. | ||
| 197 | For example, if you wanted to add support for a basic serial | ||
| 198 | console, create a file named <filename>8250.cfg</filename> in the | ||
| 199 | <filename>${FILES}</filename> directory with the following | ||
| 200 | content (without indentation): | ||
| 201 | <literallayout class='monospaced'> | ||
| 202 | CONFIG_SERIAL_8250=y | ||
| 203 | CONFIG_SERIAL_8250_CONSOLE=y | ||
| 204 | CONFIG_SERIAL_8250_PCI=y | ||
| 205 | CONFIG_SERIAL_8250_NR_UARTS=4 | ||
| 206 | CONFIG_SERIAL_8250_RUNTIME_UARTS=4 | ||
| 207 | CONFIG_SERIAL_CORE=y | ||
| 208 | CONFIG_SERIAL_CORE_CONSOLE=y | ||
| 209 | </literallayout> | ||
| 210 | Next, include this configuration fragment in a | ||
| 211 | <filename>SRC_URI</filename> statement in your | ||
| 212 | <filename>.bbappend</filename> file: | ||
| 213 | <literallayout class='monospaced'> | ||
| 214 | SRC_URI += "file://8250.cfg" | ||
| 215 | </literallayout> | ||
| 216 | The next time you run BitBake to build the Linux kernel, BitBake | ||
| 217 | detects the change in the recipe and fetches and applies the | ||
| 218 | new configuration before building the kernel. | ||
| 219 | </para> | ||
| 220 | |||
| 221 | <para> | ||
| 222 | Original Text: | ||
| 223 | <literallayout class='monospaced'> | ||
| 224 | Making wholesale or incremental changes to the Linux kernel config can be made | ||
| 177 | by including a defconfig or configuration fragments in the SRC_URI. | 225 | by including a defconfig or configuration fragments in the SRC_URI. |
| 178 | 226 | ||
| 179 | If you have a complete Linux kernel .config file you want to use, copy it as | 227 | If you have a complete Linux kernel .config file you want to use, copy it as |
| @@ -201,6 +249,7 @@ Then include this configuration fragment in the SRC_URI: | |||
| 201 | 249 | ||
| 202 | At the next build, bitbake will detect the change in the recipe and fetch and | 250 | At the next build, bitbake will detect the change in the recipe and fetch and |
| 203 | apply the new configuration before rebuilding the Linux kernel. | 251 | apply the new configuration before rebuilding the Linux kernel. |
| 252 | </literallayout> | ||
| 204 | </para> | 253 | </para> |
| 205 | </section> | 254 | </section> |
| 206 | </section> | 255 | </section> |
