KVM Support?

Avi.Fishman at nuvoton.com Avi.Fishman at nuvoton.com
Tue Jul 17 18:56:34 AEST 2018


Hi Eddie,

1. Where is the JPEG HW compression is done?
a. Is it in the V4L driver; the V4L reads the frame buffer compress it and send it via read()?
b. Or the V4L reads the frame buffer send it via read() and another driver compress it for the VNC server?
2. Since VNC RFB supports also other compression protocols, can we use other protocol than JPEG? Hextile for example.
3. Can we see this driver and application code so we can adopt to our HW?

Regards,
Avi


-----Original Message-----
From: Eddie James [mailto:eajames at linux.vnet.ibm.com]
Sent: Monday, July 16, 2018 6:39 PM
To: Avi Fishman
Cc: akashgj91 at gmail.com; OpenBMC Maillist; IV00 Uri Trichter; IS20 Eyal Cohen
Subject: Re: KVM Support?



On 07/16/2018 10:01 AM, Avi Fishman wrote:
> Hi Eddie,
>
> Is it based on V4L or also VNC?
> Does it have HW compression or SW only?

Hi,

The driver interface is V4L2, though I am just using read() calls rather
than the streaming interface.
The network interface is VNC, directly sending JPEGs to the clients
rather than using the normal VNC framebuffer update methods.

Compression is done in HW, and then decompression at the client. So CPU
usage on the BMC is kept low, though bandwidth usage is pretty high
because it sends the whole frame every time. Seems to work with any VNC
client that supports JPEG compression.

I'm currently working through some input latency problems; seems the
bandwidth usage for the frames causes huge delays for sending the input
events from the client to the server. Other than that it's working well.

Thanks,
Eddie

>
> Thanks,
> Avi
> On Mon, Jul 16, 2018 at 5:03 PM Eddie James <eajames at linux.vnet.ibm.com> wrote:
>>
>>
>> On 07/16/2018 01:34 AM, AKASH G J wrote:
>>> Hi Team,
>>>
>>> Please someone share whether Keyboard Video Mouse (KVM) over IP
>>> implementation available in OpenBMC ?
>> Hi Akash,
>>
>> It's in development... If you want to help, let me know! I'll be
>> updating the mailing list with drivers, etc, when it's more functional.
>>
>> Thanks,
>> Eddie
>>
>>>
>>>
>>> Thanks and Regards,
>>>
>>> Akash



===========================================================================================
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.


More information about the openbmc mailing list