From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sefa Eyeoglu <contact@scrumplex.net>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/edid: add non-desktop quirk to Bigscreen Beyond HMD
Date: Mon, 20 May 2024 11:40:42 +0300 [thread overview]
Message-ID: <87h6esvpth.fsf@intel.com> (raw)
In-Reply-To: <0d800997f7dab23514160ed6a61e8778b7bee57e.camel@scrumplex.net>
On Fri, 17 May 2024, Sefa Eyeoglu <contact@scrumplex.net> wrote:
> On Fri, 2024-05-17 at 16:52 +0200, Philipp Zabel wrote:
>> On Fr, 2024-05-17 at 16:09 +0200, Sefa Eyeoglu wrote:
>> > The Bigscreen Beyond VR headset is a non-desktop output and should
>> > be
>> > marked as such using an EDID quirk.
>> >
>> > Closes https://gitlab.freedesktop.org/drm/misc/kernel/-/issues/39
>>
>> From the EDID posted there, it looks like the quirk should not be
>> necessary?
>>
>> The quoted DisplayID extension block correctly marks this as an HMD:
>>
>> "Display Product Primary Use Case: Head-mounted Virtual Reality
>> (VR) display"
>>
>> The update_displayid_info() function in drm_edid.c should use this
>> information to set the non_desktop flag already. Doesn't this work as
>> expected?
>>
>>
>> regards
>> Philipp
>
> I see.
>
> The only potential reason I can come up with is that the DisplayID
> block is incomplete.
>
> $ edid-decode --check
> Failures:
>
> Block 0, Base EDID:
> Standard Timings: Missing preferred timing.
> EDID:
> DisplayID: Missing DisplayID Product Identification Data Block.
> DisplayID: Missing DisplayID Display Parameters Data Block.
> DisplayID: Missing DisplayID Display Interface Features Data Block.
>
> EDID conformity: FAIL
I've commented on the bug, but I don't think these should matter. We
should be able to deduce the primary use from the DisplayID header.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-05-20 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 10:55 [PATCH] drm/edid: add non-desktop quirk to Bigscreen Beyond HMD Sefa Eyeoglu
2024-05-17 12:54 ` Jani Nikula
2024-05-17 14:14 ` Sefa Eyeoglu
2024-05-17 14:09 ` Sefa Eyeoglu
2024-05-17 14:52 ` Philipp Zabel
2024-05-17 15:36 ` Sefa Eyeoglu
2024-05-20 8:40 ` Jani Nikula [this message]
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=87h6esvpth.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=contact@scrumplex.net \
--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.