Menu
▾
▴
mesa3d-dev
|
From: <dem...@ne...> - 2009-04-11 05:11:39
|
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 |
|
From: Corbin S. <mos...@gm...> - 2009-04-11 05:23:54
|
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??? 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. |
|
From: Jerome G. <gl...@fr...> - 2009-04-11 12:46:16
|
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 |
|
From: Dee S. <dem...@ne...> - 2009-04-11 13:06:46
|
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 |
|
From: Younes M. <you...@gm...> - 2009-04-11 16:04:02
|
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). |
|
From: <dem...@ne...> - 2009-04-11 19:01:41
|
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! |
|
From: Dee S. <dem...@ne...> - 2011-05-22 15:25:46
|
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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X