On Wed, 13 Oct 2004 14:37:12 -0700, Ian Romanick [EMAIL PROTECTED] wrote:
Michel Dänzer wrote:
Anyway, I think we're on a tangent here, as the problem doesn't seem to
be PPC specific at all.
I dug out the Rage 128 that I have for the PC, and it works just fine.
glxgears, readpix, all of
Hi, Erdi!
I have been testing the ring-buffer quite extensively since there is an
option in the unichrome X driver to use it for 2D acceleration and for
XvMC mpeg. I and other people have had some problems with short hangs
and above all total screen confusion (sometimes recoverable) every once
On Fri, Oct 15, 2004 at 10:54:58 +0200, Tino Keitel wrote:
On Fri, Oct 15, 2004 at 00:28:20 +0200, Tino Keitel wrote:
On Thu, Oct 14, 2004 at 12:16:14 -0400, Vladimir Dergachev wrote:
On Thu, 14 Oct 2004, Tino Keitel wrote:
[...]
There is no linux-core or shared-core
Am Fr, den 15.10.2004 schrieb Vladimir Dergachev um 5:27:
On Fri, 15 Oct 2004, Felix [ISO-8859-1] Kühling wrote:
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:58:
On Fri, 15 Oct 2004 03:55:37 +0200, Felix Kühling [EMAIL PROTECTED] wrote:
I'm trying to get Shadow status working in the
Felix Kühling wrote:
Am Fr, den 15.10.2004 schrieb Vladimir Dergachev um 5:27:
On Fri, 15 Oct 2004, Felix [ISO-8859-1] Kühling wrote:
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:58:
On Fri, 15 Oct 2004 03:55:37 +0200, Felix Kühling [EMAIL PROTECTED] wrote:
I'm trying to get Shadow status working
On Mon, Oct 11, 2004 at 10:52:40AM -0400, Jon Smirl wrote:
What does dmesg say? There should be some debugging data in the log.
drm loads right? which personality is failing?
It doesn't say nothing and I found (partially) why: the dynamic lynking
is failing, so the call to drm_init(pci_driver,
Keith Whitwell wrote:
I don't know how well tested that holes code is - it's pretty awful to
look back on, certainly that code is more complex than it needs to be.
Does doom3 look right with swtcl?
as far as I can see, yes. Actually, it looks pretty awful, faces are
rendered very poorly, all
On Fri, 15 Oct 2004 15:19:41 +0100, José Fonseca
[EMAIL PROTECTED] wrote:
It doesn't say nothing and I found (partially) why: the dynamic lynking
is failing, so the call to drm_init(pci_driver, pciidlist, driver)
never reaches a single line of code there (no debug message, *nothing*).
Could it
Hi,
There is disagreement about the meaning of the CLIPSPAN _n parameter in CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat _n as
the number of pixels in the span after clipping.
depthtmp.h and stenciltmp.h treat _n as the end+1 x coordinate of the span.
This
On Fri, 15 Oct 2004 15:31:08 +0200, Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 15 Oct 2004 03:55:37 +0200, Felix Kühling [EMAIL PROTECTED] wrote:
I'm trying to get Shadow status working in the savage driver. I'd like
to put the status page into locked shared memory and tell the Savage
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=1388
--- Additional Comments From [EMAIL PROTECTED] 2004-10-15 14:15 ---
I also
Hi,
I have uploaded my changes to the r300_driver CVS. I haven't merged any
changes to the R200 driver that might apply, and I haven't merged the
drm-core changes. I will do that within the next days.
Accelerated color buffer clear and basic clipping (without GL scissors)
works, although I
On Thu, 2004-10-14 at 12:29 +0200, Thomas Hellstrm wrote:
is DRM_WRITEMEMORYBARRIER() the right way to make sure data has been
flushed to AGP memory before firing it off to the DMA engine?
I think so, assuming DRM_WRITEMEMORYBARRIER boils down to an instruction
with the LOCK prefix. This is
On Fri, 2004-10-15 at 14:55, Michel Dänzer wrote:
On Thu, 2004-10-14 at 12:29 +0200, Thomas Hellström wrote:
is DRM_WRITEMEMORYBARRIER() the right way to make sure data has been
flushed to AGP memory before firing it off to the DMA engine?
I think so, assuming DRM_WRITEMEMORYBARRIER
Andreas Stenglein wrote:
Could someone else with an R100 test?
see attached patch ( some changes to make mesa compile with gcc2.95.3 omitted)
What were those changes? Were they to avoid the SSE2 code?
In any case, your patch looks good to me. In fact, it looks almost
identical to one that I'm
Am Fr, den 15.10.2004 schrieb Keith Whitwell um 15:50:
Felix Kühling wrote:
Am Fr, den 15.10.2004 schrieb Vladimir Dergachev um 5:27:
On Fri, 15 Oct 2004, Felix [ISO-8859-1] Kühling wrote:
Am Fr, den 15.10.2004 schrieb Jon Smirl um 3:58:
On Fri, 15 Oct 2004 03:55:37 +0200, Felix
The attached patch adds a new mapping type _DRM_CONSISTENT. It works
basically like shared memory but allocates consistent memory and returns
the physical address to user space as handle. I wouldn't be surprised if
I missed something, but it works for me. I'm typing this in an X session
with the
On Sat, 16 Oct 2004 02:46:27 +0200, Felix Kühling [EMAIL PROTECTED] wrote:
The attached patch adds a new mapping type _DRM_CONSISTENT. It works
basically like shared memory but allocates consistent memory and returns
the physical address to user space as handle. I wouldn't be surprised if
I
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=1519
[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://freedesktop.org/bugzilla/show_bug.cgi?id=729
[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://freedesktop.org/bugzilla/show_bug.cgi?id=814
Bug 814 depends on bug 729, which changed state.
Bug 729 Summary: Unreal Tournament 2004
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=984
[EMAIL PROTECTED] changed:
What|Removed |Added
Hi Nicolai,
Thanks for putting your code in CVS :)
More below,
On Fri, 15 Oct 2004, Nicolai Haehnle wrote:
Hi,
Securing against lockups comes at a price. The basic problem is that there
is too little communication between what the DRM writes to the ring buffer
and what the X server
On Fri, 2004-10-15 at 15:16 -0700, Eric Anholt wrote:
On Fri, 2004-10-15 at 14:55, Michel Dnzer wrote:
On Thu, 2004-10-14 at 12:29 +0200, Thomas Hellstrm wrote:
is DRM_WRITEMEMORYBARRIER() the right way to make sure data has been
flushed to AGP memory before firing it off to the DMA
24 matches
Mail list logo
