AcoSail/kernel_optimize_test
8
0
Fork 0
forked from luck/tmp_suning_uos_patched
Code Pull Requests Activity

docs: early-userspace: move to driver-api guide

Browse Source 
Those documents describe a kAPI. So, add to the driver-api
book.

Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
This commit is contained in:
Mauro Carvalho Chehab 2019-06-18 15:00:25 -03:00
parent 6cf2a73cb2
commit ec4b78a0e7
7 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
Documentation/early-userspace/buffer-format.rst → Documentation/driver-api/early-userspace/buffer-format.rst
View File

0
Documentation/early-userspace/early_userspace_support.rst → Documentation/driver-api/early-userspace/early_userspace_support.rst
View File

2
Documentation/early-userspace/index.rst → Documentation/driver-api/early-userspace/index.rst
View File

@ -1,5 +1,3 @@
:orphan:
=============== ===============
Early Userspace Early Userspace
=============== ===============

1
Documentation/driver-api/index.rst
View File

@ -16,6 +16,7 @@ available subsections can be seen below.
basics basics
infrastructure infrastructure
early-userspace/index
pm/index pm/index
clk clk
device-io device-io

2
Documentation/filesystems/nfs/nfsroot.txt
View File

@ -239,7 +239,7 @@ rdinit=<executable file>
A description of the process of mounting the root file system can be A description of the process of mounting the root file system can be
found in: found in:
Documentation/early-userspace/early_userspace_support.rst Documentation/driver-api/early-userspace/early_userspace_support.rst

4
Documentation/filesystems/ramfs-rootfs-initramfs.txt
View File

@ -105,7 +105,7 @@ All this differs from the old initrd in several ways:
- The old initrd file was a gzipped filesystem image (in some file format, - The old initrd file was a gzipped filesystem image (in some file format,
such as ext2, that needed a driver built into the kernel), while the new such as ext2, that needed a driver built into the kernel), while the new
initramfs archive is a gzipped cpio archive (like tar only simpler, initramfs archive is a gzipped cpio archive (like tar only simpler,
see cpio(1) and Documentation/early-userspace/buffer-format.rst). The see cpio(1) and Documentation/driver-api/early-userspace/buffer-format.rst). The
kernel's cpio extraction code is not only extremely small, it's also kernel's cpio extraction code is not only extremely small, it's also
__init text and data that can be discarded during the boot process. __init text and data that can be discarded during the boot process.
@ -159,7 +159,7 @@ One advantage of the configuration file is that root access is not required to
set permissions or create device nodes in the new archive. (Note that those set permissions or create device nodes in the new archive. (Note that those
two example "file" entries expect to find files named "init.sh" and "busybox" in two example "file" entries expect to find files named "init.sh" and "busybox" in
a directory called "initramfs", under the linux-2.6.* directory. See a directory called "initramfs", under the linux-2.6.* directory. See
Documentation/early-userspace/early_userspace_support.rst for more details.) Documentation/driver-api/early-userspace/early_userspace_support.rst for more details.)
The kernel does not depend on external cpio tools. If you specify a The kernel does not depend on external cpio tools. If you specify a
directory instead of a configuration file, the kernel's build infrastructure directory instead of a configuration file, the kernel's build infrastructure

2
usr/Kconfig
View File

@ -18,7 +18,7 @@ config INITRAMFS_SOURCE
When multiple directories and files are specified then the When multiple directories and files are specified then the
initramfs image will be the aggregate of all of them. initramfs image will be the aggregate of all of them.
See <file:Documentation/early-userspace/early_userspace_support.rst> for more details. See <file:Documentation/driver-api/early-userspace/early_userspace_support.rst> for more details.
If you are not sure, leave it blank. If you are not sure, leave it blank.