From: "Johannes Thyssen Tishman" Subject: Re: chromebook keyboards To: "Miod Vallat" Cc: "Mark Kettenis" , Date: Mon, 14 Oct 2024 16:05:23 +0200 2024-10-14T11:53:57Z Miod Vallat: > > > Johannes should really be using the GENERIC.MP config. > > > > Apologies for the incompetence, I didn't know that this would make a > > difference. > > What Mark means is that the patch modifies the GENERIC and GENERIC.MP > kernel configuration to add a "pckbc at acpi" line. If your CUSTOM > kernel lacks this line, then the acpi attachment will obviously never > occur. Oh, I see. I now understand the source of my mistake. After patching the GENERIC{,.MP} configs with your patch, I didn't recreate my CUSTOM config. Thanks for explaining Miod. > > Anyways, I'm happy to report that I'm writing this email > > from my laptop keyboard :) However, on a few occasions now (maybe 5 or 6 > > times) while writing this email, keyboard input froze for like a second > > or so and suddenly the last pressed key got repeated many times. After > > these hiccups I can resume typing normally. Have you experienced this > > too? > > No. I am puzzled as your DSDT bits reported an edge-triggered interrupt, > so I was expecting pckbc@isa to work and pckbc@acpi to work as badly as > pckbc@isa. Must be something magic (but then, it's ACPI, so it's a black > box anyway) I'll keep testing the patch. Maybe I can identify if there's a typing pattern that's causing these freezes and repetitions. On another note, I noticed that the trackpoint on the keyboard does not work. Should it be working now that the keyboard is "working" or is this something unrelated? And, are the 'pckbc: command timeout' messages on the console related to this somehow?