search

FreeBSDDesktop / kms-drm

the DRM part of the linuxkpi-based KMS
63 stars 26 forks source link

Add devctl (devd) notification for connector hotplug (#119) #215

Closed evadot closed 4 years ago

evadot commented 4 years ago

Wayland compositors need a notification to know when to rescan display connectors.

valpackett commented 4 years ago

oh that's why I've had to switch to a vt to rescan displays… I assumed my commit was already pulled to 5.0 as well and I thought it must be some mysterious new bug *facepalm*

zeising commented 4 years ago

oh that's why I've had to switch to a vt to rescan displays… I assumed my commit was already pulled to 5.0 as well and I thought it must be some mysterious new bug facepalm

This must have been missed when getting 5.0 ready then. Which commit are you referring to?

evadot commented 4 years ago

oh that's why I've had to switch to a vt to rescan displays… I assumed my commit was already pulled to 5.0 as well and I thought it must be some mysterious new bug facepalm

This must have been missed when getting 5.0 ready then. Which commit are you referring to?

The one I want to merge in this MR

zeising commented 4 years ago

oh that's why I've had to switch to a vt to rescan displays… I assumed my commit was already pulled to 5.0 as well and I thought it must be some mysterious new bug facepalm

This must have been missed when getting 5.0 ready then. Which commit are you referring to?

The one I want to merge in this MR

I thought by @myfreeweb 's comment that they were referring to another commit, possibly in the 4.16 branch.

evadot commented 4 years ago

oh that's why I've had to switch to a vt to rescan displays… I assumed my commit was already pulled to 5.0 as well and I thought it must be some mysterious new bug facepalm

This must have been missed when getting 5.0 ready then. Which commit are you referring to?

The one I want to merge in this MR

I thought by @myfreeweb 's comment that they were referring to another commit, possibly in the 4.16 branch.

This commit is present in the 4.16 branch.

zeising commented 4 years ago

oh that's why I've had to switch to a vt to rescan displays… I assumed my commit was already pulled to 5.0 as well and I thought it must be some mysterious new bug facepalm

This must have been missed when getting 5.0 ready then. Which commit are you referring to?

The one I want to merge in this MR

I thought by @myfreeweb 's comment that they were referring to another commit, possibly in the 4.16 branch.

This commit is present in the 4.16 branch.

Yeah, I see it now. Sorry.

evadot commented 4 years ago

Regen with git cherry-pick -x to include the original commit hash (suggested by @jbeich)

jbeich commented 4 years ago

Needs to be applied to drm-v5.0-fbsd12.1 branch as well.

zeising commented 4 years ago

Needs to be applied to drm-v5.0-fbsd12.1 branch as well.

That branch isn't in use.