Re: X.Org DRI merge and what about new dri tree.

2004-07-31 Thread Alex Deucher
On Fri, 23 Jul 2004 09:43:34 -0700, Eric Anholt <[EMAIL PROTECTED]> wrote: > On Fri, 2004-07-23 at 01:56, Sérgio M. Basto wrote: > > On Fri, 2004-07-23 at 05:04, Eric Anholt wrote: > > > I still need to merge the development drivers > > > (mach64, savage), but my testbox is down due to a bad flopp

[Bug 958] rendering error - banding on curved surfaces

2004-07-31 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=958 --- Additional Comments From [EMAIL PROTECTED] 2004-07-31 19:07 --- BTW, this is wi

[Bug 960] rendering error - random textures used

2004-07-31 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=960 --- Additional Comments From [EMAIL PROTECTED] 2004-07-31 19:05 --- Created an atta

[Bug 960] New: rendering error - random textures used

2004-07-31 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=960 Summary: rendering error - random textures used Product: Mesa V

[Bug 958] rendering error - banding on curved surfaces

2004-07-31 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=958 --- Additional Comments From [EMAIL PROTECTED] 2004-07-31 17:42 --- Created an atta

[Bug 958] New: rendering error - banding on curved surfaces

2004-07-31 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=958 Summary: rendering error - banding on curved surfaces Product: Mesa

Re: rv250 Lockup in Celestia

2004-07-31 Thread Michel Dänzer
On Sat, 2004-07-31 at 02:56 -0400, Andrew Miklas wrote: > > I'm seeing a lockup on RV250 (M9) that I thought might be related to the other > r200 problems that have been cropping up recently. These occurred using > Debian's XFree86 server (4.3.0.dfsg.1-6) and kernel 2.6.5 and 2.6.7. What versi

Re: drm - first steps towards 64-bit correctness..

2004-07-31 Thread William Lee Irwin III
On Sat, 2004-07-31 at 02:54, Arjan van de Ven wrote: >> can you explain why u32 would be outlawed? Surely it's trivial to do a >> typedef for u32 on BSD for drm ?? On Sat, Jul 31, 2004 at 02:57:17AM -0700, Eric Anholt wrote: > If there are nice standard types (uint32_t or u_int32_t, can't remember

Re: dri/sparc64 status

2004-07-31 Thread Mike Mestnik
Yes, it is posible. However my Ultra5 only has 4MB video ram(this MUST be wrong) detected by XFree86. Also I don't know how or why but XFree86 insinsts on not EVER changing the video resolution, thought it is posible to change the number of colors and use VirtualDesktop space. So if I made sure

Re: drm - first steps towards 64-bit correctness..

2004-07-31 Thread Philipp Klaus Krause
If there are nice standard types (uint32_t or u_int32_t, can't remember which at the moment, I mentioned it in an email some time ago) out there already that linux has too, why not use those? u_int32_t is the BSD type. POSIX and C use uint32_t. Philipp Klaus Krause

Re: drm - first steps towards 64-bit correctness..

2004-07-31 Thread Dave Airlie
> > can you explain why u32 would be outlawed? Surely it's trivial to do a > > typedef for u32 on BSD for drm ?? > > If there are nice standard types (uint32_t or u_int32_t, can't remember > which at the moment, I mentioned it in an email some time ago) out there > already that linux has too, why

Re: drm - first steps towards 64-bit correctness..

2004-07-31 Thread Eric Anholt
On Sat, 2004-07-31 at 02:54, Arjan van de Ven wrote: > On Sat, 2004-07-31 at 11:32, Eric Anholt wrote: > > As long as you don't use the linux-y > > "u32"-type types, BSD should be happy with the changes. > > can you explain why u32 would be outlawed? Surely it's trivial to do a > typedef for u32 o

Re: drm - first steps towards 64-bit correctness..

2004-07-31 Thread Arjan van de Ven
On Sat, 2004-07-31 at 11:32, Eric Anholt wrote: > As long as you don't use the linux-y > "u32"-type types, BSD should be happy with the changes. can you explain why u32 would be outlawed? Surely it's trivial to do a typedef for u32 on BSD for drm ?? signature.asc Description: This is a digitally

[Bug 952] New: No DRI/DDX/DRM versions checks with old libGL<->driver interface?

2004-07-31 Thread bugzilla-daemon
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://freedesktop.org/bugzilla/show_bug.cgi?id=952 Summary: No DRI/DDX/DRM versions checks with old libGL<->driver i

Re: drm - first steps towards 64-bit correctness..

2004-07-31 Thread Eric Anholt
On Sat, 2004-07-31 at 02:13, Dave Airlie wrote: > Hi, > As a first step towards sorting getting the DRM into shape for > proper use on 32/64-bit systems, I'd like to sort out all the type > definitions in drivers/char/drm/drm.h, this file is also included in > userspace and BSD builds... >

drm - first steps towards 64-bit correctness..

2004-07-31 Thread Dave Airlie
Hi, As a first step towards sorting getting the DRM into shape for proper use on 32/64-bit systems, I'd like to sort out all the type definitions in drivers/char/drm/drm.h, this file is also included in userspace and BSD builds... After reading the thread "32/64bit issues in ioctl struct

rv250 Lockup in Celestia

2004-07-31 Thread Andrew Miklas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm seeing a lockup on RV250 (M9) that I thought might be related to the other r200 problems that have been cropping up recently. These occurred using Debian's XFree86 server (4.3.0.dfsg.1-6) and kernel 2.6.5 and 2.6.7. The issue can be repro