1. 15
  1.  

  2. 2

    Great write up and kudos for all the effort you put in to making it work.

    1. 1

      About the only interesting thing with the keyboard was the Google Assistant key, where the Win key usually is. It was not recognized as anything at all […] wrote a patch to interpret it as a useful key (right meta, couldn’t think of anything better)

      Why not see what other OSes (linux, windows) did with it?

      1. 4

        I saw that Linux reports it as some ridiculous very high keycode in evdev, it was over 500 I think. That wouldn’t even be possible in the non-evdev case (that’s 8-bit) and it doesn’t make a lot of sense.

        1. 1

          What about windows?

          1. 3

            No idea. I don’t have the energy/motivation for a windows install. I should have a Windows to Go drive but ehhh I don’t.

            1. 1

              That’s fair. I don’t have a windows install either.

      2. 1

        epic hacking how long did this take you to do?

        1. 2

          uh, good question. I don’t track time :) but roughtly

          • debugging the i2c-hid driver bug and the screen brightness thing took a few days of occasional poking at things
          • the TPM i2c driver took a couple days maybe
          • the little ACPI things (keyboard backlight, tablet mode switch) took a couple hours, trivial stuff