From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: Jose Abreu <Jose.Abreu@synopsys.com>, Jia <lin.a.jia@intel.com>,
Akashdeep Sharma <akashdeep.sharma@intel.com>,
Emil Velikov <emil.l.velikov@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Lin@freedesktop.org, Jim Bride <jim.bride@linux.intel.com>
Subject: Re: [PATCH 1/2] Revert "drm: Add and handle new aspect ratios in DRM layer"
Date: Fri, 11 Nov 2016 19:03:40 +0200 [thread overview]
Message-ID: <20161111170340.GN31595@intel.com> (raw)
In-Reply-To: <20161111170017.GM31595@intel.com>
On Fri, Nov 11, 2016 at 07:00:17PM +0200, Ville Syrjälä wrote:
> On Thu, Nov 03, 2016 at 02:31:43PM +0200, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > This reverts commit a68362fe3e84fcbedd49939aa200519aa5410135.
> >
> > Adding new mode flags willy nilly breaks existing userspace. We need to
> > coordinate this better, potentially with a new client cap that only
> > exposes the aspect ratio flags when userspace is prepared for them
> > (similar to what we do with stereo 3D modes).
>
> As a demonstration here's the change in the xrandr mode list after doing
> the revert:
>
> HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 700mm x 390mm
> - 1920x1080 60.00*+
> - 1920x1080i 60.00 50.00
> + 1920x1080 60.00*+ 50.00 59.94 30.00 25.00 24.00 29.97 23.98
> + 1920x1080i 60.00 50.00 59.94
> 1600x1200 60.00
> 1680x1050 59.88
> 1280x1024 75.02 60.02
> @@ -13,30 +13,29 @@
> 1360x768 60.02
> 1280x800 59.91
> 1152x864 75.00
> - 1280x720 60.00 50.00
> + 1280x720 60.00 50.00 59.94
> 1024x768 75.03 70.07 60.00
> 832x624 74.55
> 800x600 72.19 75.00 60.32
> - 640x480 75.00 72.81 66.67 59.94
> + 720x576 50.00
> + 720x480 60.00 59.94
> + 640x480 75.00 72.81 66.67 60.00 59.94
> 720x400 70.08
>
> This was with sna, which does this:
> #define KNOWN_MODE_FLAGS ((1<<14)-1)
> if (mode->status == MODE_OK && kmode->flags & ~KNOWN_MODE_FLAGS)
> mode->status = MODE_BAD; /* unknown flags => unhandled */
> so all the modes with an aspect ratio just vanished.
>
> -modesetting and -ati on the other hand just copy over the unknown
> bits into the xrandr mode structure, which sounds dubious at best:
> mode->Flags = kmode->flags; //& FLAG_BITS;
> I've not checked what damage it can actually cause.
>
>
> It looks like a few modes disappeared from the kernel's mode list
> as well, presumably because some cea modes in the list originated from
> DTDs and whanot so they don't have an aspect ratio and that causes
> add_alternate_cea_modes() to ignore them. So not populating an aspect
> ratio for cea modes originating from a source other than
> edid_cea_modes[] looks like another bug to me as well.
Oh and I guess this is also the reason most people didn't notice
anything wrong. The preferred mode usually (or maybe always?) comes from
some other source than edid_cea_modes[] and hence doesn't tend to
go AWOL.
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-11 17:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 12:31 [PATCH 1/2] Revert "drm: Add and handle new aspect ratios in DRM layer" ville.syrjala
2016-11-03 12:31 ` [PATCH 2/2] Revert "drm: Add aspect ratio parsing " ville.syrjala
2016-11-03 12:47 ` Sharma, Shashank
[not found] ` <FF3DDC77922A8A4BB08A3BC48A1EA8CB411AE158@BGSMSX101.gar.corp.intel.com>
[not found] ` <20161103130253.GM4617@intel.com>
2016-11-03 13:04 ` [PATCH 1/2] Revert "drm: Add and handle new aspect ratios " Ville Syrjälä
2016-11-03 13:09 ` Ville Syrjälä
2016-11-03 13:22 ` Sharma, Shashank
[not found] ` <2ededbc1-b923-200e-8443-f1ee522402bf@intel.com>
2016-11-03 13:26 ` Ville Syrjälä
2016-11-03 13:34 ` Sharma, Shashank
2016-11-03 13:49 ` Ville Syrjälä
2016-11-03 16:03 ` Daniel Vetter
2016-11-03 16:19 ` Sharma, Shashank
2016-11-07 7:43 ` Sharma, Shashank
2016-11-07 15:26 ` Emil Velikov
2016-11-07 15:48 ` Sharma, Shashank
2016-11-07 16:57 ` Emil Velikov
2016-11-03 16:02 ` Daniel Vetter
2016-11-11 17:00 ` Ville Syrjälä
2016-11-11 17:03 ` Ville Syrjälä [this message]
2016-11-11 17:07 ` Alex Deucher
2016-11-11 17:08 ` Daniel Vetter
2016-11-11 17:22 ` Ville Syrjälä
2016-11-14 14:44 ` Sharma, Shashank
2016-11-14 15:49 ` Ville Syrjälä
2016-11-14 16:07 ` Sharma, Shashank
2016-11-14 16:20 ` Ville Syrjälä
2016-11-14 16:42 ` Sharma, Shashank
2016-11-14 16:45 ` Ville Syrjälä
2016-11-14 16:56 ` Sharma, Shashank
2016-11-15 8:51 ` Daniel Vetter
2016-11-15 9:00 ` Sharma, Shashank
2016-11-15 10:00 ` Daniel Vetter
2016-11-15 10:06 ` Sharma, Shashank
2016-11-15 10:52 ` Daniel Vetter
2016-11-15 13:48 ` Jose Abreu
2016-11-15 14:18 ` Ville Syrjälä
2016-11-15 15:10 ` Sharma, Shashank
2016-11-15 15:18 ` Ville Syrjälä
2016-11-15 15:13 ` Sharma, Shashank
2016-11-15 13:54 ` Ville Syrjälä
2016-11-15 14:03 ` Daniel Vetter
2016-11-15 14:18 ` Alex Deucher
2016-11-15 14:24 ` Ville Syrjälä
2016-11-15 14:26 ` Daniel Vetter
2016-11-15 15:26 ` Alex Deucher
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=20161111170340.GN31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Jose.Abreu@synopsys.com \
--cc=Lin@freedesktop.org \
--cc=akashdeep.sharma@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=jim.bride@linux.intel.com \
--cc=lin.a.jia@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).