All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202449] vrr_capable not showing up in xrandr with eDP display.
Date: Wed, 30 Jan 2019 20:12:44 +0000	[thread overview]
Message-ID: <bug-202449-2300-3gCwOfHiGQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202449-2300@https.bugzilla.kernel.org/>

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

--- Comment #7 from Haxk20 (haxk612@gmail.com) ---
(In reply to Nicholas Kazlauskas from comment #5)
> Created attachment 280873 [details]
> 0001-drm-amd-display-Attach-VRR-properties-for-eDP-connec.patch
> 
> I'm not sure if this will actually let you use variable refresh rate
> features but this should attach the properties for your eDP panel at least.

This fixes the issue.
I know its too late for this to be sent into 5.0 but can you send this into
drm-next-5.1-wip so that this makes it into 5.1 ? 
Thank you.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-01-30 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 15:16 [Bug 202449] New: vrr_capable not showing up in xrandr with eDP display bugzilla-daemon
2019-01-29 15:31 ` [Bug 202449] " bugzilla-daemon
2019-01-29 15:33 ` bugzilla-daemon
2019-01-29 15:45 ` bugzilla-daemon
2019-01-29 15:46 ` bugzilla-daemon
2019-01-30 13:59 ` bugzilla-daemon
2019-01-30 19:59 ` bugzilla-daemon
2019-01-30 20:12 ` bugzilla-daemon [this message]
2019-01-30 20:17 ` bugzilla-daemon
2019-01-31 18:53 ` 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-202449-2300-3gCwOfHiGQ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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.