From owner-freebsd-hackers Tue Nov 10 13:04:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14773 for freebsd-hackers-outgoing; Tue, 10 Nov 1998 13:04:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14768 for ; Tue, 10 Nov 1998 13:04:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA00544; Tue, 10 Nov 1998 13:03:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811102103.NAA00544@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug White cc: hackers@FreeBSD.ORG Subject: Re: splashkit current status? In-reply-to: Your message of "Tue, 10 Nov 1998 12:55:48 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 13:03:02 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The topic of the splashkit came up today and I'm curious to know what it's > current status is. I see a commit to syscons in early August about it but > the only patches available otherwise are from February. And is the 2.2.x > patch any good? > > Could you shed some light, Mike? :-) I played with it again a little bit the other night. The basic problems with the splashkit as it stands for 2.2.x are that it's really limited to 320x200x8bpp or 640x480x4bpp, and it requires some quite ugly hackery to the kernel and bootblocks. These are things that I've addressed in the new bootloader and kernel infrastructure, and Kazu dealt with the ugly integration with syscons by improving the screensaver code. I'm not highly motivated to work on the splashkit further for 2.2.x systems. As it stands, I would say that a moderately competent programmer with limited knowledge of the FreeBSD kernel should be able to take the patches and merge them into -stable. Of the patches supplied with the splashkit, about half of the ones to syscons have been adopted by the mainstream. The rest are still applicable, and easily adapted. Patches for the remainder of the system should still apply with little or no help. If someone wants to take over the 2.2.x splashkit, I'd be happy to help out with the odd piece of advice. I can't see myself working on it however, as I'm really just too busy. -- \\ 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. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message