From: Paolo Ornati <ornati@fastwebnet.it>
To: adaplas@pol.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc1: scrolling with tdfxfb 5 times slower
Date: Thu, 2 Sep 2004 11:23:25 +0200 [thread overview]
Message-ID: <200409021123.26299.ornati@fastwebnet.it> (raw)
In-Reply-To: <200409020410.22617.adaplas@hotpop.com>
On Wednesday 01 September 2004 22:10, Antonino A. Daplas wrote:
> On Wednesday 01 September 2004 19:55, Paolo Ornati wrote:
> > > This patch sets info->var.yres_virtual to the maximum upon driver
> > > load. If this works, it's possible to get sub-1 second scrolling
> > > speed.
> > >
> > > Reverse the previous patch first, then apply this patch.
> >
> > Results for 2.6.9-rc1 + your patch (time cat MAINTAINERS):
> >
> > CONFIG_FB_3DFX_ACCEL=n
> > ~1.27 s
> >
> > CONFIG_FB_3DFX_ACCEL=y
> > ~0.18 s
> >
> > BUT with CONFIG_FB_3DFX_ACCEL enabled I get strange video
> > "corruptions" (like bitmaps with random colors) that go away simply
> > swithcing to another console and than back to the previous.
>
> Might be a clipping problem? Maybe we need to set an upper limit
> to vyres, don't know for sure.
>
> Try doing an fbset -vyres 800, then keep doubling the number until
> you get the artifacts. If possible, do it for other bpp.
Doing some tests I've discovered that BPP doesn't influence this behavior
(kernel 2.6.9-rc1 + your patch, CONFIG_FB_3DFX_ACCEL=y):
BPP 800 1600 3200 6400 <-- VYRES
8 OK OK OK X
16 OK OK OK X
24 OK OK OK X
32 OK OK OK X
The upper limit for VYRES (after a lot of tests) seems to be around
4100/4200 (with 4100 all seems OK while with 4200 there are some
corruptions). This is the same for all BPP.
I don't understand why I have this problem only with
CONFIG_FB_3DFX_ACCEL=y...
--
Paolo Ornati
Gentoo Linux (kernel 2.6.8-gentoo-r3)
next prev parent reply other threads:[~2004-09-02 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:33 2.6.9-rc1: scrolling with tdfxfb 5 times slower Paolo Ornati
2004-08-31 20:28 ` Antonino A. Daplas
2004-09-01 7:10 ` Paolo Ornati
2004-08-31 23:29 ` Antonino A. Daplas
2004-09-01 7:20 ` Paolo Ornati
2004-09-01 10:21 ` Antonino A. Daplas
2004-09-01 10:51 ` Antonino A. Daplas
2004-09-01 11:55 ` Paolo Ornati
2004-09-01 20:10 ` Antonino A. Daplas
2004-09-02 9:23 ` Paolo Ornati [this message]
2004-09-02 12:20 ` Antonino A. Daplas
2004-09-02 17:10 ` Paolo Ornati
2004-09-02 19:52 ` Antonino A. Daplas
2004-09-01 20:20 ` Antonino A. Daplas
2004-09-02 9:26 ` Paolo Ornati
2004-09-01 11:48 ` Paolo Ornati
2004-09-01 1:21 ` David S. Miller
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=200409021123.26299.ornati@fastwebnet.it \
--to=ornati@fastwebnet.it \
--cc=adaplas@pol.net \
--cc=linux-kernel@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