Subject: Re: ofb proposal
To: Michael <macallan18@earthlink.net>
From: Chris Tribo <ctribo@college.dtcc.edu>
List: port-macppc
Date: 01/30/2005 16:07:53
That seems to be the gist of things.
I've included the pcictl dump of the device FWIW
PCI configuration registers:
Common header:
0x00: 0x4c501002 0x02900086 0x030000dc 0x00002008
Vendor Name: ATI Technologies (0x1002)
Device Name: 3D Rage LT Pro (0x4c50)
Command register: 0x0086
I/O space accesses: off
Memory space accesses: on
Bus mastering: on
Special cycles: off
MWI transactions: off
Palette snooping: off
Parity error checking: off
Address/data stepping: on
System error (SERR): off
Fast back-to-back transactions: off
Status register: 0x0290
Capability List support: on
66 MHz capable: off
User Definable Features (UDF) support: off
Fast back-to-back capable: on
Data parity error detected: off
DEVSEL timing: medium (0x1)
Slave signaled Target Abort: off
Master received Target Abort: off
Master received Master Abort: off
Asserted System Error (SERR): off
Parity error detected: off
Class Name: display (0x03)
Subclass Name: VGA (0x00)
Interface: 0x00
Revision ID: 0xdc
BIST: 0x00
Header Type: 0x00 (0x00)
Latency Timer: 0x20
Cache Line Size: 0x08
Type 0 ("normal" device) header:
0x10: 0x82000000 0x00000401 0x00000000 0x00000000
0x20: 0x00000000 0x00000000 0x00000000 0x00000000
0x30: 0x00000000 0x0000005c 0x00000000 0x00080118
Base address register at 0x10
type: 32-bit nonprefetchable memory
base: 0x82000000, not sized
Base address register at 0x14
type: i/o
base: 0x00000400, not sized
Base address register at 0x18
not implemented(?)
Base address register at 0x1c
not implemented(?)
Base address register at 0x20
not implemented(?)
Base address register at 0x24
not implemented(?)
Cardbus CIS Pointer: 0x00000000
Subsystem vendor ID: 0x0000
Subsystem ID: 0x0000
Expansion ROM Base Address: 0x00000000
Capability list pointer: 0x5c
Reserved @ 0x38: 0x00000000
Maximum Latency: 0x00
Minimum Grant: 0x08
Interrupt pin: 0x01 (pin A)
Interrupt line: 0x18
Capability register at 0x5c
type: 0x01 (Power Management, rev. 1.0)
Device-dependent header:
0x40: 0x0000000c 0x00000000 0x00000000 0x00000000
0x50: 0x00105c02 0xff000001 0x00000000 0x06010001
0x60: 0x00000000 0x00000000 0x00000000 0x00000000
0x70: 0x00000000 0x00000000 0x00000000 0x00000000
0x80: 0x00000000 0x00000000 0x00000000 0x00000000
0x90: 0x00000000 0x00000000 0x00000000 0x00000000
0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
0xf0: 0x00000000 0x00000000 0x00000000 0x00000000
On Jan 30, 2005, at 3:49 PM, Michael wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
>> It occurs on the Rage Pro in the Beige G3 too, my wording of the
>> original email was just overly poor. I guess I need some "Jolt Cola
>> for those late night hacks".
>
> Ok, to get things straight:
> - - scrolling works on the G3 but not on the PowerBook
> - - both don't fill the screen completely
> - - both get the resolution right
> ?
>
> I just noticed that both show
> machfb0: 16 MB aperture at 0x82000000, 4 KB registers at 0x00000000
> I'm not sure if it really uses the registers BAR, but since the
> blitter seems to work fine on the G3 despite this I don't think it's
> something to worry about.
>
> have fun
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
>
> iQEVAwUBQf1IRMpnzkX8Yg2nAQJKBgf/XsWkDk1U0qvJ14xOnr3gMlMaOGZrGxbL
> LlH63QXlhYEan3pGZOo/vMGtquuH0/tYzLtVY/qTfhEZR/+15nMVy8navvW3cxdo
> GXY4mlKnGbYHt3DYMxASmBTtV1Tzd1NqZPPxwcKVBlJkZsfXlZYxgPMRonYbpqxl
> I8S/NrNAB7na4mzPRsIIO+Cx2Re9x68VGdlavTRVJM6G3j71jpK5r5rX/dzj3Gh6
> iePCsrOjyLR2vztWvUunvcVi1791fqrIUJX+/98sbpkHmJX+y++eM5gT6zXR+Cwf
> 5dlnxZ16l8+Y7uJR/LdgfKHcSqELCF0i7XnIilOkp7J6jnzB9/DfDg==
> =iuNS
> -----END PGP SIGNATURE-----