Ok, that sounds good.? What we have right now is a very simple 2d driver API 
that basically blits bitmaps from userspace to the screen.? Our drivers have a 
duality system.? They use a kernel driver for basic access to the card, but for 
many drivers, almost everything is MMIO, so the kernel driver doesn't get 
touched much after it's opened.? I ported the *BSD AGP driver, but I haven't 
taken advantage of AGP yet, because I wasn't sure of whether I wanted to handle 
it in the kernel driver or the userland driver; since the userland API has a 
very primitive memory management system.? I don't think it's used much & the 
memory is actually managed by the windowing system.? The only thing the video 
driver actually does, in that aspect, is give the windowing system a pointer to 
the framebuffer & the rest of the memory.? Otherwise, memory is just allocated 
in system RAM.? When you say the winsys interfaces with the kernel, do you mean 
the actual kernel, or the kernel space video driver?

Dee


 


 

-----Original Message-----
From: Corbin Simpson <mostawesomed...@gmail.com>
To: demetrioussha...@netscape.net
Cc: mesa3d-...@lists.sourceforge.net; dri-devel@lists.sourceforge.net
Sent: Sun, 5 Apr 2009 6:59 pm
Subject: Re: [Mesa3d-dev] Gallium HW Drivers & DRI/DRM










demetrioussha...@netscape.net wrote:
>  Sounds good, but here's the catch, I would like to use Gallium to accelerate 
the whole windowing system.? I want our windowing system to use libGL for all 
rendering, so Gallium would basically be running on the video card with no 
windowing system standing in the way.


That's not a catch. That's what Gallium was designed to do.

You're picturing something like this, I think:

Windowing system -> OpenGL windowing system plugin -> kernel

But you can do this:

Windowing system -> Galliumized windowing system plugin -> kernel

(I'm assuming that you already have a rendering plugin system so you can
support different video cards in userspace.)

If you break down this Galliumized plugin, it would consist of:

Syllable state tracker + Syllable winsys + pipes (softpipe, i915, etc.)

So the state tracker interfaces with windowing system, the winsys
interfaces with kernel, and everything just works.

Of course, I know next to nothing about Syllable.

~ C.



 

------------------------------------------------------------------------------
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to