From: sylvain.bertrand@gmail.com
To: Harry Wentland <harry.wentland@amd.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [AMDGPU][TAHITI XT] new display code
Date: Tue, 30 Jan 2018 16:42:16 +0000 [thread overview]
Message-ID: <20180130164216.GA11893@freedom> (raw)
In-Reply-To: <e4a20e7f-a853-4853-0335-b6136625cdd1@amd.com>
On Tue, Jan 30, 2018 at 10:17:06AM -0500, Harry Wentland wrote:
> A good start would be to try re-using the DCE8 code for DCE6. You can
> probably create a new dce60_resource.c and dce60_hw_sequencer.c, copying the
> register structs, caps, function pointers, constructors and destructors from
> the dce80_ versions. Then add a new dce_version and hook it up all over the
> place, add the CHIP IDs for DC support in amdgpu_device_asic_has_dc_support
> and you should pretty much be good to go. If you're lucky you'll light up. If
> not you'll have to debug.
>
> As Alex mentioned, implementing DC support SI parts are not a priority for
> us, but if you have a working patchset I'll be happy to review.
I have massive IRL interference though. I'll give it a try anyway.
Thx for the quickstart tips.
--
Sylvain
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-01-30 16:42 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
2018-01-29 22:55 ` Alex Deucher
2018-01-30 15:17 ` Harry Wentland
2018-01-30 16:42 ` sylvain.bertrand [this message]
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=20180130164216.GA11893@freedom \
--to=sylvain.bertrand@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
/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