[Mesa3d-dev] Fwd: Winsys

[<dem...@ne...>]

 Forgot to just sent this to the Mesa mailing list!

Dee


 


 

-----Original Message-----
From: dem...@ne...
To: you...@gm...
Sent: Sat, 11 Apr 2009 1:44 pm
Subject: Re: [Mesa3d-dev] Winsys











 Ok, now I have a better understanding of it all.? This means that I have to port the winsys driver to the Syllable appserver driver API.? Also, I'll have to port the other hw winsys drivers to the same API if I want acceleration with those chipsets.? This isn't much different than if I were porting a normal video driver to Syllable.? Doing softpipe first should give me what I need to know in order to port the others.? Thanks!



Dee





 





 



-----Original Message-----

From: Younes Manton <you...@gm...>

To: Dee Sharpe <dem...@ne...>

Cc: mes...@li... <mes...@li...>

Sent: Sat, 11 Apr 2009 11:03 am

Subject: Re: [Mesa3d-dev] Winsys













On Sat, Apr 11, 2009 at 9:06 AM, Dee Sharpe

<dem...@ne...> wrote:

> So, this means I'll have to port the winsys for intel & radeon in

> addition to a generic winsys for the OS if I want to use Intel & AMD

> chipsets???



Each driver/API/OS combo needs a Winsys. Radeon/OpenGL/<Your OS>,

Intel/OpenGL/<Your OS>, etc.



It might be easier to get Softpipe/OpenGL/<Your OS> running first. You

can see what was done for Windows

(src/gallium/winsys/gdi/gdi_softpipe_winsys.c) and X

(src/gallium/winsys/xlib/xlib_softpipe.c). The Softpipe "driver"

doesn't require a lot from the Winsys, just basically some memory to

render to and a way to display it on the screen (via GDI blits, X

putimages, etc). Real hardware drivers will require more from their

Winsyses, like a way to communicate with their respective kernel

modules (and you'll need your own kernel modules if you don't have

DRM, I don't think it would be possible to do everything in the Winsys

from userspace).





 



 

Check all of your email inboxes from anywhere on the web.  Try the new Email Toolbar now!