From: Jurriaan on Alpha <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Quick question about 2.4.18-pre7.
Date: Thu, 24 Jan 2002 06:59:15 +0100 [thread overview]
Message-ID: <20020124055915.GB2018@alpha.of.nowhere> (raw)
In-Reply-To: <3C4F7F92.564A4989@starband.net>
In-Reply-To: <3C4F7F92.564A4989@starband.net>
On Wed, Jan 23, 2002 at 10:29:22PM -0500, Justin Piszcz wrote:
> - Fix 3dfx fb crash with high pixelclock (Jurriaan on Alpha)
>
> I see that there is a 3DFX fix with high pixelclock.
>
> Without the fix, could this be a reason why my machine locks up when
> I am scrolling through various MPG or DIVX movies with mplayer
> (sometimes)?
>
> I have a 3DFX Voodoo 3 3000 AGP.
>
I wrote the fix, so here goes:
the fix only applies if you run your DAC at over half the maximum speed.
That means that with a Voodoo 3 you'd need a 150 MHz pixelclock to
trigger it. If you run linux using no framebuffer or a framebuffer at
frequencies below that, nothing is changed, and you'll need to find
another culprit. If you run above that, you could try to copy in
tdfxfb.c from the previous version. If that fixes it, I've got a
problem.
Anybody with a voodoo card and running high-frequency framebuffer:
please post your experiences.
Thanks,
Jurriaan
--
***************************** WARNING *****************************
Linux should not be used by those under the influence of MicroSoft.
May cause dissiness or vertigo. Consult your tech support before
using Linux. (note--after using Linux, you may notice extreme dis-
comfort when using MicroSoft. Discontinue use of Microsoft.)
***************************** WARNING *****************************
GNU/Linux 2.4.18-pre6 on Debian/Alpha 64-bits 990 bogomips load:0.03 0.22 0.18
prev parent reply other threads:[~2002-01-24 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 3:29 Quick question about 2.4.18-pre7 Justin Piszcz
2002-01-24 5:59 ` Jurriaan on Alpha [this message]
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=20020124055915.GB2018@alpha.of.nowhere \
--to=thunder7@xs4all.nl \
--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