Re: [Mesa3d-dev] Winsys

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

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???

Dee Sharpe

Sent from my iPhone

On Apr 11, 2009, at 7:45 AM, Jerome Glisse <gl...@fr...>  
wrote:

> On Sat, 2009-04-11 at 01:11 -0400, dem...@ne...  
> wrote:
>> Ok, maybe I'm just completely dense.  I've asked this before with no
>> reply & I've looked through the code and the relevant pages.  I still
>> don't understand why there're driver families with their own winsys.
>> How're non-*nix platforms, that have to provide their own winsys,
>> supposed to be able to use these drivers that have their own  
>> winsys???
>>
>> Dee Sharpe
>>
>
> Gallium hw specific driver have to rely on system specific  
> communication
> link with the hw. So we will always have an hw specific part in the
> winsys this part winsys are mostly a thin layer btw the driver and
> what ever interface the lowlevel hw driver provide to talk to the hw.
>
> Cheers,
> Jerome Glisse
>
>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Mesa3d-dev mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev