[Bug 221777] merge the latest changes to the ig4 module from DragonFly BSD and add Kaby Lake / Intel 100 series platform support

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Aug 12 23:35:03 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221777

--- Comment #12 from marc.priggemeyer at gmail.com ---
(In reply to Daniel from comment #11)

That means that you can now access your I2C devices. There still is a bug in
ig4 that, I am not sure if I remember correctly, but either left- or right
shifts all I2C addresses by one bit (I think it was division, so it should be
2*your device address). Since it is consistent throughout modules (for example
the cyapa module besides others) it won't be a show stopper but it should be
addressed at some point.

You could try to apply the patch I now submitted for review and check if the
hid device can successfully be enumerated on your device (acpi_iichid). The
code ran on my laptop for almost a year now without issues but please consider
it unstable. It might cause a kernel panic on your laptop.

Apply patch.
Go to sys/modules/i2c/iichid, run make and kldload.
Go to sys/modules/acpi/acpi_iichid, run make and kldload.
You should then be able to see some output on dmesg. If your trackpad has
pointing device capabilities besides touchpad, you will have a good chance that
you can read descriptors from /dev/ims*
In any case you can use vmstat -i to verify interrupt handling if attach is
successful.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list