On 28/04/2021 8:21 am, Simon Ser wrote:
>> A solution to make this configuration generic and exposed by the kernel
>> would standardise this across Linux
> Having a KMS property for this makes sense to me.
>
> Chatting with Jani on IRC, it doesn't seem like there's any EDID or
> DisplayID block f
On Wed, 28 Apr 2021, Daniel Vetter 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 fb
On Wed, Apr 28, 2021 at 10:44:03AM +0300, Pekka Paalanen wrote:
> On Wed, 28 Apr 2021 07:21:28 +
> Simon Ser wrote:
>
> > > A solution to make this configuration generic and exposed by the kernel
> > > would standardise this across Linux
> >
> > Having a KMS property for this makes sense t
On Wednesday, April 28th, 2021 at 9:44 AM, Pekka Paalanen
wrote:
> I'm kind of worried whether you can design a description structure that
> would be good for a long time. That list already looks quite
> complicated. Add also watch-like devices with circular displays.
>
> Would the kernel itself
On Wed, 28 Apr 2021 07:21:28 +
Simon Ser wrote:
> > A solution to make this configuration generic and exposed by the kernel
> > would standardise this across Linux
>
> Having a KMS property for this makes sense to me.
>
> Chatting with Jani on IRC, it doesn't seem like there's any EDID or
> A solution to make this configuration generic and exposed by the kernel
> would standardise this across Linux
Having a KMS property for this makes sense to me.
Chatting with Jani on IRC, it doesn't seem like there's any EDID or
DisplayID block for this.
Note, Android exposes a data structure [
