Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple programs or tutorials.
Rune Petersen
On Thu, 27 Jan 2005, Rune Petersen wrote:
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple programs or tutorials.
Try NeHe
Hi,
I have some questions about r200 depth tiling. Generally I'm also
interested in r100 tiling too, but currently i work on r200.
First of all in functions r200_mba_z16|32 from r200_span.c frontPitch
offset is used. Is it intentional or just because depthOffset is also
the same? Maybe it should
On Thu, 27 Jan 2005 19:12:23 +0100, Johannes Berg
[EMAIL PROTECTED] wrote:
Hi,
So I've been scouring the net and the mailing list archives without
finding anything - so I'll just ask:
It seems the r300 code isn't very far yet, and the web-site states that
the Radeon 9700 code hasn't been
Indeed, it's our driver that disables the DRI if Composite is enabled,
not the DRI in general. I expect that to stay the same until the two are
properly integrated with each other (but it's not my decision to make).
If some could point us to the code in the driver which disable DRI when
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=2393
--- Additional Comments From [EMAIL PROTECTED] 2005-01-27 02:37 ---
On Fri, 28 Jan 2005 09:51:25 +0100, Jacek Rosik [EMAIL PROTECTED] wrote:
Hi,
I have some questions about r200 depth tiling. Generally I'm also
interested in r100 tiling too, but currently i work on r200.
First of all in functions r200_mba_z16|32 from r200_span.c frontPitch
offset is used.
I compiled DRI CVS for Savage (X.org, Mesa and DRM stuff) with instructions from
dri.sf.net and install it, DRI isn't working. I get this failure (from dmesg):
mtrr: 0x9000,0x200 overlaps existing 0x9000,0x20
mtrr: no more MTRRs available
[drm:drm_unlock] *ERROR* Process 6930
Jacek Rosik wrote:
Hi,
I have some questions about r200 depth tiling. Generally I'm also
interested in r100 tiling too, but currently i work on r200.
First of all in functions r200_mba_z16|32 from r200_span.c frontPitch
offset is used. Is it intentional or just because depthOffset is
also the
Vladimir Dergachev wrote:
On Thu, 27 Jan 2005, Rune Petersen wrote:
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple
Roland Scheidegger wrote:
I don't quite follow third line before last? Can someone enlighten me?
You mean the pitch 0x20 stuff? Yeah, looks strange.
Looking at it, it seems like it ensures that each block line starts
with alternating 2KB addresses (i.e. that 11th-bit). So y 0-15 will
have set
I've noticed fglrx advertises this for the r200, and doom 3 wants it...
So after I manage to beat fragment_shader into shape, going to have a look
at how to get ARB_vp working.. r300 guys you have something going on this
already?
Dave.
--
David Airlie, Software Engineer
12 matches
Mail list logo