Michael Olbrich f5ec830cc2 v4l2: propagate vendor and device id to the node object ... When pipewire is accessed through the portal camera API then only the camera node objects are visible for the client. However, chromium wants to know the vendor and device ids to identify cameras. And those properties are currently only added to the device object. Fix this by propagating the ids to the node object. Fixes #1879		2021-12-09 10:20:59 +01:00
..
alsa	alsa: improve debug	2021-12-07 12:05:49 +01:00
audioconvert	resample: recalc rate match when out of buffers	2021-12-03 17:54:00 +01:00
audiomixer	spa: use log topics	2021-10-13 10:48:23 +02:00
audiotestsrc	audiotestsrc: convert sizes to const size_t	2021-07-05 23:30:45 +03:00
bluez5	bluez: check dbus service before enumerating objects	2021-11-17 12:00:00 +01:00
control	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
ffmpeg	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
jack	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
libcamera	libcamera: improve debug	2021-11-03 17:49:10 +01:00
support	cpu: only run SSE code when supported	2021-11-02 20:12:35 +01:00
test	spa: test: remove port EnumFormat param info	2021-11-30 17:33:17 +00:00
v4l2	v4l2: propagate vendor and device id to the node object	2021-12-09 10:20:59 +01:00
videoconvert	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
videotestsrc	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
volume	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
vulkan	spa: fix the indentation in the various meson.build files	2021-09-20 07:29:03 +00:00
meson.build	meson.build: adds V4L2 header and enablement reporting via summary()	2021-06-25 15:13:07 +03:00