kbc: Support get scancode command sequence

[phcoder]

This improves compatibility with PS/2 protocol.

[leviport]

Tested on my oryp9. Not seeing any adverse effects.

[crawfxrd]

oryp9 has psmouse blacklisted in system76-driver. Was psmouse loaded?

[leviport]

It would show up in my boot parameters if it were, right? I'm not seeing it:

kernelstub.Config    : INFO     Looking for configuration...
kernelstub           : INFO     System information:

    OS:..................Pop!_OS 24.04
    Root partition:....../dev/dm-1
    Root FS UUID:........89cd8435-ab39-4ceb-8807-c29029712205
    ESP Path:............/boot/efi
    ESP Partition:......./dev/nvme1n1p1
    ESP Partition #:.....1
    NVRAM entry #:.......-1
    Boot Variable #:.....0000
    Kernel Boot Options:.systemd.show_status=false loglevel=0 quiet splash
    Kernel Image Path:.../boot/vmlinuz-6.17.4-76061704-generic
    Initrd Image Path:.../boot/initrd.img-6.17.4-76061704-generic
    Force-overwrite:.....False

kernelstub           : INFO     Configuration details:

   ESP Location:................../boot/efi
   Management Mode:...............True
   Install Loader configuration:..True
   Configuration version:.........3

Is there a different model that would be better to test this on?

[crawfxrd]

It's set by modprobe options. You can do lsmod | grep psmouse to check if it's loaded. It's probably best to test on a model that has it currently blacklisted (by removing it from the modprobe options and regenerating initramfs), because we know it has issues.

Otherwise, anything in system76driver/products.py with remove_blacklist_psmouse or without any psmouse action.

[leviport]

I also gave this a test on darp10-b since it has remove_blacklist_psmouse. I confirmed that psmouse was not blacklisted since it showed up in lsmod | grep psmouse, and I ran some typing tests. Keyboard behavior seems perfectly normal with this change.