All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen J <stephenjust@gmail.com>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Extract physical display dimensions from VBT
Date: Wed, 1 Jun 2016 15:48:12 -0600	[thread overview]
Message-ID: <CAOvWGzi1MoJ-J9joB-NPLeQMDdgUw2k7EMXswSxAy1ntBcCnXA@mail.gmail.com> (raw)
In-Reply-To: <1464685714-30507-1-git-send-email-ville.syrjala@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]

I can confirm that this v2 patch, combined with the change to the xorg
driver is enough for X to report the correct display dimensions for
my Surface 3 device.

Thank you,
Stephen

On Tue, May 31, 2016 at 3:08 AM, <ville.syrjala@linux.intel.com> wrote:

> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The VBT has these mysterious H/V image sizes as part of the display
> timings. Looking at some dumps those appear to be the physical
> dimensions in mm. Which makes sense since the timing descriptor matches
> the format used by EDID detailed timing descriptor, which defines these
> as "H/V Addressable Video Image Size in mm".
>
> So let's use that information from the panel fixed mode to get the
> physical dimensions for LVDS/eDP/DSI displays. And with that we can
> fill out the display_info so that userspace can get at it via
> GetConnector.
>
> v2: Use (hi<<8)|lo instead of broken (hi<<4)+lo
>     Handle LVDS and eDP too
>
> Cc: Stephen Just <stephenjust@gmail.com>
> Tested-by: Stephen Just <stephenjust@gmail.com> (v1)
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96255
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>

[-- Attachment #1.2: Type: text/html, Size: 2001 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-06-01 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31  9:08 [PATCH] drm/i915: Extract physical display dimensions from VBT ville.syrjala
2016-05-31 12:07 ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-06-02 11:26   ` Ville Syrjälä
2016-06-01 21:48 ` Stephen J [this message]
2016-06-02  9:54 ` [PATCH] " Mika Kahola
2016-06-02 11:41   ` Ville Syrjälä

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=CAOvWGzi1MoJ-J9joB-NPLeQMDdgUw2k7EMXswSxAy1ntBcCnXA@mail.gmail.com \
    --to=stephenjust@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 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.