commit | ed98d07da65cd88781015538fa8aeca636e23eeb | [log] [tgz] |
---|---|---|
author | Brad Bishop <bradleyb@fuzziesquirrel.com> | Thu Nov 14 14:49:20 2019 -0500 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Thu Nov 14 15:05:52 2019 -0500 |
tree | 0f8c741c433144e816ec9864d2ce6b0ac975125c | |
parent | 7cf1f1d43ef9b4c312bfb2c7c61514ca93a53ee6 [diff] |
build: drop autotools support It made sense to support both build systems while OpenBMC transitioned but that has been complete for some time - No need to support multiple build systems any longer. Change-Id: Ib698163f53a4f493f20491c54851247c5700f13e Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.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