Originally posted by DaemonFC
View Post
Originally posted by NomadDemon
View Post
In terms of roadmap it's basically the stuff we talked about at XDC recently - next generation hardware (GCN), changes to memory management, OpenCL, more work on trying to open up UVD, along with ongoing support & bug fixing.
In terms of what is working and what isn't, Trinity is basically working and the focus now is building up the GCN acceleration stack. Kernel driver for GCN has been working for a while although changes to memory management are continuing, and work is ramping up on shader compiler and 3D acceleration. We're working in a slightly different sequence from what we used on previous new generations -- command submission before display, and 3D before 2D -- in order to align better with some other projects.
A good chunk of the shader compiler work is common between GCN and OpenCL, so you can choose which of those you want to think Tom is working on. Tom is also the first contact for android-x86 issues.
It was easier to talk about this stuff when we were catching up, and working on hardware which had already been released. This "get ahead of the game and work on unreleased hardware" stuff is a bit of a pain, in the sense that there's much less we can talk about while the work is being done. We are trying to release portions of the work early wherever possible (eg the multi-ring support pushed out recently), hoping to get the revised memory management code out into the light next so that other devs can have a chance to review & comment before it goes upstream.
I guess it's fair to say that a lot of the work so far has been foundation technology which is optional on current chips but which is an essential pre-requisite for the next round of hardware support. I'm not talking about UVD here because I still don't know what the endgame is going to be, but there is a fair amount of work going on there as well.
Comment