Winsys

View: New views
7 Messages — Rating Filter:   Alert me  

Winsys

by Dee Sharpe :: Rate this Message:

| View Threaded | Show Only this Message

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

------------------------------------------------------------------------------
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
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Re: Winsys

by Corbin Simpson :: Rate this Message:

| View Threaded | Show Only this Message

demetrioussharpe@... 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???

The winsys layer is still a bit on the hacky side IMO. Right now there's
drm-based winsys, and for various reasons all of them are still split
into card-specific interfaces.

But the other winsys layers are all pretty generic. xlib, egl_xlib,
g3dvl, gdi...

Unfortunately, there's still a lot of API issues to be worked out. I
really wish I could help more, sorry.

~ c.

------------------------------------------------------------------------------
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
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Re: Winsys

by Jerome Glisse-2 :: Rate this Message:

| View Threaded | Show Only this Message

On Sat, 2009-04-11 at 01:11 -0400, demetrioussharpe@... 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
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Re: Winsys

by Dee Sharpe :: Rate this Message:

| View Threaded | Show Only this Message

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 <glisse@...>  
wrote:

> On Sat, 2009-04-11 at 01:11 -0400, demetrioussharpe@...  
> 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
> Mesa3d-dev@...
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

------------------------------------------------------------------------------
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
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Re: Winsys

by Younes Manton :: Rate this Message:

| View Threaded | Show Only this Message

On Sat, Apr 11, 2009 at 9:06 AM, Dee Sharpe
<demetrioussharpe@...> 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).

------------------------------------------------------------------------------
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
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Parent Message unknown Fwd: Winsys

by Dee Sharpe :: Rate this Message:

| View Threaded | Show Only this Message

Forgot to just sent this to the Mesa mailing list!

Dee


-----Original Message-----
From: demetrioussharpe@...
To: younes.m@...
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 <younes.m@...>
To: Dee Sharpe <demetrioussharpe@...>
Cc: mesa3d-dev@... <mesa3d-dev@...>
Sent: Sat, 11 Apr 2009 11:03 am
Subject: Re: [Mesa3d-dev] Winsys

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

<demetrioussharpe@...> 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).


------------------------------------------------------------------------------
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
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

How are GLX Visuals Created???

by Dee Sharpe :: Rate this Message:

| View Threaded | Show Only this Message

Hello all,

I'm not sure that this is really the appropriate place to pose this
question; but, I was wondering how GLX Visuals are created internally.
What info does a video driver give that allows the XServer & also GLX to
configure a list of Visuals? How is this info combined & shaped into
Visuals? I'm looking specifically for functions & variables. If someone
could point me to a few files, I'd be immensely grateful!

Dee Sharpe

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@...
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev