Re: [RFC] compositor-drm: name outputs according to connectors if EDID is unavailable

2017-08-25 Thread Pekka Paalanen
On Thu, 24 Aug 2017 09:34:33 -0500 Matt Hoosier wrote: > On Thu, Aug 24, 2017 at 2:49 AM, Pekka Paalanen wrote: > > > > > > drm_kms_helper.edid_firmware=[:][,[:]] > > > > Is there a reason why you would not want to use this kernel DRM option? > > No, the kernel support for manually

Re: [RFC] compositor-drm: name outputs according to connectors if EDID is unavailable

2017-08-24 Thread Matt Hoosier
On Thu, Aug 24, 2017 at 2:49 AM, Pekka Paalanen wrote: > Hi, > > using connector name to describe the connected monitor doesn't sound > right to me. I didn't really like it either. Thanks for the suggestions below. > > If you actually need the connector name in clients then let's > design an ext

Re: [RFC] compositor-drm: name outputs according to connectors if EDID is unavailable

2017-08-24 Thread Pekka Paalanen
On Wed, 23 Aug 2017 20:50:02 -0500 Matt Hoosier wrote: > On embedded systems, EDID is typically unavailble for connectors on buses > such as LVDS or DSI. This change enhances the original opportunistic > naming done in 2b2092adb499d8cdc10390cf19876706bcfe69cb to report the > make and model of an

[RFC] compositor-drm: name outputs according to connectors if EDID is unavailable

2017-08-23 Thread Matt Hoosier
On embedded systems, EDID is typically unavailble for connectors on buses such as LVDS or DSI. This change enhances the original opportunistic naming done in 2b2092adb499d8cdc10390cf19876706bcfe69cb to report the make and model of an output according to the KMS connector (e.g., "DSI-1") if no dynam