mirror of
git://git.yoctoproject.org/poky.git
synced 2025-07-19 21:09:03 +02:00
7d3f57cfd2
If a variable has a glossary entry and some rST files write about those
variables, it's better to point to the glossary entry instead of just
highlighting it by surrounding it with two tick quotes.
This was automated by the following python script:
"""
import re
from pathlib import Path
with open('objects.inv.txt', 'r') as f:
objects = f.readlines()
with open('bitbake-objects.inv.txt', 'r') as f:
objects = objects + f.readlines()
re_term = re.compile(r'variables.html#term-([A-Z_0-9]*)')
terms = []
for obj in objects:
match = re_term.search(obj)
if match and match.group(1):
terms.append(match.group(1))
for rst in Path('.').rglob('*.rst'):
with open(rst, 'r') as f:
content = "".joing(f.readlines())
for term in terms:
content = re.sub(r'``({})``(?!.*\s*[~-]+)'.format(term), r':term:`\1`', content)
with open(rst, 'w') as f:
f.write(content)
"""
(From yocto-docs rev: ba49d9babfcb84bc5c26a68c8c3880a1d9c236d3)
Signed-off-by: Quentin Schulz <foss@0leil.net>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
77 lines
2.5 KiB
ReStructuredText
77 lines
2.5 KiB
ReStructuredText
.. SPDX-License-Identifier: CC-BY-SA-2.0-UK
|
|
|
|
**********************
|
|
Kernel Development FAQ
|
|
**********************
|
|
|
|
Common Questions and Solutions
|
|
==============================
|
|
|
|
Here are some solutions for common questions.
|
|
|
|
How do I use my own Linux kernel ``.config`` file?
|
|
--------------------------------------------------
|
|
|
|
Refer to the
|
|
":ref:`kernel-dev/common:changing the configuration`"
|
|
section for information.
|
|
|
|
How do I create configuration fragments?
|
|
----------------------------------------
|
|
|
|
A: Refer to the
|
|
":ref:`kernel-dev/common:creating configuration fragments`"
|
|
section for information.
|
|
|
|
How do I use my own Linux kernel sources?
|
|
-----------------------------------------
|
|
|
|
Refer to the
|
|
":ref:`kernel-dev/common:working with your own sources`"
|
|
section for information.
|
|
|
|
How do I install/not-install the kernel image on the rootfs?
|
|
------------------------------------------------------------
|
|
|
|
The kernel image (e.g. ``vmlinuz``) is provided by the
|
|
``kernel-image`` package. Image recipes depend on ``kernel-base``. To
|
|
specify whether or not the kernel image is installed in the generated
|
|
root filesystem, override ``RDEPENDS_${KERNEL_PACKAGE_NAME}-base`` to include or not
|
|
include "kernel-image". See the
|
|
":ref:`dev-manual/common-tasks:using .bbappend files in your layer`"
|
|
section in the
|
|
Yocto Project Development Tasks Manual for information on how to use an
|
|
append file to override metadata.
|
|
|
|
How do I install a specific kernel module?
|
|
------------------------------------------
|
|
|
|
Linux kernel modules are packaged individually. To ensure a
|
|
specific kernel module is included in an image, include it in the
|
|
appropriate machine :term:`RRECOMMENDS` variable.
|
|
These other variables are useful for installing specific modules:
|
|
- :term:`MACHINE_ESSENTIAL_EXTRA_RDEPENDS`
|
|
- :term:`MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS`
|
|
- :term:`MACHINE_EXTRA_RDEPENDS`
|
|
- :term:`MACHINE_EXTRA_RRECOMMENDS`
|
|
|
|
For example, set the following in the ``qemux86.conf`` file to include
|
|
the ``ab123`` kernel modules with images built for the ``qemux86``
|
|
machine::
|
|
|
|
MACHINE_EXTRA_RRECOMMENDS += "kernel-module-ab123"
|
|
|
|
For more information, see the
|
|
":ref:`kernel-dev/common:incorporating out-of-tree modules`" section.
|
|
|
|
How do I change the Linux kernel command line?
|
|
----------------------------------------------
|
|
|
|
The Linux kernel command line is
|
|
typically specified in the machine config using the :term:`APPEND` variable.
|
|
For example, you can add some helpful debug information doing the
|
|
following::
|
|
|
|
APPEND += "printk.time=y initcall_debug debug"
|
|
|