| commit | c11257d864ffdc5441123de7cce588a49df66701 | [log] [tgz] |
|---|---|---|
| author | Jae Hyun Yoo <jae.hyun.yoo@intel.com> | Wed Jul 22 23:39:18 2020 -0700 |
| committer | Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> | Mon Apr 19 13:41:16 2021 -0700 |
| tree | 541abaa217b186d1b19f10ab928c3f2d58fe2ad8 | |
| parent | 7a89cd239ede011d3732336d40e83d7656f90af7 [diff] |
Connect HID gadget device dynamically Connecting HID gadget device statically from the beginning of this service causes an issue on WHLK test. To prevent the issue, this commit changes the HID gadget device handling as dynamic so that the HID gadget device can be connected when this service has at least one KVM client. Tested: /dev/hidg0 and /dev/hidg1 created only when at least one KVM client is connected. Change-Id: I5f6596b9e4e297fb6b507000499fc041460659f7 Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@intel.com>
The obmc-ikvm application is a VNC server that provides access to the host graphics output. The application interfaces with the video device on the BMC that captures the host graphics, and then serves that video data on the RFB (remote framebuffer, also known as VNC) protocol. The application also interfaces with the BMC USB gadget device to pass HID events from the BMC to the host, allowing the user to interact with the host system.
Once the host is running and an appropriate HID gadget device is instantiated on the BMC, the application can be started with the following command: obmc-ikvm -v <video device path> -i <HID gadget device path>
For example:
obmc-ikvm -v /dev/video0 -i /dev/hidg0