Date: Thu, 11 Mar 2021 01:08:19 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 221074] Hyper V Gen 2 install has no mouse Message-ID: <bug-221074-27103-emHbHHD0V6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221074-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-221074-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221074 --- Comment #16 from Vladimir Kondratyev <wulf@freebsd.org> --- (In reply to Dexuan Cui from comment #15) > I'm just not familiar with the HID part. And I am not familiar with VMbus :-) > IIRC, for every mouse event, the Hyper-V host sends > a 7-byte "input_report", which in Linux VM is handled > by the Linux HID API hid_input_report() and nothing else is done. > In FreeBSD, I'm not sure what the equivalent API is? intr_handler callback sends input report body to upper layers. See e.g. iichid driver: https://github.com/freebsd/freebsd-src/blob/main/sys/dev/iicbus/iichid.c#L583. The callback is registered with intr_setup method https://github.com/freebsd/freebsd-src/blob/main/sys/dev/hid/hid_if.m#L50. > I suppose the format of the 7 bytes from the Hyper-V host > should comply with the HID spec for mouse As it is not a boot protocol which takes only 3 bytes, it should be prescribed in HID report descriptor. I think it lies in one of the Linux header files. > I guess Wei (whu) on our team can help on this, and also review the 2 kbd patches. That would be great! Thanks! If someone familiar with VMbus would write driver capable to just print these 7 bytes, I would easily connect it to our HID API. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221074-27103-emHbHHD0V6>