From owner-freebsd-current Thu Sep 17 05:57:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02666 for freebsd-current-outgoing; Thu, 17 Sep 1998 05:57:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.27.216.204.in-addr.arpa [204.216.27.226] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02650; Thu, 17 Sep 1998 05:57:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA27793; Thu, 17 Sep 1998 05:57:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: sos@FreeBSD.ORG cc: jkh@FreeBSD.ORG (Jordan K. Hubbard), current@FreeBSD.ORG Subject: Re: Flickering syscons In-reply-to: Your message of "Thu, 17 Sep 1998 14:45:25 +0200." <199809171245.OAA06482@sos.freebsd.dk> Date: Thu, 17 Sep 1998 05:57:56 -0700 Message-ID: <27789.906037076@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First I dont like the new option name DO_FLICKER ?? that sounds a bit > harsh... Perhaps, but it also describes *exactly* what it does. I welcome any new suggestions. :) > Second we need to find out WHY it flickers now in any case, somehow > it has found a new way of introducing that again :( Well, yes, that's true too. I was thinking mostly of 2.2.x with this change anyway. > I would rather that options SC_BAD_FLICKER was added to GENERIC, and > thats it, then we only need to find out why it doesn't work anymore... I don't like the idea of adding it to GENERIC since that just makes one more "mandatory option" for folks who have vga devices which do this. Again, I think the behavior of any part of the kernel should always be set to the most conservative values by default and then, if desired, provide knobs for being less conservative. It's also more in keeping with our existing option set to do this. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message