Keith Whitwell wrote:
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->BaseLeve
Keith Whitwell wrote:
Alan Hourihane wrote:
What I'd really like to be able to do now is build the dri drivers
directly out of the Mesa tree.
Definately. Slate that up for 6.1, I'll certainly work on that issue.
It's not too hard - I had it working on the embedded branch a while ago.
In gen
Dave Jones gave me this list address. I'm having problems with GL apps
crashing with "illegal instruction". This used to work fine until I changed
motherboards. See forwarded message for more information
- Forwarded message from Wakko Warner <[EMAIL PROTECTED]> -
Date: Sat, 24 Jan 20
Based on Alex Deucher's recent request to test the Savage driver he and Felix have
been working on, I recently pulled the savage-2-0-0-branch and compiled the driver for
testing.
My configuration is Fedora Core 1, AMD Athlon 2200, 512 MB, ProsavageDDR in a Shuttle
SK41G.
My results have been g
after the xscreenesaver flying toasters froze on my desktop, i found this
in my /var/log/messages:
///
Jan 24 11:31:44 willy_wonka /kernel: error: [drm:radeon_lock_take]
*ERROR* 4 holds heavyweight lock
Jan 24 11:31:49 willy_wonka /kernel: er
Michel Dänzer <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2004-01-23 at 00:49, Andrew Morton wrote:
> > Are any of the DRI developers watching the drivers_video-dri account
> > on kernel bugzilla?
>
> It'd probably be a good idea to direct those bugs to this list. I guess
> I need to create an accoun
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=788
[EMAIL PROTECTED] changed:
What|Removed |Added
--
The message contains Unicode characters and has been sent as a binary attachment.
<>
Hi,
after a CVS upgrade last night I got two some assertions in the radeon
driver. One happened when exiting from glxgears in radeonDeleteTexture.
Commenting out the assert statement helped.
I got the other one in Torcs when entering the game. Here's a complete
backtrace.
torcs: radeon_state.c:7
http://dri.sourceforge.net/cgi-bin/moin.cgi/Download has new
instructions for getting the new nightly snapshots that are built from
freedesktop.org, now that we got cron working properly. The scripts are
in /home/projects/dri/snapshots, and should be writable by other project
members. The cronjob
On Fri, 2004-01-23 at 19:30, Andrew Morton wrote:
> Michel DÃnzer <[EMAIL PROTECTED]> wrote:
> >
> > On Fri, 2004-01-23 at 00:49, Andrew Morton wrote:
> > > Are any of the DRI developers watching the drivers_video-dri account
> > > on kernel bugzilla?
> >
> > It'd probably be a good idea to dire
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> Are any of the DRI developers watching the drivers_video-dri account
> on kernel bugzilla? bugme.kernel.org.
>
>
>
> Begin forwarded message:
>
> Date: Thu, 22 Jan 2004 13:28:22 -0800
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject
Based on Alex Deucher's recent request to test the Savage driver he and
Felix have been working on, I recently pulled the savage-2-0-0-branch
and compiled the driver for testing.
My configuration is Fedora Core 1, AMD Athlon 2200, 512 MB, ProsavageDDR
in a Shuttle SK41G.
My results have been g
Alan Hourihane wrote:
Log message:
restore backwards compatibility
Modified files:
xc/xc/lib/GL/glx/:
glxclient.h
Was there an actual breakage? The __GLXscreenConfigsRec isn't supposed
to be used by anything outside libGL. The location of driScreen
shouldn't matter as the driv
14 matches
Mail list logo
