From: Johannes Thyssen Tishman <johannes@thyssentishman.com>
Subject: Re: chromebook keyboards
To: Miod Vallat <miod@online.fr>
Cc: Brandon Mercer <bmercer@eutonian.com>, Mark Kettenis <mark.kettenis@xs4all.nl>, tech@openbsd.org
Date: Wed, 16 Oct 2024 17:29:16 +0200

On Wed, Oct 16, 2024 at 02:16:41PM +0000, Miod Vallat wrote:
> What happens on your machine is that the touchpad is also in legacy
> space (attaching as pms), and uses irq 12.
> 
> This is not handled by the pckbc@acpi attachment yet, because I was
> expecting systems with PS/2-compatible touchpad to work with the legacy
> pckbc@isa attachment, which registers the two interrupts (1 for
> keyboard, 12 for mouse). The few systems tested where pckbc@acpi is an
> improvement, have their touchpad behind i2c, as imt or ims devices).
> 
> I need to think a bit more on how to solve this - I would need the
> pckbc@acpi driver to attach to two acpi nodes, which is not something
> the BSD device model allows.

Thanks for the quick reply Miod. Just so we are on the same page and to
avoid confusions, I'm referring to the *trackpoint* (little red dot)[1]
in the middle of the keyboard and not the *touchpad* below the keyboard.
The touchpad and its 2 internal buttons (the ones you click by pressing
on the touchpad) work just fine and are indeed behind imt and ims
devices:

$ dmesg | grep -E 'im(t|s)'
imt0 at ihidev0: clickpad, 5 contacts
wsmouse0 at imt0 mux 0
ims0 at ihidev0 reportid 2: 2 buttons
wsmouse1 at ims0 mux 0

Only the trackpoint and its 3 corresponding buttons above the touchpad
do not work. I don't know if this makes any difference in regards to
what you said though, just wanted to clarify.

[1] https://en.wikipedia.org/wiki/Pointing_stick#/media/File:Mouse_pointing_stick.jpeg