From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
David Airlie <airlied@linux.ie>,
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 14:08:38 +0100 [thread overview]
Message-ID: <b54d8092-c7bc-93b3-c306-b77dd57db6ce@redhat.com> (raw)
In-Reply-To: <YfKCoOk2sxDzHVXv@phenom.ffwll.local>
On 1/27/22 12:31, Daniel Vetter wrote:
> On Thu, Jan 27, 2022 at 11:50:30AM +0100, Javier Martinez Canillas wrote:
[snip]
>> Indeed. And we can add such section as a follow-up. Maybe referring to some
>> of the drivers in drivers/gpu/drm/tiny.
>
> Do we have a talk anywhere for tiny?
>
I couldn't find one for tiny.
> Otherwise I think it'd be good to just add a paragraph about "hey tiny
> exists" and maybe link to fbdev helpers and simple pipe helpers to get
> people started with the right entry points for simple drivers.
>
Ok. I can add some sentences about drm/tiny and point out that the DRM
drivers there could be used as a good references for simple drivers.
> And make it clear that the above pile of links is more for general
> overview and if you don't yet know what exactly it is you need.
>
Sure, I'll add that too.
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2022-01-27 13:08 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
2022-01-27 11:31 ` Daniel Vetter
2022-01-27 13:08 ` Javier Martinez Canillas [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=b54d8092-c7bc-93b3-c306-b77dd57db6ce@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=corbet@lwn.net \
--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®