From: Rob Clark <robdclark@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Rob Clark <robdclark@chromium.org>, Sean Paul <sean@poorly.run>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Jonathan Marek <jonathan@marek.ca>,
Sharat Masetty <smasetty@codeaurora.org>,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
Harigovindan P <harigovi@codeaurora.org>,
Sam Ravnborg <sam@ravnborg.org>, zhengbin <zhengbin13@huawei.com>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@vger.kernel.org>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<freedreno@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm/msm: sync generated headers
Date: Sat, 11 Jul 2020 07:49:52 -0700 [thread overview]
Message-ID: <CAF6AEGu3_qYWGKVmc2VrMVzU35svgxTEVKAMpNUZfy_jZg3euQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdb0+V7AmvG0JXXETzayr4Q785OLhBWjU414tUJo1toJOQ@mail.gmail.com>
On Sat, Jul 11, 2020 at 4:49 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Tue, Jul 7, 2020 at 10:36 PM Rob Clark <robdclark@gmail.com> wrote:
>
> > From: Rob Clark <robdclark@chromium.org>
> >
> > We haven't sync'd for a while.. pull in updates to get definitions for
> > some fields in pkt7 payloads.
> >
> > Signed-off-by: Rob Clark <robdclark@chromium.org>
>
> Out of curiosity : where are the syncs coming from? Mesa?
sometimes indirectly.. but they are generated from:
https://github.com/freedreno/envytools/tree/master/rnndb
The cmdstream and devcoredump decoding tools (which also use the xml)
are in the envytools tree as well.
We have a copy of the gpu side xml in mesa, where we generate the
headers at build time, but I guess doing that on the kernel side would
introduce some build time dependencies that others wouldn't
appreciate:
https://gitlab.freedesktop.org/mesa/mesa/-/tree/master/src/freedreno/registers
Mesa already depends a lot on py generated headers, tables, etc.
BR,
-R
> Yours,
> Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Rob Clark <robdclark@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Clark <robdclark@chromium.org>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<freedreno@lists.freedesktop.org>,
Jonathan Marek <jonathan@marek.ca>,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
David Airlie <airlied@linux.ie>, Sam Ravnborg <sam@ravnborg.org>,
Sharat Masetty <smasetty@codeaurora.org>,
Harigovindan P <harigovi@codeaurora.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>,
zhengbin <zhengbin13@huawei.com>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@vger.kernel.org>, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH 1/2] drm/msm: sync generated headers
Date: Sat, 11 Jul 2020 07:49:52 -0700 [thread overview]
Message-ID: <CAF6AEGu3_qYWGKVmc2VrMVzU35svgxTEVKAMpNUZfy_jZg3euQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdb0+V7AmvG0JXXETzayr4Q785OLhBWjU414tUJo1toJOQ@mail.gmail.com>
On Sat, Jul 11, 2020 at 4:49 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Tue, Jul 7, 2020 at 10:36 PM Rob Clark <robdclark@gmail.com> wrote:
>
> > From: Rob Clark <robdclark@chromium.org>
> >
> > We haven't sync'd for a while.. pull in updates to get definitions for
> > some fields in pkt7 payloads.
> >
> > Signed-off-by: Rob Clark <robdclark@chromium.org>
>
> Out of curiosity : where are the syncs coming from? Mesa?
sometimes indirectly.. but they are generated from:
https://github.com/freedreno/envytools/tree/master/rnndb
The cmdstream and devcoredump decoding tools (which also use the xml)
are in the envytools tree as well.
We have a copy of the gpu side xml in mesa, where we generate the
headers at build time, but I guess doing that on the kernel side would
introduce some build time dependencies that others wouldn't
appreciate:
https://gitlab.freedesktop.org/mesa/mesa/-/tree/master/src/freedreno/registers
Mesa already depends a lot on py generated headers, tables, etc.
BR,
-R
> Yours,
> Linus Walleij
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-07-11 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 20:34 [PATCH 0/2] drm/msm/adreno: cleanup some packet building Rob Clark
2020-07-07 20:34 ` Rob Clark
2020-07-07 20:34 ` [PATCH 1/2] drm/msm: sync generated headers Rob Clark
2020-07-07 20:34 ` Rob Clark
2020-07-10 18:02 ` Jordan Crouse
2020-07-11 11:48 ` Linus Walleij
2020-07-11 11:48 ` Linus Walleij
2020-07-11 14:49 ` Rob Clark [this message]
2020-07-11 14:49 ` Rob Clark
2020-07-07 20:35 ` [PATCH 2/2] drm/msm/adreno: un-open-code some packets Rob Clark
2020-07-07 20:35 ` Rob Clark
2020-07-10 18:03 ` [Freedreno] " Jordan Crouse
2020-07-10 18:03 ` Jordan Crouse
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=CAF6AEGu3_qYWGKVmc2VrMVzU35svgxTEVKAMpNUZfy_jZg3euQ@mail.gmail.com \
--to=robdclark@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=harigovi@codeaurora.org \
--cc=jcrouse@codeaurora.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=jonathan@marek.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
--cc=smasetty@codeaurora.org \
--cc=zhengbin13@huawei.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 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.