search

torizon / blog

1 stars 1 forks source link

device-cgroup-rule description missing in blog post #16

Open escherstair opened 3 months ago

escherstair commented 3 months ago

The blog post about containerized hardware acceleration gives a quick but usefule description about what device-cgroup-rule is: https://github.com/torizon/blog/blob/5891d8034e700a9b9d29d647071bb0beaf98808e/content/how-does-hardware-acceleration-work-with-containers.md?plain=1#L147-L150 Devices 4, 13, 226 and 199 are described.

But in the example below, 10:233 is used too https://github.com/torizon/blog/blob/5891d8034e700a9b9d29d647071bb0beaf98808e/content/how-does-hardware-acceleration-work-with-containers.md?plain=1#L175-L181

Looking here this seems to be 223 = /dev/input/uinput User level driver support for input Is this valid for Torizon OS too? Is this a specific drived necessary to use touch (or multi-touch) gestures on Torizon OS?

Thanks

leonheldattoradex commented 2 months ago

Great catch!

Is this valid for Torizon OS too?

Yep, this more general numbers are generally respected even by downstream kernels like the one we use on the iMX8 devices.

Is this a specific drived necessary to use touch (or multi-touch) gestures on Torizon OS?

If I recall correctly, event catchers related to touch devices will be listed as device descriptors at /dev/input. 223 is specifically for emulating drivers from userspace. This is used in conjunction with tools like https://github.com/ReimuNotMoe/ydotool which can simulate clicks etc so we can automatically test GUIs.

This was used a long time ago with our automated testing setup and I guess I was working there and copied the excerpt from the testing scripts :-)