[PATCH 4/4] drivers/tty/vt: add ioctl to manage input specific keyboard configs

Because user can use different keyboards with different layouts on the same tty, an input could have a different key map from another one. In order to use and modify this specific key map the user can call three new ioctls: 1) KDGKBIENT Get an input key map's entry. If the input does not

[PATCH 4/4] drivers/tty/vt: add ioctl to manage input specific keyboard configs

Because user can use different keyboards with different layouts on the same tty, an input could have a different key map from another one. In order to use and modify this specific key map the user can call three new ioctls: 1) KDGKBIENT Get an input key map's entry. If the input does not

[RFC PATCH 4/4] drivers/tty/vt: add ioctl to manage input specific keyboard configs

Because user can use different keyboards with different layouts on the same tty, an input could have a different key map from another one. In order to use and modify this specific key map the user can call three new ioctls: 1) KDGKBIENT Get an input key map's entry. If the input does not

[RFC PATCH 4/4] drivers/tty/vt: add ioctl to manage input specific keyboard configs

Because user can use different keyboards with different layouts on the same tty, an input could have a different key map from another one. In order to use and modify this specific key map the user can call three new ioctls: 1) KDGKBIENT Get an input key map's entry. If the input does not