From owner-freebsd-current@FreeBSD.ORG Wed Feb 9 22:18:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 514F716A4CE for ; Wed, 9 Feb 2005 22:18:18 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00BAC43D39 for ; Wed, 9 Feb 2005 22:18:18 +0000 (GMT) (envelope-from nsouch@free.fr) Received: from smtp (62-240-249-21.adsl.freesurf.fr [62.240.249.21]) by fidel.freesurf.fr (Postfix) with SMTP id E44262A6DE1 for ; Wed, 9 Feb 2005 23:18:15 +0100 (CET) Received: (qmail 10815 invoked by uid 1000); 9 Feb 2005 22:17:40 -0000 Date: Wed, 9 Feb 2005 23:17:40 +0100 From: Nicolas Souchu To: Martin Message-ID: <20050209221740.GA10794@breizh> References: <20050208034855.D211E43D45@mx1.FreeBSD.org> <20050208040642.GA37528@xor.obsecurity.org> <1107848499.815.30.camel@klotz.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1107848499.815.30.camel@klotz.local> User-Agent: Mutt/1.5.6+20040907i X-Mailman-Approved-At: Thu, 10 Feb 2005 13:07:39 +0000 cc: FreeBSD Current cc: Kris Kennaway Subject: Re: Yet another sysinstall thread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 22:18:18 -0000 On Tue, Feb 08, 2005 at 08:41:39AM +0100, Martin wrote: > Am Montag, den 07.02.2005, 20:06 -0800 schrieb Kris Kennaway: > > > Fine, yeah, sysinstall sucks, but writing emails proposing > > specifications for how someone else should implement a replacement > > isn't going to get that job done. Thousands of words have been > > written on that topic over the years, but precious little code. > > I've been trying to port one of my framebuffer-based linux applications, > but I ran into problem with VESA-support on the terminal (inconsistent? > incomplete?) and after even the simpliest VGA-based (320x200) apps > failed to execute leaving me hanging in graphics mode and panic()ing, > I gave up. This was my experience with libvgl last year. > > When I wrote to this list last year, someone suggested to take a look > at KGI4BSD. That's of course nice, but to start programming something, > it would be nice to have the feeling that you have everything you need You should rather rely on GGI (http://www.ggi-project.org) It is very versatile and will allow you to output on vgl(4) or KGI4BSD as you wish. It gives graphic routines and generic framebuffer access. > in the base distribution. And btw, I don't see KGI4BSD supporting VESA > which I would prefer in the first step, because every VGA-card has got VESA is fully supported. It is the most I use here. > this interface and you don't need acceleration when developing simple > applications. KGI4BSD seems to support Matrox- and ATI-only cards > which I don't have here. I'm waiting for KGI4BSD to extend the driver > support and to merge the code into -CURRENT. The people have a good > idea there, but the project is moving slowly. Unfortunatelly, I Indeed the project is slow :( > cannot help with kernel development, because of lack of experience. > It would be nice to see more effort and more developers working at > this project. > > It is a piece of work to write a small widget toolkit and when you > you run into trouble with basic things, it is no fun anymore. GGI is your friend ;) Nicholas