linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Eger <eger-sender-da68b9@theboonies.us>
To: Thomas Winischhofer <thomas@winischhofer.net>
Cc: David Eger <eger@havoc.gtf.org>, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH] sisfb accel capabilities
Date: Thu,  3 Jun 2004 08:26:49 -0500	[thread overview]
Message-ID: <1086269209.40bf27191fe1c@mail.theboonies.us> (raw)
In-Reply-To: <40BEF4ED.7090909@winischhofer.net>

Quoting Thomas Winischhofer <thomas@winischhofer.net>:

> David Eger wrote:
> > The following patch updates sisfb for the new fb accel capabilities
> > patch I'm sending upstream.  By default, this patch will rely on your
> > copyarea() and fillrect() accel functions instead of the panning.
>
> Could you give me any hint why this should be faster than panning?

The logic to prefer copyarea()/fillrect() to panning is in the main patch.  If
panning is faster than using these for most cards, then the default when both
are available should be panning as you say.  But I'll need numbers to determine
that ;-)  I think many drivers just map a chunk of video ram just big enough
for the requested resolution, so panning does zero for them :-/

> 1) fillrect and copyarea WERE (resp. ARE) being called here despite your
> previous statement that they were not. Fillrect is used to clear every
> line after pressing enter, and copyrect was used to copy the buffer to
> the start of the virtual screen when the end was reached.)

bizarre.  For radeonfb, fillrect() was called to clear the last line as you say,
but copyarea() never was.  I'll have to dig back through the old code to really
 grok your statement.

> 2) I still don't understand the meaning of FBINFO_HWACCEL_XPAN
> (especially as your sisfb patch sets it although sisfb did not support
> x-panning until yesterday evening...)

Good catch.  My patch should not set that flag, as it's inaccurate for your
driver.  My bad.  Good thing these are going through the individual driver
maintainers ;-)

> > Please test the core patch + this patch, and let me know your console
> > works.  I'm interested to hear what speeds you see :-)
>
> I will, but it will take some while. I need to merge your changes into
> my development version (which has been modified quite a bit).

Thanks.

-dte



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504

  reply	other threads:[~2004-06-03 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  2:44 [PATCH] sisfb accel capabilities David Eger
2004-06-03  9:52 ` Thomas Winischhofer
2004-06-03 13:26   ` David Eger [this message]
2004-06-03 15:07     ` Antonino A. Daplas
2004-06-03 16:40     ` Thomas Winischhofer
2004-06-03 17:08       ` David Eger
2004-06-06 11:19         ` Geert Uytterhoeven
2004-06-06 13:19           ` Thomas Winischhofer
2004-06-06 11:08   ` Geert Uytterhoeven

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=1086269209.40bf27191fe1c@mail.theboonies.us \
    --to=eger-sender-da68b9@theboonies.us \
    --cc=eger-dated-1086874014.cda599@theboonies.us \
    --cc=eger@havoc.gtf.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=thomas@winischhofer.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).