Sorry again. I'm feeling stupid and looking for the big hole to vanish.
Sorry guys for making noise. I messed up the trees. The previous one
was against 2.6.10. I also fixed the requested patchsplits and maintainer
address changes
tglx
Use the new lock initializers DEFINE_SPIN_LOCK and DEFINE_RW
Could you try to track down what in radeon_video.c causes this ? Just
comment out (with #if 0 .. #endif) arbitrary chunks of code until you zero
in on whatever causes the lockup.
I started with fi1236:
I found that I2C_WriteRead() in Detect_FI1236() causes the problems, the
computer doesn't loc
On Wed, 12 Jan 2005, Adam K Kirchhoff wrote:
So I've finally tested the r300_driver on my 9800. Specifically it's a:
ATI Technologies Inc Radeon R350 [Radeon 9800]
Direct Rendering is enabled when X starts up. I'll attach the output from
glxinfo. glxgears -info gives me in excess of 2000 fps.
felix,
is there a noticable performance difference with
DMA versus the non-dma version of the savage driver? i have concluded that the
DMA driver work can only be compiled and used with the linux 2.6 kernel, is this
true? I ask becuase i am stuck back on the 2.4 kernel. I also believe you
So I've finally tested the r300_driver on my 9800. Specifically it's a:
ATI Technologies Inc Radeon R350 [Radeon 9800]
Direct Rendering is enabled when X starts up. I'll attach the output
from glxinfo. glxgears -info gives me in excess of 2000 fps. Any GL
app, however, will lock up X if it ru
Vladimir Dergachev wrote:
On Wed, 12 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
Really ? Could you double check this ? It would be a big surprise if
MM I2C bus access is interfering with anything.
I just did, and yes it still dies a horrible death.
Could you try to track down wha
> Well, when I went to load the kernel module I compiled from the
> /drm directory, I get this:
>
> radeon: Unknown symbol drm_open
> radeon: Unknown symbol drm_fasync
> So what am I doing wrong this time? :-)
>
insmod drm.ko first..
Dave.
>
>
FYI,
Apparently, even though the DRM_SOURCE_PATH variable is set, it's
not getting checked. If I copy the r300_driver/drm directory to the
same directory as the Mesa source tree, the r300_dri.so library gets
built fine.
Now to test it :-)
Adam
Well, when I went to load the kernel modu
Sorry guys for making noise. I messed up the trees. The previous one
was against 2.6.10. I also fixed the requested patchsplits and maintainer
address changes
tglx
Use the new lock initializers DEFINE_SPIN_LOCK and DEFINE_RW_LOCK
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
---
drm_auth.
Adam K Kirchhoff wrote:
Jerome Glisse wrote:
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
r200_context.h:98:1: warning: this is the location of the previous
definition
r300_ioctl.c: In function `r300ClearBuffer':
r300_ioctl.c:67: error: `drm_r300_cmd_header_t' undeclared (first
use in this f
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
r200_context.h:98:1: warning: this is the location of the previous
definition
r300_ioctl.c: In function `r300ClearBuffer':
r300_ioctl.c:67: error: `drm_r300_cmd_header_t' undeclared (first
use in this function)
^^
Jerome Glisse wrote:
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
r200_context.h:98:1: warning: this is the location of the previous
definition
r300_ioctl.c: In function `r300ClearBuffer':
r300_ioctl.c:67: error: `drm_r300_cmd_header_t' undeclared (first
use in this function)
Vladimir Dergachev wrote:
r200_context.h:98:1: warning: this is the location of the previous
definition
r300_ioctl.c: In function `r300ClearBuffer':
r300_ioctl.c:67: error: `drm_r300_cmd_header_t' undeclared (first use
in this function)
^^
Know wha
Keith Conger wrote:
Hi,
Is there any difference at all ? What about texture programs like NeHe
lesson 06 ?
Nope, still draws below the window. :(
Thanks,
I think i found somethings that might help. Unfortunetly i am away
for my study. But i will try this friday or saturday. Anyway Keith
On Wed, 12 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
Really ? Could you double check this ? It would be a big surprise if MM I2C
bus access is interfering with anything.
I just did, and yes it still dies a horrible death.
Could you try to track down what in radeon_video.c causes t
Vladimir Dergachev wrote:
On Wed, 12 Jan 2005, Rune Petersen wrote:
Hi,
I've managed to test r300_demo on my Radeon x800XT JK (0x4a4b).
I needed the latest driver & DRM (r300_driver) from CVS and disable the
modules "fi1236" and "msp3430".
Really ? Could you double check this ? It would be a big
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=2266
--- Additional Comments From [EMAIL PROTECTED] 2005-01-12 07:25 ---
Sounds like a
Vladimir Dergachev wrote:
On Wed, 12 Jan 2005, Rune Petersen wrote:
Hi,
I've managed to test r300_demo on my Radeon x800XT JK (0x4a4b).
I needed the latest driver & DRM (r300_driver) from CVS and disable the
modules "fi1236" and "msp3430".
Really ? Could you double check this ? It would be a big
18 matches
Mail list logo
