From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Subject: Re: [PATCH] drm/doc: Add section in the introduction page about learning material
Date: Thu, 27 Jan 2022 11:50:30 +0100 [thread overview]
Message-ID: <b305cb36-1a09-c990-a3e6-98d420c62e3a@redhat.com> (raw)
In-Reply-To: <c99a7784-7ac4-e305-1a06-dfb514a409ff@suse.de>
Hello Thomas,
On 1/27/22 10:18, Thomas Zimmermann wrote:
> Hi Javier,
>
> thanks for this patch.
>
> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
>
Thanks!
> Find some ideas for consideration below.
>
[snip]
>> +
>> +Learning material
>> +=================
>
> Maybe 'External References'.
>
Agreed, I'll change it.
>> +
>> +Since the Linux DRM layer supports complex graphics devices, it can be quite
>> +overwhelming for newcomers to get familiar with all the needed concepts and
>> +learn the subsystem's internals.
>
> It sounds a bit intimdating to me. Can we give it a positive spin?
>
Pekka also had reservations about this paragraph, so I think that will just
drop it. The goal of having this section was to ease the learning curve but
the way I worded it may reinforce the perception that DRM is hard to learn.
> IMHO we could add a separate section that talks about complexity and
> provides guidelines about how to deal with it: trivial HW? use simple
> pipe; dedicated VRAM? try TTM; awkward color formats? see
> drm_format_helper.c
>
Indeed. And we can add such section as a follow-up. Maybe referring to some
of the drivers in drivers/gpu/drm/tiny.
Best regards, --
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-01-27 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 8:20 Javier Martinez Canillas
2022-01-27 9:05 ` Pekka Paalanen
2022-01-27 10:46 ` Javier Martinez Canillas
2022-01-27 11:09 ` Pekka Paalanen
2022-01-27 9:18 ` Thomas Zimmermann
2022-01-27 10:50 ` Javier Martinez Canillas [this message]
2022-01-27 11:31 ` Daniel Vetter
2022-01-27 13:08 ` Javier Martinez Canillas
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=b305cb36-1a09-c990-a3e6-98d420c62e3a@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pekka.paalanen@collabora.co.uk \
--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®