Date: Wed, 28 Jan 1998 01:42:49 +1030 From: Mike Smith <mike@smith.net.au> To: dag-erli@ifi.uio.no (Dag-Erling Coidan Sm rgrav) Cc: joelh@gnu.org, hackers@FreeBSD.ORG Subject: Re: File I/O in kernel land (was: Re: 2nd warning: 2.2.6 BETA begins in 10 days!) Message-ID: <199801271512.BAA00461@word.smith.net.au> In-Reply-To: Your message of "27 Jan 1998 13:21:31 BST." <xzp90s2umyc.fsf@hrotti.ifi.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> When I uncomment the VGA code (which was taken from splashkit), > logo_saver() is called only twice: once when the screen saver hits in, > and once when it is unloaded. The console responds to keypresses, and > I can type commands at the shell prompt, but the screen saver never > gets the message to switch back to text mode. The kernel log shows > only two messages. You're setting the UNKNOWN_MODE flag in scp->status; right at the top of scrn_timer() it bails out if that's set. There are a couple of things you can do: 1 not set the flag (that's probably a bad idea, as it's what tells syscons not to futz with anything) 2 hack scrn_timer to call you regardless (also bad, as it means that text screensavers behaviour changes) 3 establish/disestablish your own timer routine when you are activated/deactivated (bad again because the remove-saver option is hidden behind the UNKNOWN_MODE test in scrn_timer()). I would actually combine 3 above with moving the "should we stop the screensaver" test to before the UNKNOWN_MODE bailout in scrn_timer(). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801271512.BAA00461>