From: sylvain.bertrand@gmail.com
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [AMDGPU][TAHITI XT] new display code
Date: Mon, 29 Jan 2018 22:35:22 +0000 [thread overview]
Message-ID: <20180129223522.GA12004@freedom> (raw)
In-Reply-To: <CADnq5_MOseUs1oHTGmsd9hXqLP5jK1rcaddtbTNwGXqgHMvBCQ@mail.gmail.com>
On Mon, Jan 29, 2018 at 03:40:34PM -0500, Alex Deucher wrote:
> On Mon, Jan 29, 2018 at 3:34 PM, <sylvain.bertrand@gmail.com> wrote:
> > As far as I can remember, not for the new features ofc, DCE programming for GCN1
> > is very similar if not mostly the same than DCE programming for GCN1.1/2 which
> > is supported by the new DC code.
> >
> > Is this planned?
>
> Right, as I said, you could definitely leverage the support for DCE8
> in DC. The blocks are very similar. At the moment, we have no plans
> to implement DC support for DCE6.
Ok.
Which git repo/branch has the most up-to-date DCE code?
Is there a fine granularity selection system for supported DCE features? That
to expose the available/implemented DCE features to userland DRM (I can test only discret
tahiti XT code paths).
I'll try to get something working.
--
Sylvain
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-29 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 17:56 [AMDGPU][TAHITI XT] new display code sylvain.bertrand
2018-01-29 18:04 ` Alex Deucher
2018-01-29 18:45 ` sylvain.bertrand
2018-01-29 18:58 ` Alex Deucher
2018-01-29 19:31 ` sylvain.bertrand
2018-01-29 19:39 ` Alex Deucher
2018-01-29 20:34 ` sylvain.bertrand
2018-01-29 20:40 ` Alex Deucher
2018-01-29 22:35 ` sylvain.bertrand [this message]
2018-01-29 22:55 ` Alex Deucher
2018-01-30 15:17 ` Harry Wentland
2018-01-30 16:42 ` sylvain.bertrand
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=20180129223522.GA12004@freedom \
--to=sylvain.bertrand@gmail.com \
--cc=alexdeucher@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox