Skip to contentSkip to conversation

VT Improvements

DISCUSSION Alexey Gladkov 2 participants 2 messages Dec 23, 2013

lore
Share & tools
lore
#0 lore raw

Greetings!

I would like to know about the VT plans. Historically, keymap implementations are similar in the kernel and kbd project. I rewrote it in kbd. So, it can handle keycodes bigger than 255. In a kernel everything remained as before. I want to fix this part in a kernel. As pluses will be:

* opportunity to define keycode > 255.
* opportunity to reduce this table a kernel in most cases.

I would like to ask your opinion about my plans because I heard about the thought of moving this functionality to user space.

Whether it is worth starting so large-scale changes?

Signature · 1 line
Rgrds, legion
#1 lore raw
Quoted 8 lines · Alexey Gladkov

Greetings!

I would like to know about the VT plans. Historically, keymap implementations are similar in the kernel and kbd project. I rewrote it in kbd. So, it can handle keycodes bigger than 255. In a kernel everything remained as before. I want to fix this part in a kernel. As pluses will be:

Quoted 8 lines

* opportunity to define keycode > 255.
* opportunity to reduce this table a kernel in most cases.

I would like to ask your opinion about my plans because I heard about the thought of moving this functionality to user space.

Whether it is worth starting so large-scale changes?

What I don't think we want to do is to make the current VT implementation in the kernel significantly bigger. That is why proposals to introduce bidirectionality or character shaping generally have not been accepted. If you can improve functionality with a *smaller* footprint, which you seem to imply above, then please, go ahead.

-hpa