[EMAIL PROTECTED] wrote:
Attached is another point size patch. Thanks for taking the time to look
through my first patch. This one uses per-primitive fallbacks as you suggested.
I originally had radeon_point_fallback calling swrast but this caused a lot of
rendering glitches (I'm fairly certain
On Wed, 2003-07-30 at 19:33, Andreas Stenglein wrote:
Am 2003.07.25 18:44:20 +0200 schrieb(en) Doug Rabson:
Oh, I meant to say also that if anyone is interested in tracking down
and fixing the r200 rendering problems, I can supply full buildable
source code to the low-level OpenGL parts of
On Thu, 2003-07-31 at 07:49, Ian Romanick wrote:
Michel Dnzer wrote:
On Wed, 2003-07-30 at 03:06, Ian Romanick wrote:
[...] do we really need to check the
device ID against R100-family IDs in the R200 driver?
Apparently, people do try to use the wrong drivers on the Mesa embedded
On Thu, 2003-07-31 at 01:02, Ian Romanick wrote:
Michel Dnzer wrote:
On Wed, 2003-07-30 at 18:26, Ian Romanick wrote:
[...] we don't want the R200 driver to expose GLX_MESA_swap_control
if there's no vblank interrupt available. Since it can't implement
the functionality, we don't want
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-31-07 09:02 ---
Make sure the agpgart module is loaded before the radeon DRM module.
--
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
--- You are receiving this
Ian Romanick wrote:
Michel Dnzer wrote:
On Wed, 2003-07-30 at 03:06, Ian Romanick wrote:
Antoine REVERSAT wrote:
I just compiled dri from the CVS for my radeon 9000 Mobbility card
(r250 lf) and it wont work as good as it is expected to (I.E : 30
fps in Quake3) The thing is when i do a
Keith Whitwell wrote:
Ian Romanick wrote:
Felix Kühling wrote:
On Wed, 30 Jul 2003 09:20:28 -0700
Ian Romanick [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
I see: C SPECIFICATION
const char * glXQueryExtensionsString( Display *dpy,
int screen
Keith Whitwell wrote:
Ian Romanick wrote:
Michel Dnzer wrote:
On Wed, 2003-07-30 at 03:06, Ian Romanick wrote:
Here's a patch that should clear some of that up, at least for the
R200-family of chips. I did change the code to include
xf86PciInfo.h. In spite of the comment there, it doesn't
It would be simple to add some checking to ensure the chipid is
recognized by the 3d driver, just hasn't been done yet.
Let me work up a patch that does this in a more generally way. The
current big switch-statement is somewhat unpleasant.Do the embedded
drivers have a header file where
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-31-07 12:19 ---
I'm not sure if this is any help, but now I get an infinite loop of:
(EE) RADEON(0): RADEONCPGetBuffer: CP GetBuffer -1020
(EE) RADEON(0): GetBuffer timed out, resetting
On Thu, 31 Jul 2003 10:12:47 -0600
Brian Paul [EMAIL PROTECTED] wrote:
Keith Whitwell wrote:
Ian Romanick wrote:
Felix Kühling wrote:
I observed that glXQueryExtensionsString calls glXInitialize first which
in turn loads and initializes the dri drivers (calls their createScreen
11 matches
Mail list logo
