From: "Christian König" <deathsimple@vodafone.de>
To: dri-devel@lists.freedesktop.org
Subject: RFC: Radeon multi ring support branch
Date: Sat, 29 Oct 2011 15:00:28 +0200 [thread overview]
Message-ID: <4EABF8EC.3020701@vodafone.de> (raw)
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.
next reply other threads:[~2011-10-29 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 13:00 Christian König [this message]
2011-10-31 15:05 ` RFC: Radeon multi ring support branch Jerome Glisse
2011-11-02 10:12 ` Christian König
2011-11-02 14:24 ` Jerome Glisse
2011-11-15 19:32 ` Jerome Glisse
2011-11-15 23:19 ` Christian König
2011-11-16 0:24 ` Jerome Glisse
2011-11-17 16:24 ` Christian König
2011-11-17 16:58 ` Jerome Glisse
2011-11-18 12:19 ` Christian König
2011-11-18 14:21 ` Jerome Glisse
2011-11-18 15:41 ` Jerome Glisse
2011-11-17 20:16 ` Alex Deucher
2011-11-18 12:44 ` Alex Deucher
2011-11-18 16:34 ` Jerome Glisse
2011-11-20 21:04 ` Jerome Glisse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EABF8EC.3020701@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.