Home | Content | Search | Navigation | Indexes
 

Mailinglist Archive: radeonhd (265 mails)

< Previous Next >
Re: [radeonhd] Re: Initial Radeon R6xx/R7xx acceleration support pushed
Hi,

Am Freitag, den 02.01.2009, 19:00 +0100 schrieb Matthias Hopf:
On Dec 30, 08 10:41:43 -0500, Alex Deucher wrote:
Looks like you have an AGP card. Those aren't supported at the moment
(PCIE only). I should probably add a check to the ddx to not try and
init the drm until we have r6xx AGP support.

Alex, is this a DRM only issue? It's also possible that AGP isn't
working correctly in radeonhd, I *think* I added code for AGP, but that
has never been verified.

We now have an AGP r6xx card here, so I can eventually verify.
i don't know if it helps, but attached is a r600_demo output i created
with my hacked drm code. It looks like the memory controller gets stuck
when a command processor script is run, but still my knowledge of all of
this is very limited.

And by the way: I think i can get a HP Notebook with an radeon chipset
on Monday. I will prepare a usb drive with an working linux environment
till then and test it on any system i can get my hand on in the office,
so prepare for some results :)

Bye, Christian.

*** ./r600_demo, version b1f4330

driver "radeon" version 1.29.0
driver description "ATI Radeon"
AGPVendorID: 8086 AGPDeviceId: 1a30
BusID: "pci:0000:01:00.0"
Context 2
gart_base: 0x00c0000000
gart_buffer: 0x00c0202000
gart_tex_handle: 0xc0402000 (ret 0)
AGP base: 0xc0000000
Map Offset Size Type Handle Mtrr
0 0xc0402000 12032 KB AGP 0xc0402000 1 texture heap
1 0xc0202000 2048 KB AGP 0xc0202000 1
2 0xc0201000 4 KB AGP 0xc0201000 1
3 0xc0000000 2052 KB AGP 0xc0000000 1
4 0xe0832000 8 KB SHM 0xe0832000 none
5 0xd0000000 262144 KB FB 0xd0000000 2
6 0xe1000000 64 KB REG 0xe1000000 none
Buffers:
0: index = 15, size = 65536
1: index = 16, size = 65536
2: index = 17, size = 65536
Mapping buffers:
idx size used address
0 65536 0 0xa6eff000
1 65536 0 0xa6f0f000
2 65536 0 0xa6f1f000
3 65536 0 0xa6f2f000
4 65536 0 0xa6f3f000
5 65536 0 0xa6f4f000
6 65536 0 0xa6f5f000
7 65536 0 0xa6f6f000
8 65536 0 0xa6f7f000
9 65536 0 0xa6f8f000
10 65536 0 0xa6f9f000
11 65536 0 0xa6faf000
12 65536 0 0xa6fbf000
13 65536 0 0xa6fcf000
14 65536 0 0xa6fdf000
15 65536 0 0xa6fef000 INDIRECT
16 65536 0 0xa6fff000 VERTICES cpu 0xa6fff000 gpu 0x00c0302000
17 65536 0 0xa700f000 TEXTURE cpu 0xa700f000 gpu 0x00c0312000
18 65536 0 0xa701f000
19 65536 0 0xa702f000
20 65536 0 0xa703f000
21 65536 0 0xa704f000
22 65536 0 0xa705f000
23 65536 0 0xa706f000
24 65536 0 0xa707f000
25 65536 0 0xa708f000
26 65536 0 0xa709f000
27 65536 0 0xa70af000
28 65536 0 0xa70bf000
29 65536 0 0xa70cf000
30 65536 0 0xa70df000
31 65536 0 0xa70ef000
command buffer: cpu 0xa6fef000 size 10000
ring buffer: cpu (nil) gpu, 0x00c0000000
indirect buffer: cpu 0xa6fef000 size 10000
VendorID: 1002 DeviceID: 9587
Chipset: RV630

display_width=1280
display gpu: 0xd0008000
framebuffer cpu 0xa710f000, gpu 0x00d0000000

fb: gpu 0x00d0000000, cpu 0xa710f000
display: gpu 0x00d0008000, cpu 0xa7117000 (1280x1280) @1280
color RT: gpu 0x00d0008000 (1280x480)
depth: gpu 0x00d0279000 (1280x480)
gart: gpu 0x00c0000000, cpu (nil)
gart bufs:gpu 0x00c0202000, cpu 0xa6eff000
buf vtx: gpu 0x00c0302000, cpu 0xa6fff000
buf tex: gpu 0x00c0312000, cpu 0xa700f000
ring: gpu 0x00c0000000, cpu (nil)
garttex: gpu 0x00c0402000, cpu 0xb7310000

Tests:

PACK0: init: set correctly after 0 loops: 0xdeadbeef
***** CP: scratch: still not set after 1000000 loops: 0xdeadbeef, should be
0xcafebabe
***** FAILED


* Current GPU state

CP Read Ptr: 0x0052 CP Write Ptr: 0x0052
MEQ Read Ptr: 0x0000 MEQ Write Ptr: 0x0000
ROQ Read Ptr: 0x0000 ROQ Write Ptr: 0x0052
ROQ IB1 Read Ptr: 0x00b0 ROQ IB1 Write Ptr: 0x00b0
CMDFIFO_AVAIL (0-16): 16
ME STATUS: 0xcc3ecc49
GRBM_STATUS*:
GRBM_STATUS__CP_BUSY: Command Processor is busy
GUI_ACTIVE : Graphics Pipe is busy. This includes whether the CP
and GRBM also have transactions
SRBM_STATUS:
CP_STAT:
CSF_RING_BUSY : The Ring fetcher still has command buffer data to
fetch or the PFP still has data left to process from the reorder queue
CSF_BUSY : The input FIFOs have command buffers to be fetched,
or one or more of the fetchers are busy, or the arbiter has a request to send
to the MIU
MIU_RDREQ_BUSY : The read path logic inside the MIU is busy
CP_STAT__CP_BUSY : Any block in the CP is busy
CP_BUSY_STAT:
OUTSTANDING_READ_TAGS: The MIU is waiting for read request data to be
returned from the MC
CP_INT_STATUS:
CP_STALLED_STAT*:
VGT_CNTL_STATUS:
Vertex + Texture:
Various:
Read Errors:
* SRBM READ ERROR indicated:
Target Adr 0x0044 by HI/BIF


* CP test: PACK0 scratch reg

flushing indirect buffer 15 with 16 dwords:
00002147 cafebabe 80000000 80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000 80000000

* Current GPU state

CP Read Ptr: 0x0052 CP Write Ptr: 0x0062
MEQ Read Ptr: 0x0000 MEQ Write Ptr: 0x0000
ROQ Read Ptr: 0x0000 ROQ Write Ptr: 0x0052
ROQ IB1 Read Ptr: 0x00b0 ROQ IB1 Write Ptr: 0x00b0
CMDFIFO_AVAIL (0-16): 16
ME STATUS: 0x963fcf79
GRBM_STATUS*:
GRBM_STATUS__CP_BUSY: Command Processor is busy
GUI_ACTIVE : Graphics Pipe is busy. This includes whether the CP
and GRBM also have transactions
SRBM_STATUS:
CP_STAT:
CSF_RING_BUSY : The Ring fetcher still has command buffer data to
fetch or the PFP still has data left to process from the reorder queue
CSF_BUSY : The input FIFOs have command buffers to be fetched,
or one or more of the fetchers are busy, or the arbiter has a request to send
to the MIU
MIU_RDREQ_BUSY : The read path logic inside the MIU is busy
CP_STAT__CP_BUSY : Any block in the CP is busy
CP_BUSY_STAT:
RING_FETCHING_DATA : There is still data to be fetched from the Ring Buffer
OUTSTANDING_READ_TAGS: The MIU is waiting for read request data to be
returned from the MC
CP_INT_STATUS:
CP_STALLED_STAT*:
VGT_CNTL_STATUS:
Vertex + Texture:
Various:
Read Errors:
* SRBM READ ERROR indicated:
Target Adr 0x0044 by HI/BIF

< Previous Next >
References