Hi! > Every multi_zone_* mode could also output a zones_image. That is a greyscale > bitmap or even a svg containing the information where each zone is located > and which outline it has. For the bitmap the information would be encoded in > the grey value, aka 0 = zone 0 etc with 0xff = no zone (i.e. space between > the keys). For the svg, the name of the paths would indicate the > zone they This is not really suitable for kernel. > > It would go to drivers/auxdisplay, most probably. > > Looking into it, thanks for the direction. But this would come with the > downside that upowers kbd_brightness no longer controls the keyboard. Yep. We could add some kind of kludge to fix that. Perhaps first question is to ask auxdisplay people if treating keyboard as a weird display is okay? cc: lkml, leds, drm, input at least. Best regards, Pavel -- People of Russia, stop Putin before his war on Ukraine escalates.
Attachment:
signature.asc
Description: PGP signature
