From: Daniel Stone <daniel@fooishbar.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Stefan Agner" <stefan@agner.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH] drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again
Date: Thu, 23 Mar 2017 12:01:30 +0000 [thread overview]
Message-ID: <CAPj87rOFo252265QWQem5MkOKCPMAL3eKC4qYCzAzK5dNYbZhA@mail.gmail.com> (raw)
In-Reply-To: <20170323085326.20185-1-michel@daenzer.net>
Hi Michel,
On 23 March 2017 at 08:53, Michel Dänzer <michel@daenzer.net> wrote:
> Otherwise this can also prevent modesets e.g. for switching VTs, when
> multiple monitors with different native resolutions are connected.
>
> The depths must match though, so keep the != test for that.
>
> Also update the DRM_DEBUG output to be slightly more accurate, this
> doesn't only affect requests from userspace.
This test looks much more sensible, and also fixes VT switching for me.
Reviewed-by: Daniel Stone <daniels@collabora.com>
Cheers,
Daniel
next prev parent reply other threads:[~2017-03-23 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 9:55 [PATCH] drm/fb-helper: Only reject FB changes if FB_MISC_USER_EVENT is set Michel Dänzer
2017-03-16 10:09 ` Ville Syrjälä
2017-03-17 9:01 ` Michel Dänzer
2017-03-17 10:01 ` Ville Syrjälä
2017-03-17 10:19 ` Michel Dänzer
2017-03-17 11:13 ` Ville Syrjälä
2017-03-21 3:24 ` Michel Dänzer
2017-03-16 10:09 ` Daniel Stone
2017-03-17 8:54 ` Michel Dänzer
2017-03-23 8:53 ` [PATCH] drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again Michel Dänzer
2017-03-23 12:01 ` Daniel Stone [this message]
2017-03-23 13:59 ` Daniel Vetter
2017-03-24 0:42 ` Stefan Agner
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=CAPj87rOFo252265QWQem5MkOKCPMAL3eKC4qYCzAzK5dNYbZhA@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=stefan@agner.ch \
--cc=ville.syrjala@linux.intel.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).