Documentation/sphinx: add basic working Sphinx configuration and build
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be run on the
various 'make *docs' targets.
All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
that and the Documentation/DocBook/Makefile are now expected to handle
all the documentation targets, explicitly ignoring them if they're not
relevant for that particular toolchain. The changes to the existing
DocBook Makefile are kept minimal.
There is graceful handling of missing Sphinx and rst2pdf (which is
needed for pdf output) by checking for the tool and python module,
respectively, with informative messages to the user.
If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
otherwise gracefully fall back to the Sphinx default theme, with an
informative message to the user, and slightly less pretty HTML output.
Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
epubdocs and xmldocs targets. The output documents are written into per
output type subdirectories under Documentation/output.
Finally, you can pass options to sphinx-build using the SPHINXBUILD make
variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
output from Sphinx.
This is based on the original work by Jonathan Corbet, but he probably
wouldn't recognize this as his own anymore.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
2016-05-19 12:14:05 +00:00
|
|
|
.. The Linux Kernel documentation master file, created by
|
|
|
|
|
sphinx-quickstart on Fri Feb 12 13:51:46 2016.
|
|
|
|
|
You can adapt this file completely to your liking, but it should at least
|
|
|
|
|
contain the root `toctree` directive.
|
|
|
|
|
|
2017-06-06 20:50:04 +00:00
|
|
|
The Linux Kernel documentation
|
|
|
|
|
==============================
|
Documentation/sphinx: add basic working Sphinx configuration and build
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be run on the
various 'make *docs' targets.
All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
that and the Documentation/DocBook/Makefile are now expected to handle
all the documentation targets, explicitly ignoring them if they're not
relevant for that particular toolchain. The changes to the existing
DocBook Makefile are kept minimal.
There is graceful handling of missing Sphinx and rst2pdf (which is
needed for pdf output) by checking for the tool and python module,
respectively, with informative messages to the user.
If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
otherwise gracefully fall back to the Sphinx default theme, with an
informative message to the user, and slightly less pretty HTML output.
Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
epubdocs and xmldocs targets. The output documents are written into per
output type subdirectories under Documentation/output.
Finally, you can pass options to sphinx-build using the SPHINXBUILD make
variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
output from Sphinx.
This is based on the original work by Jonathan Corbet, but he probably
wouldn't recognize this as his own anymore.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
2016-05-19 12:14:05 +00:00
|
|
|
|
2016-10-26 21:43:00 +00:00
|
|
|
This is the top level of the kernel's documentation tree. Kernel
|
|
|
|
|
documentation, like the kernel itself, is very much a work in progress;
|
|
|
|
|
that is especially true as we work to integrate our many scattered
|
|
|
|
|
documents into a coherent whole. Please note that improvements to the
|
|
|
|
|
documentation are welcome; join the linux-doc list at vger.kernel.org if
|
|
|
|
|
you want to help out.
|
|
|
|
|
|
2017-12-28 22:17:17 +00:00
|
|
|
Licensing documentation
|
|
|
|
|
-----------------------
|
|
|
|
|
|
|
|
|
|
The following describes the license of the Linux kernel source code
|
|
|
|
|
(GPLv2), how to properly mark the license of individual files in the source
|
|
|
|
|
tree, as well as links to the full license text.
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
|
|
|
|
process/license-rules.rst
|
|
|
|
|
|
2016-10-26 21:43:00 +00:00
|
|
|
User-oriented documentation
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
The following manuals are written for *users* of the kernel — those who are
|
|
|
|
|
trying to get it to work optimally on a given system.
|
Documentation/sphinx: add basic working Sphinx configuration and build
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be run on the
various 'make *docs' targets.
All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
that and the Documentation/DocBook/Makefile are now expected to handle
all the documentation targets, explicitly ignoring them if they're not
relevant for that particular toolchain. The changes to the existing
DocBook Makefile are kept minimal.
There is graceful handling of missing Sphinx and rst2pdf (which is
needed for pdf output) by checking for the tool and python module,
respectively, with informative messages to the user.
If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
otherwise gracefully fall back to the Sphinx default theme, with an
informative message to the user, and slightly less pretty HTML output.
Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
epubdocs and xmldocs targets. The output documents are written into per
output type subdirectories under Documentation/output.
Finally, you can pass options to sphinx-build using the SPHINXBUILD make
variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
output from Sphinx.
This is based on the original work by Jonathan Corbet, but he probably
wouldn't recognize this as his own anymore.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
2016-05-19 12:14:05 +00:00
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
2016-09-21 12:51:11 +00:00
|
|
|
admin-guide/index
|
2016-10-26 21:43:00 +00:00
|
|
|
|
2017-04-02 20:58:01 +00:00
|
|
|
Application-developer documentation
|
|
|
|
|
-----------------------------------
|
|
|
|
|
|
|
|
|
|
The user-space API manual gathers together documents describing aspects of
|
|
|
|
|
the kernel interface as seen by application developers.
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
2018-03-21 19:22:48 +00:00
|
|
|
userspace-api/index
|
2017-04-02 20:58:01 +00:00
|
|
|
|
|
|
|
|
|
2016-10-26 21:43:00 +00:00
|
|
|
Introduction to kernel development
|
|
|
|
|
----------------------------------
|
|
|
|
|
|
|
|
|
|
These manuals contain overall information about how to develop the kernel.
|
|
|
|
|
The kernel community is quite large, with thousands of developers
|
|
|
|
|
contributing over the course of a year. As with any large community,
|
|
|
|
|
knowing how things are done will make the process of getting your changes
|
|
|
|
|
merged much easier.
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
2016-10-18 11:05:32 +00:00
|
|
|
process/index
|
2016-10-26 06:23:14 +00:00
|
|
|
dev-tools/index
|
2016-11-17 10:32:33 +00:00
|
|
|
doc-guide/index
|
2017-05-11 11:03:27 +00:00
|
|
|
kernel-hacking/index
|
2018-02-17 05:39:34 +00:00
|
|
|
trace/index
|
2017-12-03 23:27:29 +00:00
|
|
|
maintainer/index
|
2016-10-26 21:43:00 +00:00
|
|
|
|
|
|
|
|
Kernel API documentation
|
|
|
|
|
------------------------
|
|
|
|
|
|
|
|
|
|
These books get into the details of how specific kernel subsystems work
|
|
|
|
|
from the point of view of a kernel developer. Much of the information here
|
|
|
|
|
is taken directly from the kernel source, with supplemental material added
|
|
|
|
|
as needed (or at least as we managed to add it — probably *not* all that is
|
2017-01-25 04:14:33 +00:00
|
|
|
needed).
|
2016-10-26 21:43:00 +00:00
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
2016-08-20 19:17:32 +00:00
|
|
|
driver-api/index
|
2016-10-28 08:14:10 +00:00
|
|
|
core-api/index
|
2016-08-13 14:12:43 +00:00
|
|
|
media/index
|
2017-05-12 12:14:02 +00:00
|
|
|
networking/index
|
2017-04-11 10:01:19 +00:00
|
|
|
input/index
|
2016-06-21 11:48:57 +00:00
|
|
|
gpu/index
|
2016-11-03 23:57:52 +00:00
|
|
|
security/index
|
2016-11-02 20:30:39 +00:00
|
|
|
sound/index
|
2016-10-21 02:54:22 +00:00
|
|
|
crypto/index
|
2017-05-12 09:50:22 +00:00
|
|
|
filesystems/index
|
2018-03-21 19:22:48 +00:00
|
|
|
vm/index
|
Documentation/sphinx: add basic working Sphinx configuration and build
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be run on the
various 'make *docs' targets.
All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
that and the Documentation/DocBook/Makefile are now expected to handle
all the documentation targets, explicitly ignoring them if they're not
relevant for that particular toolchain. The changes to the existing
DocBook Makefile are kept minimal.
There is graceful handling of missing Sphinx and rst2pdf (which is
needed for pdf output) by checking for the tool and python module,
respectively, with informative messages to the user.
If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
otherwise gracefully fall back to the Sphinx default theme, with an
informative message to the user, and slightly less pretty HTML output.
Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
epubdocs and xmldocs targets. The output documents are written into per
output type subdirectories under Documentation/output.
Finally, you can pass options to sphinx-build using the SPHINXBUILD make
variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
output from Sphinx.
This is based on the original work by Jonathan Corbet, but he probably
wouldn't recognize this as his own anymore.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
2016-05-19 12:14:05 +00:00
|
|
|
|
2017-05-13 10:50:43 +00:00
|
|
|
Architecture-specific documentation
|
|
|
|
|
-----------------------------------
|
|
|
|
|
|
|
|
|
|
These books provide programming details about architecture-specific
|
|
|
|
|
implementation.
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 2
|
|
|
|
|
|
|
|
|
|
sh/index
|
|
|
|
|
|
2016-11-08 12:26:09 +00:00
|
|
|
Korean translations
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 1
|
|
|
|
|
|
|
|
|
|
translations/ko_KR/index
|
|
|
|
|
|
2017-01-25 04:14:33 +00:00
|
|
|
Chinese translations
|
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 1
|
|
|
|
|
|
|
|
|
|
translations/zh_CN/index
|
|
|
|
|
|
2017-04-08 10:24:04 +00:00
|
|
|
Japanese translations
|
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
|
|
|
|
:maxdepth: 1
|
|
|
|
|
|
|
|
|
|
translations/ja_JP/index
|
|
|
|
|
|
Documentation/sphinx: add basic working Sphinx configuration and build
Add basic configuration and makefile to build documentation from any
.rst files under Documentation using Sphinx. For starters, there's just
the placeholder index.rst.
At the top level Makefile, hook Sphinx documentation targets alongside
(but independent of) the DocBook toolchain, having both be run on the
various 'make *docs' targets.
All Sphinx processing is placed into Documentation/Makefile.sphinx. Both
that and the Documentation/DocBook/Makefile are now expected to handle
all the documentation targets, explicitly ignoring them if they're not
relevant for that particular toolchain. The changes to the existing
DocBook Makefile are kept minimal.
There is graceful handling of missing Sphinx and rst2pdf (which is
needed for pdf output) by checking for the tool and python module,
respectively, with informative messages to the user.
If the Read the Docs theme (sphinx_rtd_theme) is available, use it, but
otherwise gracefully fall back to the Sphinx default theme, with an
informative message to the user, and slightly less pretty HTML output.
Sphinx can now handle htmldocs, pdfdocs (if rst2pdf is available),
epubdocs and xmldocs targets. The output documents are written into per
output type subdirectories under Documentation/output.
Finally, you can pass options to sphinx-build using the SPHINXBUILD make
variable. For example, 'make SPHINXOPTS=-v htmldocs' for more verbose
output from Sphinx.
This is based on the original work by Jonathan Corbet, but he probably
wouldn't recognize this as his own anymore.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
2016-05-19 12:14:05 +00:00
|
|
|
Indices and tables
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
* :ref:`genindex`
|
