Hi,
I am running Ubuntu Linux on Intel-based iMac and was wondering if I
could use the r300 driver for 3D. The card is a PCI Express ATI Radeon
Mobility X1600 (M56P). Neither the DRM nor the DRI driver recognize my
card due to missing PCI IDs. I tried adding my card to the DRM driver
like this
No.
and ATI hate you for trying :-)
see numerous archive posts about this..
Dave.
On Thu, 25 May 2006, Pekka Enberg wrote:
Hi,
I am running Ubuntu Linux on Intel-based iMac and was wondering if I
could use the r300 driver for 3D. The card is a PCI Express ATI Radeon
Mobility X1600
On Thu, 2006-05-25 at 10:31 +0100, Dave Airlie wrote:
No.
and ATI hate you for trying :-)
see numerous archive posts about this..
Aah, thanks. Well, I am stuck with this chip, so please let me know if
I can help out with reverse engineering the R500 chip as I am sure ATI
will ignore my
Hi,
I suspect that the vertex attribute changes from 2006-04-26 broke
Doom3 on r300.
Symptoms:
The rendering of Mars in the main menu screen is broken, see the
attached screenshot (the planet is supposed to look reddish, not white).
It's also flickering a lot.
Similar problems exist in game, but
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=7034
Summary: via_cmdbuf_wait timed out hw
Product: DRI
On Thu, 2006-05-25 at 01:18 -0300, Matheus Izvekov wrote:
Shouldnt you also change this line to return NULL; or return 0;?
No. The callers of drm_sysfs_create and drm_sysfs_device_add are
already checking for an error using IS_ERR, not comparing to NULL. They
won't see NULL as an error at all
Hi,
This is nice tool to play with.
Peter
http://lists.freedesktop.org/archives/xorg/2006-May/015496.html
On Thu, 2006-05-25 at 12:52 +0300, Pekka Enberg wrote:
Aah, thanks. Well, I am stuck with this chip, so please let me know if
I can help out with reverse engineering the R500 chip as I
in the r200 driver, R200_CMD_BUF_SZ is 8*1024. Is it possible to change
that? I couldn't really find a reason why it's 8k, seems like an
arbitrary choice. There is some comment in r200_ioctl.h for what that
constant is used but it doesn't explain the value. Especially since the
indirect buffer
Ok here's what I came up with, I'm going to commit it soon, though there
really are some ugly hacks in there needed to prevent lockups, (related
to setting/restoring the tcl outputs), maybe someone has any ideas?
The vertex program translation code is pretty taken from the r300
driver, which