From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Abdulrasaq Lawani <abdulrasaqolawani@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jonathan Corbet <corbet@lwn.net>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: add overview diagram for drm stack
Date: Fri, 23 May 2025 10:10:42 +0700 [thread overview]
Message-ID: <aC_nMs-hAyd8cpDJ@archie.me> (raw)
In-Reply-To: <20250522-drm-doc-updates-v1-1-d1efd54740bd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4527 bytes --]
On Thu, May 22, 2025 at 06:20:27PM -0400, Abdulrasaq Lawani wrote:
> -[Insert diagram of typical DRM stack here]
> +Overview of the Linux DRM Architecture
> +-----------------------------------------------
> ++-----------------------------+
> +| User-space Apps |
> +| (Games, Browsers, ML, etc.) |
> ++-----------------------------+
> + |
> + v
> ++---------------------------------------+
> +| Graphics APIs | Compute APIs |
> +| (OpenGL, Vulkan) | (OpenCL, CUDA) |
> ++---------------------------------------+
> + | |
> + v v
> ++---------------------+ +-----------------------+
> +| User-space Driver | | Compute Runtime |
> +| (Mesa, AMD/NVIDIA) | | (OpenCL, CUDA, ROCm) |
> ++---------------------+ +-----------------------+
> + | |
> + +--------+----------+
> + |
> + v
> + +-----------------------+
> + | libdrm (DRM API) |
> + +-----------------------+
> + |
> + v
> ++-------------------------------------------+
> +| Kernel DRM/KMS Driver (i915, amdgpu, |
> +| nouveau, etc.) |
> ++-------------------------------------------+
> + | |
> + v v
> ++----------------+ +-------------------+
> +| GPU Display HW | | GPU Compute Units |
> ++----------------+ +-------------------+
> +
I get multiple Sphinx indentation warnings and errors:
Documentation/gpu/introduction.rst:23: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/introduction.rst:22: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/introduction.rst:23: WARNING: Blank line required after table. [docutils]
Documentation/gpu/introduction.rst:24: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/introduction.rst:25: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/introduction.rst:29: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/introduction.rst:28: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/introduction.rst:29: WARNING: Blank line required after table. [docutils]
Documentation/gpu/introduction.rst:29: WARNING: Inline substitution_reference start-string without end-string. [docutils]
Documentation/gpu/introduction.rst:30: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/introduction.rst:31: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/introduction.rst:35: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/introduction.rst:35: WARNING: Inline substitution_reference start-string without end-string. [docutils]
Documentation/gpu/introduction.rst:36: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/introduction.rst:37: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/introduction.rst:37: WARNING: Blank line required after table. [docutils]
Documentation/gpu/introduction.rst:38: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/introduction.rst:39: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/introduction.rst:42: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/introduction.rst:42: WARNING: Blank line required after table. [docutils]
Documentation/gpu/introduction.rst:43: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/introduction.rst:44: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/introduction.rst:48: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/introduction.rst:48: WARNING: Blank line required after table. [docutils]
Documentation/gpu/introduction.rst:48: WARNING: Inline substitution_reference start-string without end-string. [docutils]
Documentation/gpu/introduction.rst:49: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/introduction.rst:50: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Please wrap the diagram above in literal code block.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-23 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 22:20 Abdulrasaq Lawani
2025-05-23 3:10 ` Bagas Sanjaya [this message]
2025-05-23 11:58 ` Jonathan Corbet
2025-05-24 17:34 ` Abdulrasaq Lawani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aC_nMs-hAyd8cpDJ@archie.me \
--to=bagasdotme@gmail.com \
--cc=abdulrasaqolawani@gmail.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®