Date: Sun, 29 Nov 1998 18:07:37 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Bryan Liesner <bleez@netaxs.com> Cc: Bruce Evans <bde@zeta.org.au>, elias@cnetworks.net, seggers@semyam.dinoco.de, current@FreeBSD.ORG, green@unixhelp.org Subject: Re: kern_clock.c (was: video mode switching has gone south) Message-ID: <8923.912359257@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 29 Nov 1998 11:38:31 EST." <Pine.BSF.4.05.9811291122250.281-100000@gravy.kishka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>Applying the patch to ignore the 'force' flag seems to have cleared >this up. Can anything "bad" happen using this patch? Is there a better >solution in the works? For all practical puposes, "forcing the force flag", ie, always completing the entire tco_forward() reverts to previous behaviour, and I will probably make the "force" feature a sysctl in a few hours time, since as bruce said, the hardware which it fixes is rather rare, all things considered. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8923.912359257>