[RFC] radeon bo/cs API cleanup
Dave Airlie
airlied at gmail.com
Wed Dec 16 20:34:37 PST 2009
Hi,
so Michel pointed out that the libdrm_radeon API was pretty unmaintainble.
Reasons:
1. inlines in headers mean API/ABI is fixed completely.
2. All of structure internals for bo/cs are exposed.
3. RADEON_BO_TRACK changed the library API when on/off.
So I
a) removed bo tracking
b) split the cs/bo structs into public/private parts and minimised the
members, the cs_int/bo_int need to reflect the public bits.
c) left some members intact for fast paths for functions that need it
(write_dword)
3 patches attached, libdrm/ddx/mesa (no r300g bits yet) to clean the API of
all of this.
I'd like to then declare this as the stable API going forward.
Dave.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-radeon-straighten-out-the-API-insanity.patch
Type: application/mbox
Size: 50583 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-driver-ati/attachments/20091217/962796c8/attachment-0003.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-radeon-r600-use-new-api.patch
Type: application/mbox
Size: 30509 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-driver-ati/attachments/20091217/962796c8/attachment-0004.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-radeon-use-new-libdrm-api.patch
Type: application/mbox
Size: 3457 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-driver-ati/attachments/20091217/962796c8/attachment-0005.bin
More information about the xorg-driver-ati
mailing list