Hi!Yeah thought as much
Every multi_zone_* mode could also output a zones_image. That is a greyscaleThis is not really suitable for kernel.
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
Yep. We could add some kind of kludge to fix that.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.
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