linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Paul Mundt <lethal@linux-sh.org>,
	linux-fbdev-devel@lists.sourceforge.net
Cc: adaplas@pol.net
Subject: Re: Re: [PATCH][RFC] Add support for Epson S1D13806 FB
Date: Mon, 14 Mar 2005 23:06:00 +0800	[thread overview]
Message-ID: <200503142306.00236.adaplas@hotpop.com> (raw)
In-Reply-To: <20050314143509.GD2695@linux-sh.org>

On Monday 14 March 2005 22:35, Paul Mundt wrote:
> On Mon, Mar 14, 2005 at 10:10:35PM +0800, Antonino A. Daplas wrote:
> > BTW, I would guess that scrolling is slow in this driver.  Since this
> > driver can do pan_display, If this:
> >
> > info->flags = FBINFO_DEFAULT | FBINFO_HWACCEL_YPAN;
> >
> > is added somewhere before register_framebuffer(), and var->xres_virtual >
> > var->xres, you might get a several-fold increase in scrolling speed
> > (since scrolling mode will be SCROLL_PAN_REDRAW instead of
> > SCROLL_REDRAW).
>
> This is interesting. When FBINFO_HWACCEL_YPAN was added to hitfb, it slowed
> down scrolling by several orders of magnitude. Perhaps it was something
> relating to how the pan_display was implemented, but it's definitely not
> a general win for everyone..

In the case of hitfb, fillrect and copyarea are both accelerated.  So the proper flags would
be:

FBINFO_DEFAULT | FBINFO_HWACCEL_YPAN | FBINFO_HWACCEL_COPYAREA |
FBINFO_HWACCEL_FILLRECT.

If you think that ypan has problems, then you can remove the
FBINFO_HWACCEL_YPAN part.

Tony




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-14 15:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 10:13 [PATCH][RFC] Add support for Epson S1D13806 FB Thibaut VARENE
2005-03-14 12:15 ` Antonino A. Daplas
2005-03-14 13:00   ` Thibaut VARENE
2005-03-14 13:13     ` Antonino A. Daplas
2005-03-14 14:10     ` Antonino A. Daplas
2005-03-14 14:24       ` Thibaut VARENE
2005-03-14 15:06         ` Antonino A. Daplas
2005-03-14 14:35       ` Paul Mundt
2005-03-14 15:06         ` Antonino A. Daplas [this message]
2005-03-15  7:17           ` Paul Mundt
2005-03-15 10:26             ` Antonino A. Daplas
2005-03-14 15:18         ` Antonino A. Daplas
2005-03-14 13:18   ` Paul Mundt
2005-03-14 13:25     ` Geert Uytterhoeven
2005-03-14 13:34       ` Thibaut VARENE
2005-03-14 13:53         ` Antonino A. Daplas
2005-03-14 14:09           ` Thibaut VARENE
2005-03-14 14:12           ` Thibaut VARENE
2005-03-14 13:44       ` Paul Mundt

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=200503142306.00236.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=lethal@linux-sh.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).