Sorry folks, I attached the wrong file. This is the second time in a
week. I have to be more careful. Now the correct program.
Am Do, den 16.12.2004 schrieb Felix Kühling um 1:11:
Hi,
I noticed some strange rendering artifacts with the Savage that are
caused by very large texture coordinates
Felix Kühling [EMAIL PROTECTED] writes:
Sorry folks, I attached the wrong file. This is the second time in a
week. I have to be more careful. Now the correct program.
Here's what I get with my radeon 7500 with the correct program :
http://homes.kataplop.net/~dkm/texturetest2.png
Hope it can
Sorry folks, I attached the wrong file. This is the second time in a
week. I have to be more careful. Now the correct program.
You're simply working too hard :-) Here you go:
http://kempniu.no-ip.com/files/teximage.jpg (Savage/IX 8 MB)
Best regards,
Michal Kepien
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2092
Summary: _radeon_texrect_stage looks broken
Product: Mesa
SM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM dri_util.c
In file included from dri_util.c:52:
dri_util.h:563: Warnung: redundant redeclaration of `glXGetProcAddress' in
same scope
/opt/Mesa/include/GL/glx.h:295: Warnung: previous declaration of
`glXGetProcAddress'
dri_util.c:57: error:
On Thursday 16 December 2004 13:06, Alex Deucher wrote:
On Thu, 16 Dec 2004 12:35:34 -0500, Adam Jackson [EMAIL PROTECTED] wrote:
On Thursday 16 December 2004 12:20, Dieter Nützel wrote:
make[6]: Leaving directory
`/tmp/INSTALL/SOURCE/dri-trunk/xc/xc/lib/GL/mesa/drivers/dri/common'
On Thu, 16 Dec 2004 13:43:26 -0500, Adam Jackson [EMAIL PROTECTED] wrote:
On Thursday 16 December 2004 13:06, Alex Deucher wrote:
On Thu, 16 Dec 2004 12:35:34 -0500, Adam Jackson [EMAIL PROTECTED] wrote:
On Thursday 16 December 2004 12:20, Dieter Nützel wrote:
make[6]: Leaving directory
Adam Jackson wrote:
On Tuesday 14 December 2004 19:03, Bill Shannon wrote:
It's been over a month since I sent this message and I've yet to
receive a single response. If you're ignoring me on purpose,
would someone please say so? If I'm asking the wrong people,
again I'd appreciate a pointer to
On Thursday 16 December 2004 12:20, Dieter Ntzel wrote:
make[6]: Leaving directory
`/tmp/INSTALL/SOURCE/dri-trunk/xc/xc/lib/GL/mesa/drivers/dri/common'
The xc tree under /cvs/dri is archival. No new development happens there.
Don't bother using it.
That said, there are a few drivers
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=1220
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2093
--- Additional Comments From [EMAIL PROTECTED] 2004-12-16 17:32 ---
Could this be
thanks,
Now I can load radeon.ko
after modprobe i2c_via.ko
thanks,
On Mon, 2004-12-13 at 17:27 -0500, Adam Jackson wrote:
On Monday 13 December 2004 17:15, Dave Airlie wrote:
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
you need i2c support modules
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=271
--- Additional Comments From [EMAIL PROTECTED] 2004-12-13 05:14 ---
I have
It should definitely fall back to indirect rendering, just like when
there's a problem loading any of the existing 3D drivers.
Well, I have just committed the code, protected by X_R300_DRM option - if
not enabled (which is default) the DRM is not used in any way.
The option is superfluous IMHO,
On Sun, 2004-12-12 at 22:39 +0100, Stephane Marchesin wrote:
Michel Dnzer wrote:
+typedef struct drm_radeon_surface_alloc {
+ int lower;
+ int upper;
+ int flags;
+} drm_radeon_surface_alloc_t;
+
+typedef struct drm_radeon_surface_free {
+ int lower;
+}
Hi,
On Monday 13 December 2004 18:29, Kronos wrote:
Hi,
Makefile in drm/linux-core/ doesn't pass CC to linux kernel build
system. This prevents loading the modules if kernel has been compiled
with a compiler different from the default (ie. gcc).
The following patch add CC to kernel
Alan Hourihane wrote:
There's a backwards compatibility breakage with X.Org 6.8.0 and beyond
because of revision 1.3 of the file xc/include/glxint.h. So, those
that provide binary drivers that were compiled against X.Org 6.7.x or
XFree86 4.4.0 or earlier will break as well.
So, the real answer to
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=1950
[EMAIL PROTECTED] changed:
What|Removed |Added
On Sat, 11 Dec 2004, Michel [ISO-8859-1] Dänzer wrote:
On Sat, 2004-12-11 at 11:19 -0500, Vladimir Dergachev wrote:
The reason this is useful is that such trick greatly accelerates 3d on
^ 2? :)
large resolution screens as 2d
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
you need i2c support modules loaded.. modprobe the radeon driver it should
all work then...
when I try to load radeon ko .
thanks,
On Mon, 2004-12-13 at 00:11 +0100, Roland Scheidegger wrote:
Sergio
Sergio Monteiro Basto wrote:
thanks,
Now I can load radeon.ko
after modprobe i2c_via.ko
Do you have i2c-algo-bit.ko loaded (or built into your
kernel image)? That's where i2c_bit_add|del_bus are.
Check this .config symbol:
CONFIG_I2C_ALGOBIT=y
(on my system)
On Mon, 2004-12-13 at 17:27 -0500,
On Mon, Dec 13, 2004 at 11:30:07AM +, Alan Cox wrote:
Does this not break compatibility with 6.8.0/6.8.1 - that seems at least
as big a problem as the breakage from 6.7 because it will prevent anyone
stuck with a 6.8.* driver from updating to get security fixes ?
We discussed this issue on
Il Tue, Dec 14, 2004 at 11:27:14AM +0100, Nicolai Haehnle ha scritto:
--- a/drm/linux-core/Makefile 2004-10-23 14:43:44.0 +0200
+++ b/drm/linux-core/Makefile 2004-12-13 18:20:16.0 +0100
@@ -172,7 +172,7 @@
all: modules
modules: includes
- make -C $(LINUXDIR)
Hi,
Now, on FC3 testing lastest cvs I got:
radeon: Unknown symbol i2c_bit_add_bus
radeon: Unknown symbol i2c_bit_del_bus
when I try to load radeon ko .
thanks,
On Mon, 2004-12-13 at 00:11 +0100, Roland Scheidegger wrote:
Sergio Monteiro Basto wrote:
Hi Roland,
So , for hyperz patch did
On Sun, 2004-12-12 at 14:52 +0100, Stephane Marchesin wrote:
Here is my second try at the surface ioctl.
Does everything look correct ?
Looks like you've made good progress.
Index: shared/radeon_drm.h
===
RCS file:
On Wed, 15 Dec 2004 15:34:52 +0100 (CET), Thomas Hellström
[EMAIL PROTECTED] wrote:
Hi!
Is it possible to commit rights for the Mesa tree, or have someone commit
the work done in bug 1950 to port the unichrome driver to the new security
policy implemented in the Via DRM?
I won't be doing
On Tuesday 14 December 2004 05:27, Nicolai Haehnle wrote:
Hi,
On Monday 13 December 2004 18:29, Kronos wrote:
In this way calling:
CC=gcc-3.4 make
does the Right Thing
The base DRM Makefile doesn't pass the CC on either, and this may or may
not be with good reason. AFAIK kernel code
On Tuesday 14 December 2004 19:03, Bill Shannon wrote:
It's been over a month since I sent this message and I've yet to
receive a single response. If you're ignoring me on purpose,
would someone please say so? If I'm asking the wrong people,
again I'd appreciate a pointer to the right
Sounds like you are using an old CVS.
Try updating.
Alan.
On Thu, Dec 16, 2004 at 06:20:55PM +0100, Dieter Nützel wrote:
SM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM dri_util.c
In file included from dri_util.c:52:
dri_util.h:563: Warnung: redundant redeclaration of `glXGetProcAddress' in
Alex Deucher wrote:
On Thu, 16 Dec 2004 12:35:34 -0500, Adam Jackson [EMAIL PROTECTED] wrote:
On Thursday 16 December 2004 12:20, Dieter Nützel wrote:
make[6]: Leaving directory
`/tmp/INSTALL/SOURCE/dri-trunk/xc/xc/lib/GL/mesa/drivers/dri/common'
The xc tree under /cvs/dri is archival. No new
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2093
Summary: Unichrome / Mesa: Drawable changes sometimes not gets
Am Do, den 16.12.2004 schrieb Brian Paul um 16:45:
Felix Kühling wrote:
Hi,
I noticed some strange rendering artifacts with the Savage that are
caused by very large texture coordinates on GL_REPEAT'ed textures. Very
large means that it gets noticeable with texture coordinates 255 or
Felix Kühling wrote:
Am Do, den 16.12.2004 schrieb Brian Paul um 16:45:
Felix Kühling wrote:
Hi,
I noticed some strange rendering artifacts with the Savage that are
caused by very large texture coordinates on GL_REPEAT'ed textures. Very
large means that it gets noticeable with texture coordinates
33 matches
Mail list logo
