| 1 |
=============== |
| 2 |
GPU RFC Section |
| 3 |
=============== |
| 4 |
|
| 5 |
For complex work, especially new uapi, it is often good to nail the high level |
| 6 |
design issues before getting lost in the code details. This section is meant to |
| 7 |
host such documentation: |
| 8 |
|
| 9 |
* Each RFC should be a section in this file, explaining the goal and main design |
| 10 |
considerations. Especially for uapi make sure you Cc: all relevant project |
| 11 |
mailing lists and involved people outside of dri-devel. |
| 12 |
|
| 13 |
* For uapi structures add a file to this directory with and then pull the |
| 14 |
kerneldoc in like with real uapi headers. |
| 15 |
|
| 16 |
* Once the code has landed move all the documentation to the right places in |
| 17 |
the main core, helper or driver sections. |
| 18 |
|
| 19 |
.. toctree:: |
| 20 |
|
| 21 |
gpusvm.rst |
| 22 |
|
| 23 |
.. toctree:: |
| 24 |
|
| 25 |
i915_gem_lmem.rst |
| 26 |
|
| 27 |
.. toctree:: |
| 28 |
|
| 29 |
i915_scheduler.rst |
| 30 |
|
| 31 |
.. toctree:: |
| 32 |
|
| 33 |
i915_small_bar.rst |
| 34 |
|
| 35 |
.. toctree:: |
| 36 |
|
| 37 |
i915_vm_bind.rst |
| 38 |
|
| 39 |
.. toctree:: |
| 40 |
color_pipeline.rst |