From: "Nicolai Hähnle" <nhaehnle@gmail.com>
To: christian.koenig@amd.com, Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for v4.15
Date: Sat, 18 Nov 2017 11:49:27 +0100 [thread overview]
Message-ID: <d4823dd9-56e7-6b8c-4e2c-d7b48c7413c1@gmail.com> (raw)
In-Reply-To: <c248101e-91ba-e451-b648-3d504befd29d@gmail.com>
On 17.11.2017 20:18, Christian König wrote:
> The obvious alternative which we are working on for a few years now is
> to improve the input data we get from the hardware people.
>
> In other words instead of getting a flat list of registers we want the
> information about where and how many times a hardware block was
> instantiated.
>
> But getting that proved much more difficult than we thought and yes we
> are working on that for multiple years now.
Well, the good news is that at least for the gfx registers, I actually
have a proof-of-concept script that extracts the required information
from the hardware sources. Generating e.g. a CB_COLOR_INFO(x) macro
instead of CB_COLORx_INFO defines from that is not that hard :)
The real challenge is getting this integrated into the right processes
so we don't have as much of a maintenance burden.
Cheers,
Nicolai
--
Lerne, wie die Welt wirklich ist,
Aber vergiss niemals, wie sie sein sollte.
prev parent reply other threads:[~2017-11-18 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 2:34 [git pull] drm for v4.15 Dave Airlie
2017-11-16 4:59 ` Linus Torvalds
2017-11-16 13:57 ` Rob Clark
2017-11-16 17:17 ` Michel Dänzer
2017-11-16 20:57 ` Dave Airlie
2017-11-16 21:05 ` Linus Torvalds
2017-11-17 12:51 ` Nicolai Hähnle
2017-11-17 16:57 ` Linus Torvalds
2017-11-17 17:19 ` Lukas Wunner
2017-11-17 17:24 ` Linus Torvalds
2017-11-17 18:14 ` Christian König
2017-11-17 18:55 ` Linus Torvalds
2017-11-17 19:18 ` Christian König
2017-11-18 10:49 ` Nicolai Hähnle [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=d4823dd9-56e7-6b8c-4e2c-d7b48c7413c1@gmail.com \
--to=nhaehnle@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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