From owner-freebsd-current Sun Nov 29 09:11:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13455 for freebsd-current-outgoing; Sun, 29 Nov 1998 09:11:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13418 for ; Sun, 29 Nov 1998 09:11:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA08925; Sun, 29 Nov 1998 18:07:49 +0100 (CET) To: Bryan Liesner cc: Bruce Evans , 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) In-reply-to: Your message of "Sun, 29 Nov 1998 11:38:31 EST." Date: Sun, 29 Nov 1998 18:07:37 +0100 Message-ID: <8923.912359257@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >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