Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I2C protocol for touchpad module #10

Closed
cscott opened this issue Feb 2, 2024 · 1 comment · Fixed by #17
Closed

I2C protocol for touchpad module #10

cscott opened this issue Feb 2, 2024 · 1 comment · Fixed by #17

Comments

@cscott
Copy link

cscott commented Feb 2, 2024

Again, thanks so much for the information provided in #8.

There have been requests to create alternate touchpads, and the missing piece to do this (other than #9, the mechanical specs) would be details of the I2C protocol spoken by the touchpad. There is a "HID over I2C" thing, and if that's what's going on here than probably just stating so would be enough. If its a bespoke protocol, then we'd probably need the datasheet for the stock touchpad used in the FW16 so we could emulate it properly.

@JohnAZoidberg
Copy link
Member

I2C is connected to the CPU, so you can do whatever you want, as long as you have an OS driver that supports it.
Our modules do HID over I2C (on Framework 16 but also on Framework 13).
I see you came to the same conclusion already 😃 https://community.frame.work/t/touchpad-with-2-buttons-instead-of-clickpad/36343/18?u=daniel_schaefer
Sorry the the late response.

The same I2C bus is also connected to the EC. So that if you boot to your OS without the touchpad connected, the EC will pretend to be a touchpad. This is so that the windows driver won't freak out. See FrameworkComputer/EmbeddedController@9d49389

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants