From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Pekka Paalanen <ppaalanen@gmail.com>
Cc: martijn@brixit.nl, Caleb Connolly <caleb@connolly.tech>,
dri-devel@lists.freedesktop.org, dri-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: Display notch support
Date: Wed, 28 Apr 2021 15:18:41 +0300 [thread overview]
Message-ID: <87tunq38m6.fsf@intel.com> (raw)
In-Reply-To: <YIlOoHcPyk91Pone@phenom.ffwll.local>
On Wed, 28 Apr 2021, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Apr 28, 2021 at 10:44:03AM +0300, Pekka Paalanen wrote:
>> This seems more like a job for the hypothetical liboutput, just like
>> recognising HMDs (yes, I know, kernel does that already, but there is a
>> point that kernel may not want to put fbcon on a HMD).
>
> I think the desktop linux solution would be hwdb entries, except we've
> never done this for anything display related. So yeah liboutput sounds
> about right for this :-)
>
> Btw on fbcon on HMD, I thought we're already taking care of that?
This is a bit off-topic, but DisplayID 2.0 defines primary use cases for
head mounted VR and AR, so we wouldn't have to quirk them.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-28 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 20:47 Display notch support Caleb Connolly
2021-04-28 7:21 ` Simon Ser
2021-04-28 7:44 ` Pekka Paalanen
2021-04-28 7:51 ` Simon Ser
2021-04-28 12:01 ` Daniel Vetter
2021-04-28 12:18 ` Jani Nikula [this message]
2021-05-03 12:13 ` Caleb Connolly
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=87tunq38m6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=caleb@connolly.tech \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dri-devel@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=ppaalanen@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).