-
Notifications
You must be signed in to change notification settings - Fork 340
Proposal: configure devices with their name and their connector #403
Comments
The names already describe a physical connector on a GPU so there is already no ambiguity, but I do see the value in configuring a monitor based on information about the monitor itself, instead of where you plugged it in. None of this configuration needs to live in wlroots, though. We already make users configure it from a The only thing that would actually require wlroots changes is adding a serial number, which is a pretty minor change. DRM is the only backend you could get this information. Although, I suppose it's the only backend that would find it useful too.
I don't see the point in doing this in particular. |
That's why I want to rename
Yes, most of the work will be in rootston. We just need to add some fields in |
In the DRM backend, there is no distinction between output and connector. |
Yeah, but a
Maybe |
Do we want to support syspaths as unique input device identifiers? @SirCmpwn: can you add this to struct udev_device *udev_dev = libinput_device_get_udev_device(libinput_dev);
const char *sysname = udev_device_get_sysname(udev_dev);
wlr_log(L_DEBUG, "sysname: %s", sysname); |
Added fallbacks in DRM backend in case EDID extension data for model and serial is missing. Updates swaywm#403
Added fallbacks in DRM backend in case EDID extension data for model and serial is missing. Updates swaywm#403
Might be able to do good stuff with udev properties:
|
Input devices
Currently input devices are configured with their
wlr_input_device.name
- but if you have two identical devices, you can't configure them independently:Unfortunately, inputs devices don't seem to have a serial number - only a friendly name, manufacturer and model.
Proposal: being able to configure them by their connector (retrieved from udev). We could add a
char *connector
field towlr_input_device
for that.Ouputs
Outputs are always identified by their connector for now:
VGA-1
,HDMI-1-A
... However, if you have for instance two DisplayPort connectors, it can make more sense to configure outputs by their name (just like input devices right now). Also outputs have a serial number which can be used to uniquely identify them (given a valid EDID).Proposal: being able to configure them by their name (manufacturer, model and serial). The
wlr_output
currently has aname
field used for the connector name - we could rename it toconnector
and add aserial
field (make
andmodel
are already here).serial
fieldFind a better name for thename
fieldmake
,model
andserial
to configure outputsThe text was updated successfully, but these errors were encountered: