From: Ondrej Zary <linux@rainbow-software.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-fbdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: [PATCH 5/5] [resend] gxt4500: enable panning
Date: Tue, 03 Mar 2015 21:01:00 +0000 [thread overview]
Message-ID: <1425416460-10773-5-git-send-email-linux@rainbow-software.org> (raw)
In-Reply-To: <1425416460-10773-1-git-send-email-linux@rainbow-software.org>
The driver implements pan_display but the corresponding flags are not set.
Add FBINFO_HWACCEL_XPAN and FBINFO_HWACCEL_YPAN to flags to allow HW
accelerated panning (for fast scrolling).
Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
---
drivers/video/fbdev/gxt4500.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/gxt4500.c b/drivers/video/fbdev/gxt4500.c
index f278c82..7f97c89 100644
--- a/drivers/video/fbdev/gxt4500.c
+++ b/drivers/video/fbdev/gxt4500.c
@@ -699,7 +699,8 @@ static int gxt4500_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
#endif
info->fbops = &gxt4500_ops;
- info->flags = FBINFO_FLAG_DEFAULT;
+ info->flags = FBINFO_FLAG_DEFAULT | FBINFO_HWACCEL_XPAN |
+ FBINFO_HWACCEL_YPAN;
err = fb_alloc_cmap(&info->cmap, 256, 0);
if (err) {
--
Ondrej Zary
next prev parent reply other threads:[~2015-03-03 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 21:00 [PATCH 1/5] [resend] gxt4500: enable on non-PPC architectures Ondrej Zary
2015-03-03 21:00 ` [PATCH 2/5] [resend] gxt4500: fix 16bpp 565 mode Ondrej Zary
2015-03-03 21:00 ` [PATCH 3/5] [resend] gxt4500: fix color order Ondrej Zary
2015-03-03 21:00 ` [PATCH 4/5] [resend] gxt4500: Use write-combining for framebuffer (PAT and MTRR) Ondrej Zary
2015-03-03 21:01 ` Ondrej Zary [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-24 20:15 [PATCH 0/5] [resend] gxt4500: Make usable on x86 and fix some bugs Ondrej Zary
2015-08-24 20:15 ` [PATCH 5/5] [resend] gxt4500: enable panning Ondrej Zary
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=1425416460-10773-5-git-send-email-linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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).