From: Pekka Paalanen <ppaalanen@gmail.com>
To: "Ser, Simon" <simon.ser@intel.com>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
"michel@daenzer.net" <michel@daenzer.net>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"paul.kocialkowski@bootlin.com" <paul.kocialkowski@bootlin.com>,
"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"Vetter, Daniel" <daniel.vetter@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v7 09/11] drm: uevent for connector status change
Date: Tue, 4 Jun 2019 10:06:09 +0300 [thread overview]
Message-ID: <20190604100609.235cd763@eldfell.localdomain> (raw)
In-Reply-To: <6782500f2aa3a2b1fbf2dde6a6c31d1bba8b575c.camel@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1900 bytes --]
On Mon, 3 Jun 2019 15:19:13 +0000
"Ser, Simon" <simon.ser@intel.com> wrote:
> On Mon, 2019-06-03 at 17:08 +0200, Daniel Vetter wrote:
> > It's definitely a very suboptimal situation. Not sure there's a good way
> > out. The trouble here is that i915 ended up configuring crtc/connectors
> > differently than -modesetting (to allow fastboot, which I think is still
> > i915 exclusive). This then highlighted that modesetting can't do atomic
> > modesets if you try to reassign connectors.
> >
> > One idea I have is that vgms would help compositors to play out a bunch of
>
> Just so people aren't confused: I think Daniel meant "vkms" here :P
>
> > standard scenarios, even automated. But that's not there yet, and every
> > compositor project needs to care beyond "boots on my laptop, ship it". No
> > idea that's even possible.
>
> Having documentation for userspace is also important IMHO.
>
> Regarding automated compositor testing, it's probably not possible to
> have a single place where all compositors are tested: vkms should
> probably be included as part of their CI. Thoughts?
>
> Anyway, we could start a discussion to see if compositor people are
> interested. Or have you already talked to some compositor maintainers?
FWIW, I would absolutely *love* to be able to exercise Weston's
DRM-backend in Gitlab CI with anything, even just vkms, at least in
Weston's test suite to test Weston against KMS in general. Once that is
up, kernel people could replicate from that to their own CI for testing
drivers against known userspace.
I think it would be an awesome long term plan, whether uAPI specs
appear or not. Long term, because I have no idea who could work on it
when. In theory, all I would be waiting for is for vkms to be just
featureful enough and to figure out a way how to get that running
inside Gitlab CI.
Thanks,
pq
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-04 7:06 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:27 [PATCH v7 00/11] HDCP2.2 Phase II Ramalingam C
2019-05-07 16:27 ` [PATCH v7 01/11] drm: move content protection property to mode_config Ramalingam C
2019-05-07 16:27 ` [PATCH v7 02/11] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-05-07 16:27 ` [PATCH v7 03/11] drm: generic fn converting be24 to cpu and vice versa Ramalingam C
2019-05-07 16:27 ` [PATCH v7 04/11] drm: revocation check at drm subsystem Ramalingam C
2019-07-04 10:53 ` Pekka Paalanen
2019-09-12 0:15 ` Harry Wentland
2019-09-12 1:14 ` Deucher, Alexander
2019-09-12 6:54 ` Ramalingam C
2019-09-12 15:49 ` Harry Wentland
2019-05-07 16:27 ` [PATCH v7 05/11] drm/i915: SRM revocation check for HDCP1.4 and 2.2 Ramalingam C
2019-05-07 16:27 ` [PATCH v7 06/11] drm/hdcp: gathering hdcp related code into drm_hdcp.c Ramalingam C
2019-05-07 16:27 ` [PATCH v7 07/11] drm: Add Content protection type property Ramalingam C
2019-07-04 11:11 ` Pekka Paalanen
2019-07-04 10:36 ` Ramalingam C
2019-07-05 13:00 ` Pekka Paalanen
2019-07-05 6:33 ` Ramalingam C
2019-07-05 14:12 ` Pekka Paalanen
2019-05-07 16:27 ` [PATCH v7 08/11] drm/i915: Attach content " Ramalingam C
2019-05-07 16:27 ` [PATCH v7 09/11] drm: uevent for connector status change Ramalingam C
2019-05-10 12:12 ` Paul Kocialkowski
2019-05-10 14:54 ` Daniel Vetter
2019-05-13 9:02 ` Paul Kocialkowski
2019-05-13 9:34 ` Daniel Vetter
2019-05-13 10:11 ` Ser, Simon
2019-05-13 15:04 ` Daniel Vetter
2019-05-14 6:18 ` Ser, Simon
2019-05-13 17:14 ` Paul Kocialkowski
2019-05-14 11:09 ` Daniel Vetter
2019-05-14 14:12 ` Paul Kocialkowski
2019-05-14 14:28 ` Daniel Vetter
2019-05-15 7:43 ` Paul Kocialkowski
2019-05-15 7:48 ` Daniel Vetter
2019-05-14 8:02 ` Pekka Paalanen
2019-05-14 8:18 ` Ser, Simon
2019-05-14 11:02 ` Daniel Vetter
2019-05-14 13:36 ` Pekka Paalanen
2019-05-14 13:58 ` Paul Kocialkowski
2019-05-14 14:34 ` Daniel Vetter
2019-05-15 7:37 ` Pekka Paalanen
2019-05-15 7:49 ` Paul Kocialkowski
2019-05-15 8:24 ` Daniel Vetter
2019-05-16 8:22 ` Pekka Paalanen
2019-05-16 12:24 ` Daniel Vetter
2019-05-17 10:08 ` Pekka Paalanen
2019-05-20 16:11 ` Daniel Vetter
2019-05-20 16:24 ` Paul Kocialkowski
2019-05-21 6:55 ` Pekka Paalanen
2019-05-21 7:52 ` Daniel Vetter
2019-05-21 9:01 ` Pekka Paalanen
2019-05-21 9:42 ` Daniel Vetter
2019-06-03 9:50 ` Michel Dänzer
2019-06-03 15:08 ` Daniel Vetter
2019-06-03 15:19 ` Ser, Simon
2019-06-04 7:06 ` Pekka Paalanen [this message]
2019-05-13 21:20 ` Lyude Paul
2019-05-14 11:12 ` Daniel Vetter
2019-07-04 11:12 ` Pekka Paalanen
2019-07-04 10:42 ` Ramalingam C
2019-07-05 13:36 ` Pekka Paalanen
2019-05-07 16:27 ` [PATCH v7 10/11] drm/hdcp: update content protection property with uevent Ramalingam C
2019-07-04 11:14 ` Pekka Paalanen
2019-07-04 11:11 ` Ramalingam C
2019-07-05 13:59 ` Pekka Paalanen
2019-07-04 23:51 ` Ramalingam C
2019-05-07 16:27 ` [PATCH v7 11/11] drm/i915: update the hdcp state " Ramalingam C
2019-05-07 16:45 ` ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev9) Patchwork
2019-05-07 16:52 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-07 17:37 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-08 0:41 ` ✓ Fi.CI.IGT: " Patchwork
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=20190604100609.235cd763@eldfell.localdomain \
--to=ppaalanen@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=michel@daenzer.net \
--cc=paul.kocialkowski@bootlin.com \
--cc=simon.ser@intel.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox