Date: Thu, 25 Jan 2001 19:39:09 +0100 From: Nicolas Souchu <nsouch@alcove.fr> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: hackers@FreeBSD.org Subject: Re: [RFC] New features for libvgl Message-ID: <20010125193909.G18032@wiliam.alcove-int> In-Reply-To: <3A7062C5.482DA161@FreeBSD.org>; from sobomax@FreeBSD.org on Thu, Jan 25, 2001 at 07:30:46PM %2B0200 References: <3A6C7FBF.251B4C89@FreeBSD.org> <20010124185013.G12375@ontario.alcove-int> <3A6F1B68.9AA53C0B@FreeBSD.org> <20010125121032.B17571@wiliam.alcove-int> <3A7062C5.482DA161@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 25, 2001 at 07:30:46PM +0200, Maxim Sobolev wrote: > Nicolas Souchu wrote: > > > On Wed, Jan 24, 2001 at 08:14:01PM +0200, Maxim Sobolev wrote: > > > > > > > > Isn't your list of modes redundant with the internal data structures of the > > > > VGA/VESA driver? Why do you list modes if it's not to query a specific one? > > > > > > I believe that there should be possibility to do both these things, i.e. (1) query > > > list of available modes using some filter, so the aplication/toolkit will be able to > > > select one that matches its needs, and (2) let the video driver select the best one > > > given certain constrains. For example SDL provides a possibility to at least emulate > > > mode if is not directly available from video hardware, so it need to know what the > > > alternatives are. > > > > All this is done by GGI. I agree that you may need it for SDL. > > So why not to put it into libvgl and allow any toolkit use this code? I think we should rather consider GGI or SDL has the future graphic standard in FreeBSD and rewrite VGL on top of it :) The port of GGI on top of VGL is just an intermediate step before moving everything in the kernel like KGI does. But, I hesitate a bit now with moving everything in the kernel and add the overhead of context switches. > > So, the mousehandler is called each time the mouse is moving? > > Yes, each time mouse is moving syscons driver sends a signal specified by the CONS_MOUSECTL > ioctl. What I'm proposing here is to add a knob to allow vgl-using apps to assign their own > handlers for this. > > > The SDL library is synchronous with input peripheral? > > It depends on specific driver implementation. You can make it to either query mouse position > periodically or be synchronous with input peripheral. Matter of taste ;). > > > How will you handle acceleration with SDL? > > There are not much you can do about acceleration with vgl, hovewer SDL in general contains a > provision for hardware accelerated blits. Yes, performance is a big caveat of vgl. But, it was not designed for this. As far as I could understand libvgl was rather a quick implementation. Building a true graphic library on top of it may not be a good choice. What is SDL typical backend in Linux, fb, X11? > > Ok, do you have any patches for vgl yet? I would like to take a look at it if possible. No, everything has been commited to -current after review by Soren. Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010125193909.G18032>