Hi Marek,
So I was looking at some perf traces from r600g, and I see a stall on
the blitter quad vbuf, every clear will cause the CPU to block on the
mapping of the vbuf to upload the new coords. On r300g I can see this
not mattering as the immediate upload path takes care of things,
however I thi
On Mon, Nov 22, 2010 at 2:36 PM, Tilman Sauerbeck wrote:
> Mathias Fröhlich [2010-11-22 19:30]:
>
>> Attached is a patch to r600g which limits the number of compared vertex
>> elements to the amount that is actually active instead of comparing all
>> possible 32 vertex elements.
>> The patch moves
Andy Furniss wrote:
--enable-debug
make
Hmm, it's working now. I notice the tree has changed from earlier with a
merge - maybe something in that?
Testing, it seems like it's just the --enable-debug that has made the
difference between working and not.
Reverted the last commit - as it doe
Christian König wrote:
I just committed some additionally error handling, and you should add "
--enable-debug" to your configure options. Just run the following
commands:
make distclean
../configure --with-dri-drivers=r600 --enable-gallium-r600
--with-state-trackers=xorg,xorg/xvmc --enable-gall
Am Montag, den 22.11.2010, 10:57 + schrieb Andy Furniss:
> Christian König wrote:
>
> > Could you fire up gdb and give me an output of the idct structure at
> > frame 3? To do so make sure gdb is installed and then run the following
>
> Program received signal SIGSEGV, Segmentation fault.
>
Good catch. Thanks! Committed with a slight modification.
Marek
(PS: for convenience, please use git format-patch or git send-email next
time)
2010/11/22 Mathias Fröhlich
>
> Hi,
>
> Attached is a patch to r300g that avoids returning a 4 element vector in a
> static array. The patch should fix
https://bugs.freedesktop.org/show_bug.cgi?id=31844
Tom Stellard changed:
What|Removed |Added
Attachment #40484|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=31844
Summary: Yo Frankie!: tgsi_ureg.h:790:ureg_writemask: Assertion
`reg.File != TGSI_FILE_NULL' failed.
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Stat
Mathias Fröhlich [2010-11-22 19:30]:
> Attached is a patch to r600g which limits the number of compared vertex
> elements to the amount that is actually active instead of comparing all
> possible 32 vertex elements.
> The patch moves the r600_shader_update function down in my usual profile runs
Hi,
Attached is a patch to r600g which limits the number of compared vertex
elements to the amount that is actually active instead of comparing all
possible 32 vertex elements.
The patch moves the r600_shader_update function down in my usual profile runs.
Please review/apply.
Thanks
Mathias
Hi,
Attached is a patch to r300g that avoids returning a 4 element vector in a
static array. The patch should fix a potential race with multiple contexts in
multiple threads.
Please review/apply.
Thanks!
Mathias
diff --git a/src/gallium/drivers/r300/r300_emit.c b/src/gallium/drivers/r300/r30
On 11/21/2010 02:18 PM, Marek Olšák wrote:
---
src/mesa/state_tracker/st_extensions.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/mesa/state_tracker/st_extensions.c
b/src/mesa/state_tracker/st_extensions.c
index 8c3fa0e..e72caa3 100644
--- a/src/mesa/state_tra
On 11/22/2010 02:54 AM, Jose Fonseca wrote:
I have no objection with the change FWIW.
I agree that given that there is no shared compiler infrastructure for gallium
drivers exposing the right capabilities to state tracker is the good compromise.
Concerning replacing TGSI with something else, I
https://bugs.freedesktop.org/show_bug.cgi?id=31837
Brian Paul changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=31837
--- Comment #1 from Benoit Jacob 2010-11-22 07:17:42 PST
---
Created an attachment (id=40478)
View: https://bugs.freedesktop.org/attachment.cgi?id=40478
Review: https://bugs.freedesktop.org/review?bug=31837&attachment=40478
patch
I guess tha
https://bugs.freedesktop.org/show_bug.cgi?id=31837
Summary: Valgrind error due to alpha channel being left
uninitialized when sampling 24bit RGB textures
Product: Mesa
Version: 7.8
Platform: Other
OS/Version: All
St
Christian König wrote:
I didn't mention at the time as I thought it may go away when IDCT was
enabled.
That's interesting, it looks like the pointer to the vertex shader is
NULL. That would also explain the gray picture, but there is in assert
if the shader can't be created in the init function
i came back from short holiday and charged myself fully
i want to solve this problem , so chia please tell me some hints to debug .
where to debug !? options and anything needed for solving the problem .
On Wed, Nov 10, 2010 at 10:59 PM, Chia-I Wu wrote:
> On Thu, Nov 11, 2010 at 3:08 AM, Clu
Christian König wrote:
Could you fire up gdb and give me an output of the idct structure at
frame 3? To do so make sure gdb is installed and then run the following
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6bfa6d0 (LWP 2455)]
r600_bo_reference (radeon=0x8f3c5
I have no objection with the change FWIW.
I agree that given that there is no shared compiler infrastructure for gallium
drivers exposing the right capabilities to state tracker is the good compromise.
Concerning replacing TGSI with something else, I've said it before, but it
doesn't hurt re-st
20 matches
Mail list logo
