commit | 94f5f422b6b862606ca96108c2538ed32c5ec104 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Fri Aug 16 15:22:08 2024 -0400 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Aug 16 15:22:08 2024 -0400 |
tree | 8ec7e00660809957f4a2f50a35f7b4dc6930e92e | |
parent | 1ece8e3c72c256af0b921ce0eed296b00364d79d [diff] |
clang-format: re-format for clang-18 clang-format-18 isn't compatible with the clang-format-17 output, so we need to reformat the code with the latest version. The way clang-18 handles lambda formatting also changed, so we have made changes to the organization default style format to better handle lambda formatting. See I5e08687e696dd240402a2780158664b7113def0e for updated style. See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement. Change-Id: I6e1b877213f3a2921d78ffe2a5fe71d93db65574 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
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