Date: 18 Sep 1998 00:12:52 +0200 From: dag-erli@ifi.uio.no (Dag-Erling =?iso-8859-1?Q?Co=EFdan?= =?iso-8859-1?Q?Sm=F8rgrav?= ) To: Mikael Karpberg <karpen@ocean.campus.luth.se> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/isa scvidctl.c videoio.c videoio.h syscons.c syscons.h src/sys/alpha/conf files.alpha src/sys/al Message-ID: <xzp7lz2v15n.fsf@hrotti.ifi.uio.no> In-Reply-To: Mikael Karpberg's message of "Thu, 17 Sep 1998 23:39:06 %2B0200 (CEST)" References: <199809172139.XAA07834@ocean.campus.luth.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Mikael Karpberg <karpen@ocean.campus.luth.se> writes: > According to Dag-Erling Coïdan Smørgrav: > > I agree that "flicker countermeasures" should be the default, but > > please leave in a knob for turning them off when they're not needed. > Exactly WHAT is it that makes the option needed at all? I mean the code works > just fine with no-flicker... Why would you want the extra code that is turned > off then you run in no-flicker? What does it do, since it's not needed? I think you misunderstand. The issue is: certain video chipsets react badly to font changes outside the vertical retrace period. Using moused(8) on these chipsets is unbearable without the no-flicker code. The problem is that the no-flicker code slows things down a tad. Not much, but enough that you notice it if there's a lot of mouse activity. So those of us who don't have that problem may want to turn it off, unless we're always running X since it only affects text mode. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzp7lz2v15n.fsf>