From owner-freebsd-hackers Wed May 2 12:29:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.guildsoftware.com (guild.guildsoftware.com [207.67.51.35]) by hub.freebsd.org (Postfix) with ESMTP id C198837B422 for ; Wed, 2 May 2001 12:29:34 -0700 (PDT) (envelope-from andude@guild.guildsoftware.com) Received: (from andude@localhost) by guild.guildsoftware.com (8.9.3/8.9.3) id OAA26582; Wed, 2 May 2001 14:29:31 -0500 Date: Wed, 2 May 2001 14:29:31 -0500 From: Andy Sloane To: Torbjorn Kristoffersen Cc: freebsd-hackers@FreeBSD.org Subject: Re: new syscons screensaver Message-ID: <20010502142931.D19547@guild.guildsoftware.com> References: <20010502021600.A34130@cec.wustl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Torbjorn Kristoffersen on Wed, May 02, 2001 at 08:42:01PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 02, 2001 at 08:42:01PM +0200, Torbjorn Kristoffersen wrote: > What about implementing some code from green_saver into his saver to > enable DPMS support? And have a sysctl value to set the delay after the > green saver will begin :) Maybe there's a better way, to let his > beastie_saver.ko load green_saver.ko (and possibly unload itself) after a > specified delay? Actually, looking at the code, it would be very easy to do so. The only issue is how does one set the delay... sysctl would work, I suppose, and one could introduce a general sysctl variable for screensaver standby mode timeout or something, and then all the other screensavers could be updated. Or it could be handled by the underlying screensaver driver, which seems to make more sense to me, although I don't know much about it. (i.e. after the timeout expires, stop calling the scrn_saver_t "saver" function and perform a blank_display(V_DISPLAY_STAND_BY)...) -Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message