In driCalculateTextureFirstLastLevel, there's this bit of code:
if (tObj->MinFilter == GL_NEAREST || tObj->MinFilter == GL_LINEAR) {
/* GL_NEAREST and GL_LINEAR only care about GL_TEXTURE_BASE_LEVEL.
*/
firstLevel = lastLevel = tObj->BaseLevel;
}
else {
Does the R100 hardware support cubemapping with mipmaps
and/or hw-tcl?
greetings,
Andreas
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabi
Does switching to a VT before suspend and switching back after help any?
Dave.
On Tue, 2 Sep 2003, Robos wrote:
> Hi dear developers :)
> Thanks a lot for your efforts! Now my (newbie) question:
> my i830 dri powered xserver sometimes restarts after suspend-to-ram (loosing
> all open windows)
Hi dear developers :)
Thanks a lot for your efforts! Now my (newbie) question:
my i830 dri powered xserver sometimes restarts after suspend-to-ram (loosing
all open windows) with this error message in dmesg:
[drm:i830_wait_ring] *ERROR* space: 52232 wanted 131064
[drm:i830_wait_ring] *ERROR* locku
I have a question about the __GLcontextModesRec structure in glcore.h.
Is it safe to extend that structure? I'd like to extend it to have the
additional fields that are in __GLXFBConfigRec (from DRI's
include/GL/glxint.h). If that were done, I could remove
__GLXFBConfigRec entirely.
However,
Ian Romanick wrote:
Jacek Blizinski wrote:
Which package do I use for the new 855GM, or is it not yet supported?
Thanks a lot!
You *should* be able to use the i830 driver. AFAIK, the
i830M/i845G/i845GE/i855GM/i865G all use the same graphics core, so the
3D driver should just work.
Ian is cor
Which package do I use for the new 855GM, or is it not yet supported? Thanks a
lot!
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and e
Jacek Blizinski wrote:
Which package do I use for the new 855GM, or is it not yet supported? Thanks a
lot!
You *should* be able to use the i830 driver. AFAIK, the
i830M/i845G/i845GE/i855GM/i865G all use the same graphics core, so the
3D driver should just work.
-
the code S3/VIA released was against xfree86 4.2.0. several people
have built the source against 4.2.0. check tim roberts' savage mailing
list archive for instructions
(http://www.probo.com/mailman/listinfo/savage40 ). I don't think the
initial driver drop enabled hw acceleration on savage mx/i
Hi dear Developers,
i have a simple question regarding the savage DRI driver, which doesn't seem
to be included in official releases yet.
Do i get HW acceleration if I compile from 4.3.0 CVS?
Is there any closer information (link, maling list) regarding its status?
Who is the developer in charg
Hi!
i would like to know about the nwn + r200 texture flickering...is it a
dri driver problem and if so will it be fixed sooner or later?
i play with R200_NO_TCL=1 now but thats not very nice! :-)
Or...is it a nwn linux-client problem?
Thank you very much, i love your work!
Jan
--
kisa is simpl
Vanson Wu wrote:
> Hi All,
>
> we are trying to setup up multi-screen in my system. as we knows, the DRI
> module not support Xinerama yet.
> it will be software rendering, but when i running glxgears. no matter we use
> dual-adapter system or dual-head system.
> The second screen always can't dis
Hi All,
we are trying to setup up multi-screen in my system. as we knows, the DRI
module not support Xinerama yet.
it will be software rendering, but when i running glxgears. no matter we use
dual-adapter system or dual-head system.
The second screen always can't display glxgears image? How does i
Dave Airlie wrote:
I've noticed the i830 drivers have a unified memory allocation scheme for
2d and 3d, is there any reason this couldnt be used on the i810?
Is there any major reasons the i830 driver couldn't be usd on the i810
with the functionality it doesn't need turned off?
I'm just wondering
I've noticed the i830 drivers have a unified memory allocation scheme for
2d and 3d, is there any reason this couldnt be used on the i810?
Is there any major reasons the i830 driver couldn't be usd on the i810
with the functionality it doesn't need turned off?
I'm just wondering the i810/i830 dr
I'm wading through DRM context switches at the kernel level now.
I've gotten lost a bit -- I'm missing a chunk o stuff at the
(*) point.
User wants a "context switch" to happen.
Calls ioctl(DRM_IOCTL_SWITCH_CTX)
Kernel goes into DRM(context_switch)
Sets an internal "current context" Variable
Philip Brown wrote:
I've been reading
http://dri.sourceforge.net/doc/hardware_locking_low_level.html
and the code, obviously... so I've seen references to the "lightweight"
lock. ButI have yet to figure out why there is one.
The url document mentions that one supposedly exists, and that
"the lig
Philip Brown wrote:
I've been reading
http://dri.sourceforge.net/doc/hardware_locking_low_level.html
and the code, obviously... so I've seen references to the "lightweight"
lock. ButI have yet to figure out why there is one.
The url document mentions that one supposedly exists, and that
"the lig
I've been reading
http://dri.sourceforge.net/doc/hardware_locking_low_level.html
and the code, obviously... so I've seen references to the "lightweight"
lock. ButI have yet to figure out why there is one.
The url document mentions that one supposedly exists, and that
"the lightweight lock will no
my patch and the tweaked multiarb test programm.
the mga texture blending units:
clock | unit1 | unit2
cl1:t1*t2
cl2:t2*t3t1*t2
cl3: t2*t3
so unit2 should use the previous stage
at the third clock and not at the second.
(TD0_color_arg2mul_alpha2 and TD0_color_blend_e
Keith Whitwell wrote:
> but also, people have put some work into looking at GL_DECAL on mga - and
> concluded that it isn't possible to do correctly. Maybe a 2-stage process can
> simulate single-texture blend, but in general it doesn't look possible.
>
i got it working once.. ill dig it up.
-
Hi there,
I'm really disappointed about this patch story, not because it hasn't
been applied yet (I've notive that yesterday too), but because I was
indirectly told why, exactly 7 months later. If I knew, it would have
been really easy to change my patch to make it conform to the DRI
patching ru
Lawrence Gold wrote:
>
> Hi,
>
> Back in June 2001, Karl Lessard posted the following patch to the mailing
> list:
>
> http://www.geocrawler.com/lists/3/SourceForge/680/0/5955984/
>
> Are there any plans to incorporate this? I perused the latest CVS sources
> and wasn't able to find t
Hi,
Back in June 2001, Karl Lessard posted the following patch to the mailing
list:
http://www.geocrawler.com/lists/3/SourceForge/680/0/5955984/
Are there any plans to incorporate this? I perused the latest CVS sources
and wasn't able to find this in there.
Thanks!
___
Hello.
I'm interesting in writing drivers for new hardware and helping DRI
project with anything I can. How can I get started?
-Igor
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
[EMAIL PROTECTED] wrote:
>Can I compile the files in a driver directory alone, without having to do
>the whole DRI or X11 tree ? Then grab the driver_dri.so file and throw
>it in the modules directory and restart X11 for it to take effect ?
>
>This assumes that the only changes are within
Can I compile the files in a driver directory alone, without having to do
the whole DRI or X11 tree ? Then grab the driver_dri.so file and throw
it in the modules directory and restart X11 for it to take effect ?
This assumes that the only changes are within the driver directory, and
not
Hello
I have some problems with DRI on my computer
for quite a while already.
(http://www.xfree86.org/pipermail/xpert/2001-May/008040.html).
In particular I can crash my server by using UseCCEFor2D option
and things are horribly slow (not useable), though glxinfo says that
I have DRI.
XFree86 t
On Wed, Apr 04, 2001 at 02:47:09PM -0500, [EMAIL PROTECTED] wrote:
>
> Thanks for the quick response Alan,
>
No problem.
> PS. would you know if there's anything funky i need to do to get the kernel
> DRM module going? I didn't see it being spat out of the main Makefile, even
> though there
Thanks for the quick response Alan,
>SiS themselves dropped us the code quite some time ago and have not
>really updated the driver since the initial drop.
aha! that explains the fact that i haven't seen word about it on the lists..
>None of the active DRI developers have access to such c
On Wed, Apr 04, 2001 at 01:44:27PM -0500, [EMAIL PROTECTED] wrote:
>
> I _did_ see (unless i was up waaay too late again) a SiS DRM driver in the
> last DRI code I checked out, and also the corresponding SiS driver in the
> X tree ...
> I briefly looked inside and it said that it supports the S
I _did_ see (unless i was up waaay too late again) a SiS DRM driver in the
last DRI code I checked out, and also the corresponding SiS driver in the
X tree ...
I briefly looked inside and it said that it supports the SiS630/540 and
a couple other models...
Did i see things right? And why d
32 matches
Mail list logo
