You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
raw, which drive "matrix" keyboards with ps/2 scancodes (PET, UK101)
serial, which act like serial terminal inputs (Apple1, cpm80)
Each of these uses a different library combination: PS2KeyRaw and PS2KeyAdvanced / PS2KeyMap.
Raw has its own disadvantages too, it is tied to the UK variant of the PS/2 keyboard.
Could resolve the first problem by adding a scancode interface to PS2KeyAdvanced.
Stoffregen's PS2Keyboard provides APIs for scancodes and utf-8 characters so could be a potential solution. However it isn't clear how function keys are handled in the latter case.
Using a single library would allow to initialise it in hardware_init and be bound to by ps2_raw_kbd or ps2_serial_kbd as required.
It seems as if either PS2KeyAdvanced or PS2Keyboard would need to be forked to facilitate this though.
The text was updated successfully, but these errors were encountered:
Now we have two classes of keyboard:
Each of these uses a different library combination: PS2KeyRaw and PS2KeyAdvanced / PS2KeyMap.
Raw has its own disadvantages too, it is tied to the UK variant of the PS/2 keyboard.
Could resolve the first problem by adding a scancode interface to PS2KeyAdvanced.
Stoffregen's PS2Keyboard provides APIs for scancodes and utf-8 characters so could be a potential solution. However it isn't clear how function keys are handled in the latter case.
Using a single library would allow to initialise it in
hardware_init
and be bound to byps2_raw_kbd
orps2_serial_kbd
as required.It seems as if either PS2KeyAdvanced or PS2Keyboard would need to be forked to facilitate this though.
The text was updated successfully, but these errors were encountered: