From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: daniel@ffwll.ch, corbet@lwn.net, dri-devel@lists.freedesktop.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 1/1] drm: Add TODO item for fbdev driver conversion
Date: Thu, 17 Oct 2019 10:21:06 +0200 [thread overview]
Message-ID: <20191017082106.GU11828@phenom.ffwll.local> (raw)
In-Reply-To: <20191017074705.9140-2-tzimmermann@suse.de>
On Thu, Oct 17, 2019 at 09:47:05AM +0200, Thomas Zimmermann wrote:
> The DRM TODO list now contains an entry for converting fbdev
> drivers over to DRM.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> Documentation/gpu/todo.rst | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index 79785559d711..23b3a67794ba 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -462,3 +462,30 @@ Contact: Sam Ravnborg
>
> Outside DRM
> ===========
> +
> +Convert fbdev drivers to DRM
> +----------------------------
> +
> +There are plenty of fbdev drivers for older hardware. Some hwardware has
> +become obsolete, but some still provides good(-enough) framebuffers. The
> +drivers that are still useful should be converted to DRM and afterwards
> +removed from fbdev.
> +
> +Very simple fbdev drivers can best be converted by starting with a new
> +DRM driver. Simple KMS helpers and SHMEM should be able to handle any
> +existing hardware. The new driver's call-back functions are filled from
> +existing fbdev code.
> +
> +More complex fbdev drivers can be refactored step-by-step into a DRM
> +driver with the help of the DRM fbconv helpers. [1] These helpers provide
> +the transition layer between the DRM core infrastructure and the fbdev
> +driver interface. Create a new DRM driver on top of the fbconv helpers,
> +copy over the fbdev driver, and hook it up to the DRM code. Examples for
> +several fbdev drivers are available at [1] and a tutorial of this process
> +available at [2]. The result is a primitive DRM driver that can run X11
> +and Weston.
> +
> + - [1] https://gitlab.freedesktop.org/tzimmermann/linux/tree/fbconv
> + - [2] https://gitlab.freedesktop.org/tzimmermann/linux/blob/fbconv/drivers/gpu/drm/drm_fbconv_helper.c
btw if you want to push a patch to get this built and published:
https://gitlab.freedesktop.org/drm/igt-gpu-tools/blob/master/.gitlab-ci.yml
The "pages" job is the one which gets published to
https://drm.pages.freedesktop.org/igt-gpu-tools/
With that you could point at the pretty hmtl even.
-Daniel
> +
> +Contact: Thomas Zimmermann <tzimmermann@suse.de>
> --
> 2.23.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2019-10-17 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 7:47 [PATCH v3 0/1] DRM fbconv helpers for converting fbdev drivers Thomas Zimmermann
2019-10-17 7:47 ` [PATCH v3 1/1] drm: Add TODO item for fbdev driver conversion Thomas Zimmermann
2019-10-17 8:21 ` Daniel Vetter [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=20191017082106.GU11828@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--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