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>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] drm: add overview diagram for drm stack
Date: Thu, 5 Jun 2025 09:01:14 +0700 [thread overview]
Message-ID: <aED6ahMoKjO11JVv@archie.me> (raw)
In-Reply-To: <aEBaJ5zMHfzhpdlz@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 3596 bytes --]
On Wed, Jun 04, 2025 at 04:37:27PM +0200, Simona Vetter wrote:
> On Mon, Jun 02, 2025 at 08:28:30AM +0700, Bagas Sanjaya wrote:
> > On Sun, Jun 01, 2025 at 06:18:47PM -0400, Abdulrasaq Lawani wrote:
> > > Add an overview diagram of Linux DRM architecture for
> > > graphics and compute to introduction.rst
> > >
> > > Signed-off-by: Abdulrasaq Lawani <abdulrasaqolawani@gmail.com>
> > > ---
> > > <snipped>...
> > > 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 |
> > > + +----------------+ +-------------------+
> > > +
>
> I'm a bit late to the party, apologies. I'm not sure how much use there is
> in an extremely simplified diagram like this, least because it's really
> incomplete and leaves out the entire display and compositor side.
>
> My idea was that we'd instead link to the large pile of introductory and
> overview talks further down in this file, if people want to get an
> overview over what drm does.
So the stub that's being patched here can be removed, right?
>
> If you want I guess you could add some links to the relevant wikipedia
> pages, I think they also do a fairly decent job of explaining the big
> picture.
What articles?
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-06-05 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 22:18 [PATCH v4] drm: add overview diagram for drm stack Abdulrasaq Lawani
2025-06-02 1:28 ` Bagas Sanjaya
2025-06-04 14:37 ` Simona Vetter
2025-06-05 2:01 ` Bagas Sanjaya [this message]
2025-06-09 18:23 ` 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=aED6ahMoKjO11JVv@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;
as well as URLs for NNTP newsgroup(s).