From: Thomas Zimmermann <tzimmermann@suse.de> To: Sven Schnelle <svens@stackframe.org> Cc: linux-fbdev@vger.kernel.org, dri-devel <dri-devel@lists.freedesktop.org>, linux-parisc@vger.kernel.org, Helge Deller <deller@gmx.de> Subject: Re: [PATCH/RFT] fbdev driver for HP Visualize FX cards Date: Mon, 1 Nov 2021 10:33:12 +0100 [thread overview] Message-ID: <e21cdf83-2178-7c59-2585-a6012f861f68@suse.de> (raw) In-Reply-To: <87r1c0s1bt.fsf@x1.stackframe.org> [-- Attachment #1.1: Type: text/plain, Size: 1884 bytes --] Hi Am 01.11.21 um 09:54 schrieb Sven Schnelle: > Hi Thomas, > > Thomas Zimmermann <tzimmermann@suse.de> writes: > >> Am 31.10.21 um 20:53 schrieb Sven Schnelle: >>> Hi List(s), >>> i wrote a fbdev driver for the HP Visualize FX cards used some of >>> the >>> PA-RISC workstations. It utilizes some of the 2D acceleration features >>> present in the card. >>> [..] >> >> Thanks for all the work you put into this. We welcome drivers even for >> older hardware, but not for fbdev. DRM is all the rage now and has >> been for a while. I'd like to ask you to convert the driver to DRM and >> resubmit to <dri-devel@lists.freedesktop.org>. >> >> I while ago, I made conversion helpers for this. You can look at [1] >> for a trivial DRM drivers that wraps existing fbdev drivers for use >> with DRM. Once you have that, it turns into a refactoring job. > > Thanks, i wasn't aware as i normally don't do any graphics related > development. I take a look at dri and port the driver, which is > hopefully not too hard. Sounds good. The one big difference when converting is that DRM really wants drivers to support 32-bit XRGB colors. It's not a DRM limitation per se, but a requirement of today's userspace programs. AFAICS your fbdev driver uses a 256-color palette format. So the DRM driver would have to convert XRGB8888 to 8-bit RGB332 and install a corresponding palette. Don't worry, it's easy. Take a look at the cirrus driver for a simple DRM driver. [1] If you need help, there's <dri-devel@lists.freedesktop.org>. Best regards Thomas [1] https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/tiny/cirrus.c > > Sven > -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 840 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Zimmermann <tzimmermann@suse.de> To: Sven Schnelle <svens@stackframe.org> Cc: linux-parisc@vger.kernel.org, linux-fbdev@vger.kernel.org, dri-devel <dri-devel@lists.freedesktop.org>, Helge Deller <deller@gmx.de> Subject: Re: [PATCH/RFT] fbdev driver for HP Visualize FX cards Date: Mon, 1 Nov 2021 10:33:12 +0100 [thread overview] Message-ID: <e21cdf83-2178-7c59-2585-a6012f861f68@suse.de> (raw) In-Reply-To: <87r1c0s1bt.fsf@x1.stackframe.org> [-- Attachment #1.1: Type: text/plain, Size: 1884 bytes --] Hi Am 01.11.21 um 09:54 schrieb Sven Schnelle: > Hi Thomas, > > Thomas Zimmermann <tzimmermann@suse.de> writes: > >> Am 31.10.21 um 20:53 schrieb Sven Schnelle: >>> Hi List(s), >>> i wrote a fbdev driver for the HP Visualize FX cards used some of >>> the >>> PA-RISC workstations. It utilizes some of the 2D acceleration features >>> present in the card. >>> [..] >> >> Thanks for all the work you put into this. We welcome drivers even for >> older hardware, but not for fbdev. DRM is all the rage now and has >> been for a while. I'd like to ask you to convert the driver to DRM and >> resubmit to <dri-devel@lists.freedesktop.org>. >> >> I while ago, I made conversion helpers for this. You can look at [1] >> for a trivial DRM drivers that wraps existing fbdev drivers for use >> with DRM. Once you have that, it turns into a refactoring job. > > Thanks, i wasn't aware as i normally don't do any graphics related > development. I take a look at dri and port the driver, which is > hopefully not too hard. Sounds good. The one big difference when converting is that DRM really wants drivers to support 32-bit XRGB colors. It's not a DRM limitation per se, but a requirement of today's userspace programs. AFAICS your fbdev driver uses a 256-color palette format. So the DRM driver would have to convert XRGB8888 to 8-bit RGB332 and install a corresponding palette. Don't worry, it's easy. Take a look at the cirrus driver for a simple DRM driver. [1] If you need help, there's <dri-devel@lists.freedesktop.org>. Best regards Thomas [1] https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/tiny/cirrus.c > > Sven > -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-11-01 9:33 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-31 19:53 [PATCH/RFT] fbdev driver for HP Visualize FX cards Sven Schnelle 2021-10-31 19:53 ` [PATCH] video: fbdev: add HP Visualize FX driver Sven Schnelle 2021-11-01 7:07 ` [PATCH/RFT] fbdev driver for HP Visualize FX cards Thomas Zimmermann 2021-11-01 8:54 ` Sven Schnelle 2021-11-01 8:54 ` Sven Schnelle 2021-11-01 9:33 ` Thomas Zimmermann [this message] 2021-11-01 9:33 ` Thomas Zimmermann 2021-11-01 10:11 ` Sven Schnelle 2021-11-01 10:11 ` Sven Schnelle 2021-11-06 21:02 ` Sven Schnelle 2021-11-06 21:02 ` Sven Schnelle 2021-11-08 8:37 ` Thomas Zimmermann 2021-11-08 8:37 ` Thomas Zimmermann 2021-11-08 16:31 ` Sven Schnelle 2021-11-08 16:31 ` Sven Schnelle 2021-11-08 19:08 ` Thomas Zimmermann 2021-11-08 19:08 ` Thomas Zimmermann
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=e21cdf83-2178-7c59-2585-a6012f861f68@suse.de \ --to=tzimmermann@suse.de \ --cc=deller@gmx.de \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-parisc@vger.kernel.org \ --cc=svens@stackframe.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.