All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
	Paul Mundt <lethal@linux-sh.org>
Cc: adaplas@pol.net
Subject: Re: Re: [PATCH][RFC] Add support for Epson S1D13806 FB
Date: Mon, 14 Mar 2005 23:18:25 +0800	[thread overview]
Message-ID: <200503142318.25740.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..

Some hardware waits for vblank/vsync before updating the start address, and
in the case of fbcon, that will be for each row of text. So yes, in this
case, ypan is not a win.

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

  parent reply	other threads:[~2005-03-14 15:18 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
2005-03-15  7:17           ` Paul Mundt
2005-03-15 10:26             ` Antonino A. Daplas
2005-03-14 15:18         ` Antonino A. Daplas [this message]
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=200503142318.25740.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.