linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Sven Schnelle <svens@stackframe.org>,
	parisc-linux@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: Helge Deller <deller@gmx.de>
Subject: Re: [PATCH/RFT] fbdev driver for HP Visualize FX cards
Date: Mon, 1 Nov 2021 08:07:41 +0100	[thread overview]
Message-ID: <cd0f90d9-7dba-af33-f88b-289fc6f80b51@suse.de> (raw)
In-Reply-To: <20211031195347.13754-1-svens@stackframe.org>


[-- Attachment #1.1: Type: text/plain, Size: 2212 bytes --]

(cc'ing dri-devel)

Hi

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.
> 
> What is working right now:
> 
> - modesetting (tested all VESA modes between 640x480 - 1600x1200).
> - hardware cursor
> - 2D acceleration like imageblit and fillrect.
> 
> What is not (fully) working:
> 
> - X11 with fbdev. xinit + mwm looks almost ok, except some corruption
> where the text cursor was drawn when it is moved.
> - more advanced X11 programs. xfce4-session doesn't really show much.
> 
> I would be most interested if people could test this driver with their FX
> cards and report. I know that Visualize FXe doesn't work because it uses
> completely different register addresses. For FX10 i would hope that they
> share the same register set as they are based on the same architecture.
> Note that you have to disable the sticon driver, otherwhise that one would
> hog the PCI card and visualizefx would never be probed.
> 
> Not sure about FX2/4/6. Might be different, might be not.
> 
> I obtained all the knowledge about the registers by watching what STI and the HP-UX
> X Server writes into the card. So the register names might be called different
> compared to what HP has written in their data books.

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.

Best regards
Thomas

[1] 
https://gitlab.freedesktop.org/tzimmermann/linux/-/commits/fbconv-plus-drivers

> 
> 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 --]

  parent reply	other threads:[~2021-11-01  7:07 UTC|newest]

Thread overview: 10+ 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 ` Thomas Zimmermann [this message]
2021-11-01  8:54   ` [PATCH/RFT] fbdev driver for HP Visualize FX cards Sven Schnelle
2021-11-01  9:33     ` Thomas Zimmermann
2021-11-01 10:11       ` Sven Schnelle
2021-11-06 21:02       ` Sven Schnelle
2021-11-08  8:37         ` Thomas Zimmermann
2021-11-08 16:31           ` Sven Schnelle
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=cd0f90d9-7dba-af33-f88b-289fc6f80b51@suse.de \
    --to=tzimmermann@suse.de \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=parisc-linux@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: 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).