From: Karol Herbst <kherbst@redhat.com>
To: James Jones <jajones@nvidia.com>
Cc: Thierry Reding <treding@nvidia.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.8-rc1
Date: Thu, 13 Aug 2020 19:48:39 +0200 [thread overview]
Message-ID: <CACO55tsZAh4aThBSqiQJ5o6jCi+6vcfXDEfCueyBmOK62ZsW5Q@mail.gmail.com> (raw)
In-Reply-To: <efb830fe-9ded-f5d3-6944-45adbb2a1f80@nvidia.com>
On Thu, Aug 13, 2020 at 7:45 PM James Jones <jajones@nvidia.com> wrote:
>
> I'll defer to Thierry, but I think that may be by design. Tegra format
> modifiers were added to get things like this working in the first place,
> right? It's not a regression, is it?
>
That would be slightly annoying as this would mean by design it's
broken by default :/ Also, we have no Xorg release supporting
modifiers anyway and it does seem to work with X 1.20.8 (which doesn't
enable modifier support). And I talked with Jonas (working on mutter)
about it and there were no plans to turn on modifier support by
default at this point.
> Thanks,
> -James
>
> On 8/13/20 10:19 AM, Karol Herbst wrote:
> > another thing: with gsettings set org.gnome.mutter
> > experimental-features '["kms-modifiers"]' it all just works out of the
> > box with wayland, but that won't be enabled for quite some time, so we
> > need to figure out what is broken (less so with my patch) under
> > wayland with gnome :)
> >
> > On Thu, Aug 13, 2020 at 5:39 PM Karol Herbst <kherbst@redhat.com> wrote:
> >>
> >> btw, I just noticed that wayland with gnome-shell is totally busted.
> >> With this MR it at least displays something, but without it doesn't
> >> work at all.
> >>
> >> On Thu, Aug 13, 2020 at 3:00 PM Karol Herbst <kherbst@redhat.com> wrote:
> >>>
> >>> At least for now I've created an MR to revert the change:
> >>> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6300
> >>>
> >>> But it seems like there was probably a good reason why it got added?
> >>> Happy to have better fixes, but that's the best we've got so far I
> >>> think?
> >>>
> >>> Thierry, what do you think?
> >>>
> >>> On Wed, Aug 12, 2020 at 8:51 PM Karol Herbst <kherbst@redhat.com> wrote:
> >>>>
> >>>> in case you all were wondering, it works on xorg-server git because of
> >>>> this commit: https://gitlab.freedesktop.org/xorg/xserver/-/commit/9b8999411033c9473cd68e92e4690a91aecf5b95
> >>>>
> >>>> On Wed, Aug 12, 2020 at 8:25 PM James Jones <jajones@nvidia.com> wrote:
> >>>>>
> >>>>> On 8/12/20 10:40 AM, Alyssa Rosenzweig wrote:
> >>>>>>> ...and in merging my code with Alyssa's new panfrost format modifier
> >>>>>>> support, I see panfrost does the opposite of this and treats a format
> >>>>>>> modifier list of only INVALID as "don't care". I modeled the new nouveau
> >>>>>>> behavior on the Iris driver. Now I'm not sure which is correct :-(
> >>>>>>
> >>>>>> ....and neither am I. Uh-oh.
> >>>>>>
> >>>>>> I modeled the panfrost code after v3d_resource_create_with_modifiers,
> >>>>>> which treats INVALID as "don't care". I can confirm the panfrost code
> >>>>>> works (in the sense that it's functional on the machines I've tested),
> >>>>>> but I don't know if it is actually correct. I think it is, since
> >>>>>> otherwise you end up using linear in places it's unnecessary, but I'm
> >>>>>> not sure where this is spec'd.
> >>>>>
> >>>>> It would depend on whether an app actually calls the function this way,
> >>>>> and whether that app was tested I suppose. If I'm interpreting the Iris
> >>>>> code correctly and it doesn't break anything, then I'm assuming both
> >>>>> implementations are equally valid in that nothing exercises this path,
> >>>>> but it would be good to have the intended behavior documented somewhere
> >>>>> so we can try to work towards consistent in case someone tries it in the
> >>>>> future.
> >>>>>
> >>>>> My nouveau change runs afoul of assumptions in the tegra driver, but
> >>>>> that's easy enough to fix in lockstep if desired.
> >>>>>
> >>>>> Also, heads up: I'll ping you on my format modifier cleanup MR once I've
> >>>>> pushed the latest version. The panfrost modifier usage was harder to
> >>>>> merge into the refactoring than most, so it'll be good to have your
> >>>>> review and if you have time, some testing. I think I landed on an
> >>>>> elegant solution, but open to suggestions.
> >>>>>
> >>>>> Thanks,
> >>>>> -James
> >>>>>
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-08-13 17:49 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 6:06 [git pull] drm for 5.8-rc1 Dave Airlie
2020-06-02 21:21 ` Linus Torvalds
2020-06-02 21:22 ` Linus Torvalds
2020-06-02 21:56 ` Linus Torvalds
2020-06-03 7:18 ` Thomas Zimmermann
2020-06-03 7:43 ` Daniel Vetter
2020-06-02 22:14 ` Linus Torvalds
2020-06-02 23:03 ` Dave Airlie
2020-06-02 22:20 ` pr-tracker-bot
2020-06-03 20:13 ` Jason Gunthorpe
2020-06-04 8:10 ` Christian König
2020-06-30 23:08 ` Kirill A. Shutemov
2020-07-01 4:40 ` James Jones
2020-07-01 7:57 ` Kirill A. Shutemov
2020-07-01 7:59 ` Kirill A. Shutemov
2020-07-01 19:45 ` James Jones
2020-07-02 7:36 ` Daniel Vetter
2020-07-02 7:59 ` Pekka Paalanen
2020-07-02 8:22 ` Daniel Stone
2020-07-02 21:14 ` James Jones
2020-07-03 6:01 ` James Jones
2020-07-03 7:16 ` Daniel Vetter
2020-07-13 1:37 ` Dave Airlie
2020-07-14 14:31 ` James Jones
2020-08-04 8:58 ` Karol Herbst
2020-08-12 0:19 ` James Jones
2020-08-12 10:27 ` Karol Herbst
2020-08-12 10:43 ` Karol Herbst
2020-08-12 12:24 ` Karol Herbst
2020-08-12 12:37 ` Ilia Mirkin
2020-08-12 17:03 ` James Jones
2020-08-12 17:10 ` Karol Herbst
2020-08-12 17:19 ` James Jones
2020-08-12 17:40 ` Alyssa Rosenzweig
2020-08-12 18:24 ` James Jones
2020-08-12 18:51 ` Karol Herbst
2020-08-13 13:00 ` Karol Herbst
2020-08-13 15:39 ` Karol Herbst
2020-08-13 17:19 ` Karol Herbst
2020-08-13 17:45 ` James Jones
2020-08-13 17:48 ` Karol Herbst [this message]
2020-08-14 13:57 ` Thierry Reding
2020-08-14 13:59 ` Karol Herbst
2020-08-14 14:10 ` Thierry Reding
2020-08-14 14:05 ` Thierry Reding
2020-08-14 14:44 ` Karol Herbst
2020-08-14 15:34 ` Thierry Reding
2020-08-14 15:40 ` Karol Herbst
2020-08-14 16:06 ` Thierry Reding
2020-08-14 16:12 ` Karol Herbst
2020-08-14 16:22 ` Thierry Reding
2020-08-14 17:17 ` Daniel Stone
2020-08-14 17:25 ` Daniel Vetter
2020-08-18 14:37 ` Thierry Reding
2020-09-01 7:13 ` Daniel Vetter
2020-09-01 10:42 ` Daniel Stone
2020-09-01 10:59 ` Karol Herbst
2020-09-01 14:42 ` James Jones
2020-08-14 14:08 ` Thierry Reding
2020-08-14 14:45 ` Karol Herbst
2020-08-14 15:24 ` Thierry Reding
2020-08-14 15:43 ` Karol Herbst
2020-08-14 13:54 ` Thierry Reding
2020-08-14 13:40 ` Thierry Reding
2020-08-14 13:56 ` Karol Herbst
2020-08-12 15:05 ` Thierry Reding
2020-08-12 15:20 ` Karol Herbst
2020-08-12 15:49 ` Karol Herbst
2020-07-01 11:24 ` Karol Herbst
2020-07-01 15:51 ` James Jones
2020-07-01 16:01 ` Daniel Vetter
2020-07-01 17:04 ` Karol Herbst
2020-07-01 17:37 ` James Jones
2020-07-01 18:08 ` Karol Herbst
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=CACO55tsZAh4aThBSqiQJ5o6jCi+6vcfXDEfCueyBmOK62ZsW5Q@mail.gmail.com \
--to=kherbst@redhat.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jajones@nvidia.com \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).