From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Christian_K=F6nig?= Subject: RFC: Radeon multi ring support branch Date: Sat, 29 Oct 2011 15:00:28 +0200 Message-ID: <4EABF8EC.3020701@vodafone.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from outgoing.email.vodafone.de (outgoing.email.vodafone.de [139.7.28.128]) by gabe.freedesktop.org (Postfix) with ESMTP id D46C39E85A for ; Sat, 29 Oct 2011 06:00:30 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Hello everybody, to support multiple compute rings, async DMA engines and UVD we need to teach the radeon kernel module how to sync buffers between different rings and make some changes to the command submission ioctls. Since we can't release any documentation about async DMA or UVD (yet), my current branch concentrates on getting the additional compute rings on cayman running. Unfortunately those rings have hardware bugs that can't be worked around, so they are actually not very useful in a production environment, but they should do quite well for this testing purpose. The branch can be found here: http://cgit.freedesktop.org/~deathsimple/linux/log/ Since some of the patches are quite intrusive, constantly rebaseing them could get a bit painful. So I would like to see most of the stuff included into drm-next, even if we don't make use of the new functionality right now. Comments welcome, Christian.