Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
40 lines
906 B
ReStructuredText
40 lines
906 B
ReStructuredText
===============
|
|
GPU RFC Section
|
|
===============
|
|
|
|
For complex work, especially new uapi, it is often good to nail the high level
|
|
design issues before getting lost in the code details. This section is meant to
|
|
host such documentation:
|
|
|
|
* Each RFC should be a section in this file, explaining the goal and main design
|
|
considerations. Especially for uapi make sure you Cc: all relevant project
|
|
mailing lists and involved people outside of dri-devel.
|
|
|
|
* For uapi structures add a file to this directory with and then pull the
|
|
kerneldoc in like with real uapi headers.
|
|
|
|
* Once the code has landed move all the documentation to the right places in
|
|
the main core, helper or driver sections.
|
|
|
|
.. toctree::
|
|
|
|
gpusvm.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_gem_lmem.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_scheduler.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_small_bar.rst
|
|
|
|
.. toctree::
|
|
|
|
i915_vm_bind.rst
|
|
|
|
.. toctree::
|
|
color_pipeline.rst |