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 v3] drm: add overview diagram for drm stack
Date: Thu, 29 May 2025 08:28:07 +0700 [thread overview]
Message-ID: <aDe4J8Cmlzicggx2@archie.me> (raw)
In-Reply-To: <20250527-drm-doc-updates-v3-1-58e97a831d03@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2735 bytes --]
On Tue, May 27, 2025 at 03:17:43AM -0400, Abdulrasaq Lawani wrote:
> revert promotion of overview diagram title to that
> of previous commit in introduction.rst
>
The patch description doesn't really describe the diff below, which is
to add overview diagram instead. Maybe you can replace that with from your v1?
> diff --git a/Documentation/gpu/introduction.rst b/Documentation/gpu/introduction.rst
> index 3cd0c8860b949408ed570d3f9384edd5f03df002..a8d3f953a470180b395ec52a45d0f3f4561424e0 100644
> --- a/Documentation/gpu/introduction.rst
> +++ b/Documentation/gpu/introduction.rst
> @@ -14,7 +14,45 @@ including the TTM memory manager, output configuration and mode setting,
> and the new vblank internals, in addition to all the regular features
> found in current kernels.
>
> -[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 |
> + +----------------+ +-------------------+
> +
>
> Style Guidelines
> ================
>
The diff itself looks good.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-05-29 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 7:17 Abdulrasaq Lawani
2025-05-29 1:28 ` Bagas Sanjaya [this message]
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=aDe4J8Cmlzicggx2@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®