Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v4 3/3] fbcon: Add option to enable legacy hardware acceleration
Date: Fri, 4 Feb 2022 11:17:33 +0100	[thread overview]
Message-ID: <ee851128-1080-d0ae-6c55-e1816bc89e74@gmx.de> (raw)
In-Reply-To: <CAMuHMdWTuFt12faj58sLv3H9rN0xK-+CCTkFeEiKdLSQTU2Lmg@mail.gmail.com>

Hello Geert,

On 2/4/22 09:37, Geert Uytterhoeven wrote:
> On Wed, Feb 2, 2022 at 8:05 PM Helge Deller <deller@gmx.de> wrote:
>> Add a config option CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION to
>> enable bitblt and fillrect hardware acceleration in the framebuffer
>> console. If disabled, such acceleration will not be used, even if it is
>> supported by the graphics hardware driver.
>
> Note that this also applies to vertical panning and wrapping.

That's correct.
Would you mind to send a patch which adds this info?

Helge

  reply	other threads:[~2022-02-04 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 13:55 [PATCH v4 0/3] Fix regression introduced by disabling accelerated scrolling in fbcon Helge Deller
2022-02-02 13:55 ` [PATCH v4 1/3] Revert "fbdev: Garbage collect fbdev scrolling acceleration, part 1 (from TODO list)" Helge Deller
2022-02-02 13:55 ` [PATCH v4 2/3] Revert "fbcon: Disable accelerated scrolling" Helge Deller
2022-02-02 13:55 ` [PATCH v4 3/3] fbcon: Add option to enable legacy hardware acceleration Helge Deller
2022-02-04  8:37   ` Geert Uytterhoeven
2022-02-04 10:17     ` Helge Deller [this message]
2022-02-04 10:24       ` Geert Uytterhoeven
2022-02-04 17:31         ` Helge Deller
2022-02-02 15:00 ` [PATCH v4 0/3] Fix regression introduced by disabling accelerated scrolling in fbcon Daniel Vetter

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=ee851128-1080-d0ae-6c55-e1816bc89e74@gmx.de \
    --to=deller@gmx.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.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