Re: rs480 + r300 driver fun..
Dave,
So I tested the (git from last night 5/10) the latest code
(x+mesa+drm) on my RS480
In general, things are MUCH better, but I was running through the
sample programs in Mesa, and I found some remaining issues. I ran the
tests on fglrx, took some screenshots, and compared them to the R300
results.
I've included the details below, but is bugzilla the best place to put
this info?
Cheers,
--Phil
I ran some of the Mesa samples in: '/progs/samples'
Visually Identical:
accum, blendeq, depth, star, stencil
Minor Problems:
line:
R300 is not pixel identical to fglrx, but they generally look the same.
nurb:
R300 is not pixel identical to fglrx, but they generally look the same.
olympic:
R300 is not pixel identical to fglrx, but they generally look the same.
bitmap1:
fgrlx seems broken.. 'GL' is not shown in the middle.
tri:
R300 is not pixel identical to fglrx, but they generally look the same.
I did notice that in the R300 version, the color gradient inside box
starts a line below the fglrx version.
I did get this warning:
*WARN_ONCE*
File r300_render.c function r300Fallback line 494
Software fallback:ctx-Line.StippleFlag
***
Major Problems:
logo:
It appears as if the clip plane is completely different, but the
basic geomtery is the same.
point:
On the R300 version, The crosshairs is one pixel lower.
prim:
On the R300 version, The openGL crossharis is one pixel lower
fogtest:
On the R300 version, the end of the tube is not red.
(In the source, the only thing that is red is:
static float back_mat_diffuse[] = {1.0, 0.0, 0.0, 1.0};
glMaterialfv(GL_BACK, GL_DIFFUSE, back_mat_diffuse); )
quad:
On the R300 version, the interior of the cone is not green.
sphere:
On the R300 version, the grid lines are missing, and there is a strip
missing on the cyclinder.
wave:
On the R300 version, the checkerboard is completely missing. If I
turn off lighting, the checkerboard appears.
progs/demos:
fire:
On the R300, the trees are corrupt... They're in front of the fire.
cubmap:
On the R300, This has a wierd corruption as it spins.
terrain:
On the R300, This has triangles flying everywhere. ;-)
ipers:
On the R300, Triangles intersect the main geometry.
tunnel:
On the R300, Triangles intersect the main geometry.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
On 4/9/07, Alex Jackson awj_in_japan-at-hotmail.com |rivatv-devel| ... wrote: What has to be done now? Where can look to start hacking Mesa to support it? (I've spent all of my time so far in DRM.. (radeon_cp.c) ) Does setting tcl_mode=0 in .drirc make it work? I tested this with my Xpress 200M (128M video RAM, no system RAM). glxgears runs, and even exits cleanly when I press Esc; however, it displays an utterly corrupted window instead of the lovely spinning gears we all want to see. The displacement of vertices is most likely caused by the fact that r300 drivers swtcl path cheats and does vertex transformation in hardware. That's also why arbvpwarpmesh fails to work when sw path is active. See: http://www.egore911.de/vype/dri-log/index.php?page=dri-devel-2007-04-09.log http://www.egore911.de/vype/dri-log/index.php?page=dri-devel-2007-04-10.log I haven't seen any dumps so I can't comment on whats wrong with other attribs. Of course, it would help if I'd have some hardware to work with. -- Aapo Tahkola - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
The displacement of vertices is most likely caused by the fact that r300 drivers swtcl path cheats and does vertex transformation in hardware. That's also why arbvpwarpmesh fails to work when sw path is active. So do we need to do a completely separate swtcl path that doesn't do this? As in this hw is exactly like every other r300 but it has no vertex shader registers to program... I haven't seen any dumps so I can't comment on whats wrong with other attribs. Of course, it would help if I'd have some hardware to work with. There is a packet at http://www.skynet.ie/~airlied/radeon/r200m/myp3 which is from the mesa/progs/trivial/tri test Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
On 4/9/07, Alex Jackson awj_in_japan-at-hotmail.com |rivatv-devel| ... wrote: What has to be done now? Where can look to start hacking Mesa to support it? (I've spent all of my time so far in DRM.. (radeon_cp.c) ) Does setting tcl_mode=0 in .drirc make it work? I tested this with my Xpress 200M (128M video RAM, no system RAM). glxgears runs, and even exits cleanly when I press Esc; however, it displays an utterly corrupted window instead of the lovely spinning gears we all want to see. --Noah --AWJ-- _ Don't waste time standing in line—try shopping online. Visit Sympatico / MSN Shopping today! http://shopping.sympatico.msn.ca - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
On 4/9/07, Zoltan Boszormenyi [EMAIL PROTECTED] wrote: Hi, Dave Airlie írta: Okay the GART is working fine on the rs480 from my branch, however the Congrats! r300 driver causes a chip lockup, I've loaded fglrx and from what I can see it disables the Vertex Shaders in hw and does that bit of the pipeline in sw.. at least on the system I have... If anyone else has an xpress 200 or 200m, perhaps they could try fglrx and run a GL app and find out what the value in reg 0x2140 is, the latest version of radeontool from my git repo will do it..[1] radeontool regmatch SE_CNTL_STATUS Before running glxgears, it gives 0x. During and after: 0x0100. I see the exact same results on my Radeon 200M: ( 01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE) (prog-if 00 [VGA]) ) I have to get the latest and greatest X/ati/Mesa to try drirc hack. Cheers, --Phil - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
rs480 + r300 driver fun..
Okay the GART is working fine on the rs480 from my branch, however the r300 driver causes a chip lockup, I've loaded fglrx and from what I can see it disables the Vertex Shaders in hw and does that bit of the pipeline in sw.. at least on the system I have... If anyone else has an xpress 200 or 200m, perhaps they could try fglrx and run a GL app and find out what the value in reg 0x2140 is, the latest version of radeontool from my git repo will do it..[1] radeontool regmatch SE_CNTL_STATUS I think the bit that turns on/off the Vertex stuff is the same bit that used to turn on/off the TCL engine.. I'm not sure how we can handle this in r300, we probably need to use a swtcl path for these chips Dave. [1] git://people.freedesktop.org/~airlied/radeontool -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
Dave Airlie wrote: Okay the GART is working fine on the rs480 from my branch, however the r300 driver causes a chip lockup, I've loaded fglrx and from what I can see it disables the Vertex Shaders in hw and does that bit of the pipeline in sw.. at least on the system I have... If anyone else has an xpress 200 or 200m, perhaps they could try fglrx and run a GL app and find out what the value in reg 0x2140 is, the latest version of radeontool from my git repo will do it..[1] radeontool regmatch SE_CNTL_STATUS I think the bit that turns on/off the Vertex stuff is the same bit that used to turn on/off the TCL engine.. I'm not sure how we can handle this in r300, we probably need to use a swtcl path for these chips Dave. I thought the r300 driver could already handle tcl fallbacks. It's not news that the xpress chips don't have any hw tcl/vertex shaders, that has been known forever and is afaik officially confirmed (the screen code doesn't set the RADEON_CHIPSET_TCL bit for these chips for a reason). The same is still true for rs690, btw. Roland - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
Dave Roland, On 4/9/07, Roland Scheidegger [EMAIL PROTECTED] wrote: Dave Airlie wrote: Okay the GART is working fine on the rs480 from my branch, Congratulations on getting it to work. I've tested your DRM branch on my HP laptop with a 200M, and it works. (128M of video RAM, 0 sideport RAM.) X starts up with a nice stipple pattern, and gears hangs in the same way you described in your blog. (Damn. I was so close, I had 4 or 5 proper startups with my hacked/reverse engineered code, but I couldn't figure out how to make it happen reliably. I didn't read RADEON_IGPGART_UNK_38 before I wrote it.. Maybe that was the problem.) BTW. Base on the back traces I gathered when running kmmio, I think that the following defines should be renamed: RADEON_IGPGART_UNK_2E - RADEON_IGPGART_FLUSH RADEON_IGPGART_UNK_38 - RADEON_IGPGART_ENABLE (More details at: http://dri.freedesktop.org/wiki/Radeon200M) however the r300 driver causes a chip lockup, I've loaded fglrx and from what I can see it disables the Vertex Shaders in hw and does that bit of the pipeline in sw.. at least on the system I have... If anyone else has an xpress 200 or 200m, perhaps they could try fglrx and run a GL app and find out what the value in reg 0x2140 is, the latest version of radeontool from my git repo will do it..[1] radeontool regmatch SE_CNTL_STATUS I'll check out that register tonight. I think the bit that turns on/off the Vertex stuff is the same bit that used to turn on/off the TCL engine.. I'm not sure how we can handle this in r300, we probably need to use a swtcl path for these chips Dave. I thought the r300 driver could already handle tcl fallbacks. It's not news that the xpress chips don't have any hw tcl/vertex shaders, that has been known forever and is afaik officially confirmed (the screen code doesn't set the RADEON_CHIPSET_TCL bit for these chips for a reason). The same is still true for rs690, btw. Roland What has to be done now? Where can look to start hacking Mesa to support it? (I've spent all of my time so far in DRM.. (radeon_cp.c) ) Cheers, --Phil - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
What has to be done now? Where can look to start hacking Mesa to support it? (I've spent all of my time so far in DRM.. (radeon_cp.c) ) Does setting tcl_mode=0 in .drirc make it work? --AWJ-- _ Dont waste time standing in linetry shopping online. Visit Sympatico / MSN Shopping today! http://shopping.sympatico.msn.ca - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: rs480 + r300 driver fun..
Hi,
Dave Airlie írta:
Okay the GART is working fine on the rs480 from my branch, however the
Congrats!
r300 driver causes a chip lockup, I've loaded fglrx and from what I can
see it disables the Vertex Shaders in hw and does that bit of the pipeline
in sw.. at least on the system I have...
If anyone else has an xpress 200 or 200m, perhaps they could try fglrx and
run a GL app and find out what the value in reg 0x2140 is, the latest
version of radeontool from my git repo will do it..[1]
radeontool regmatch SE_CNTL_STATUS
Before running glxgears, it gives 0x.
During and after: 0x0100.
I had to patch your radeontool a bit to get it working,
the notebook has all sort of ATI Technology integrated
stuff, starting with a bridge. So, line 811 should read:
if(strstr(line,Radeon) strstr(line,ATI Tech)) { ...
instead of
if(strstr(line,Radeon) || strstr(line,ATI Tech)) { ...
to read the correct entry. lspci and glxinfo attached.
I think the bit that turns on/off the Vertex stuff is the same bit that
used to turn on/off the TCL engine..
I'm not sure how we can handle this in r300, we probably need to use a
swtcl path for these chips
Dave.
[1] git://people.freedesktop.org/~airlied/radeontool
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, 66MHz, medium devsel, latency 64
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 9000-9fff
Memory behind bridge: d010-d01f
Prefetchable memory behind bridge: d400-d7f0
Capabilities: access denied
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
Capabilities: access denied
00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=05, sec-latency=0
Capabilities: access denied
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
Memory at d0004000 (32-bit, non-prefetchable) [size=4K]
Capabilities: access denied
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
Memory at d0005000 (32-bit, non-prefetchable) [size=4K]
Capabilities: access denied
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
Memory at d0006000 (32-bit, non-prefetchable) [size=4K]
Capabilities: access denied
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: 66MHz, medium devsel
I/O ports at 8400 [size=16]
Memory at fed0 (32-bit, non-prefetchable) [size=1K]
Capabilities: access denied
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI (rev 80) (prog-if 82 [Master PriP])
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 16
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 8410 [size=16]
Capabilities: access denied
00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, slow devsel, latency 64, IRQ 16
Memory at d000 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
Subsystem: Acer Incorporated [ALI] Unknown device 009f
Flags: bus master, 66MHz, medium devsel, latency 0
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80) (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=06, subordinate=08, sec-latency=64
I/O behind bridge: a000-afff
Memory behind bridge: d020-d02f
Prefetchable memory behind bridge: 3000-33ff
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: access denied
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel
00:18.2 Host bridge: Advanced Micro Devices
