All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: tdfx framebuffer garbles display in 2.6.19.5
Date: Mon, 26 Feb 2007 21:32:23 +0100	[thread overview]
Message-ID: <20070226203223.GA161@DervishD> (raw)
In-Reply-To: <1172510654.7101.11.camel@daplas>

    Hi Antonino :)

 * Antonino A. Daplas <adaplas@gmail.com> dixit:
> On Mon, 2007-02-26 at 18:13 +0100, DervishD wrote:
> > > Try fbset -a -vyres 600 first and let us know of the result.
> > 
> > After doing this, I no longer can garble the display (before, just a
> > "ls -lR /" was enough to do it, in fact, any big output garbled the
> > display). The only problem with this solution is that the scroll
> > speed has decreased a bit. In fact, the scroll speed is affected by
> > the vyres parameter a lot! The highter the vyres, the faster the
> > scroll, and I cannot reproduce the problem anymore after changing it
> > once!
> 
> Display panning is what makes scrolling fast which is the default
> scroll method if vyres > yres.  Unfortunately, tdfxfb occasionally
> have problems with this method, the higher the vyres, the greater the
> likelihood of screen corruption.

    Then I'll try with 4096 and will diminish the number until the
display is stable.

> That's why tdfxb limits the vyres to a maximum of 4096. As to why the
> problem disappeared just by changing this parameter, that I too don't
> know.

    Probably setting it back to 4096 will make the problem reappear.
Right now I cannot test, but I'll make some experiments.

    Thanks a lot!

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

  reply	other threads:[~2007-02-26 20:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 14:47 tdfx framebuffer garbles display in 2.6.19.5 DervishD
2007-02-26 15:24 ` Antonino A. Daplas
2007-02-26 15:24   ` Antonino A. Daplas
2007-02-26 17:13   ` DervishD
2007-02-26 17:24     ` Antonino A. Daplas
2007-02-26 20:32       ` DervishD [this message]
2007-02-27 23:09         ` Antonino A. Daplas
2007-02-27 23:09           ` Antonino A. Daplas
2007-02-28 10:49           ` DervishD
2007-03-01 16:01           ` DervishD
2007-03-06  1:33             ` Antonino A. Daplas
2007-03-06  1:33               ` Antonino A. Daplas
2007-03-06  6:25               ` DervishD
2007-03-06  6:53                 ` Antonino A. Daplas
2007-03-06 11:17                   ` DervishD
2007-03-07 10:02                   ` DervishD
2007-03-14  9:06                   ` [TESTED] " DervishD
2007-03-14  9:06                     ` DervishD
2007-02-26 15:24 ` James Simmons
2007-02-26 15:24   ` James Simmons
2007-02-26 17:04   ` DervishD

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=20070226203223.GA161@DervishD \
    --to=lkml@dervishd.net \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.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 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.