mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Miro Kropacek <miro.kropacek@gmail.com>
Cc: geert@linux-m68k.org, schmitzmic@gmail.com, lilinmao@kylinos.cn,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: atafb: Restrict SuperVidel handling to the Falcon
Date: Wed, 18 Nov 2026 19:38:00 +0100	[thread overview]
Message-ID: <248e818d-8af8-4068-92db-c06c10ce6e58@gmx.de> (raw)
In-Reply-To: <20261113005616.402721-1-miro.kropacek@gmail.com>

On 11/13/26 01:56, Miro Kropacek wrote:
> A framebuffer at 0xa0000000 or above is taken as being in SuperVidel
> RAM. A TT with a VME graphics card such as the Nova has its framebuffer
> there too, so in 8bpp it gets the Falcon palette registers instead of
> the card's VGA DAC, and in 8, 16 and 32bpp the SuperBlitter, which it
> does not have.
> 
> The SuperVidel exists only for the Falcon, so check for the Falcon video
> hardware as well.
> 
> Fixes: 51df976c3268 ("fbdev: atafb: Add support for further video bit depths on atafb:external")
> Fixes: d463633d63e6 ("fbdev: atafb: Add support for SuperVidel's SuperBlitter")
> Cc: stable@vger.kernel.org
> Reported-by: Christian Zietz <czietz@gmx.net>
> Signed-off-by: Miro Kropacek <miro.kropacek@gmail.com>
> ---
>   drivers/video/fbdev/atafb.c | 18 +++++++++++++-----
>   1 file changed, 13 insertions(+), 5 deletions(-)
applied.

Thanks!
Helge

      reply	other threads:[~2026-11-18 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13  0:56 Miro Kropacek
2026-11-18 18:38 ` Helge Deller [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=248e818d-8af8-4068-92db-c06c10ce6e58@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=lilinmao@kylinos.cn \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=miro.kropacek@gmail.com \
    --cc=schmitzmic@gmail.com \
    /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®