All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216814] New: amdgpu: CTM support has disappeared (vega)
Date: Fri, 16 Dec 2022 12:08:41 +0000	[thread overview]
Message-ID: <bug-216814-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216814

            Bug ID: 216814
           Summary: amdgpu: CTM support has disappeared (vega)
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.0
          Hardware: AMD
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: maxijac@free.fr
        Regression: No

Hello,

I noticed the CTM support from X is no longer advertised with recent kernels.

Card: Vega64
xf86-video-amdgpu: 22.0.0-1

With older kernels, xrandr reports CTM correctly.
With the same X stack, simple rebooting on a more recent kernel, CTM is not
advertised anymore.


>$ uname -r
>5.15.83-1-lts
>$ xrandr --prop | grep -i ctm
>        CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
>        CTM: 0
>        CTM: 0
>        CTM: 0
>        CTM: 0
>        CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
>$
> 

> -- Reboot to 6.1 --

> 
>$ uname -r
>6.1.0-arch1-1
>$ xrandr --prop | grep -i ctm
>$

I also have a custom config 6.0 kernel that shows no CTM so the break has
happened between 5.15 and 6.0.
I tried looking at commits in between and code changes in amdgpu but did not
notice anything obvious.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-12-16 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 12:08 bugzilla-daemon [this message]
2022-12-17  8:30 ` [Bug 216814] amdgpu: CTM support has disappeared (vega) bugzilla-daemon

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=bug-216814-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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 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.