On Thu, Apr 19, 2018 at 02:44:19PM +0300, Oleksandr Andrushchenko wrote:Ok, but in order to preserve the default behavior, e.g.
On 04/19/2018 02:25 PM, Juergen Gross wrote:Why do you consider this implementation specific? How other guests
On 18/04/18 17:04, Oleksandr Andrushchenko wrote:Well, I would prefer not to touch anything outside Linux and
From: Oleksandr Andrushchenko <oleksandr_andrushchenko@xxxxxxxx>Why don't you want to go that route for keyboard and mouse, too?
It is now only possible to control if multi-touch virtual device
is created or not (via the corresponding XenStore entries),
but keyboard and pointer devices are always created.
Or does this really make no sense?
this driver. And these settings seem to be implementation specific.
So, this is why introduce Linux module parameters and don't extend
the kbdif protocol.
decide to forego creation of relative pointer device or keyboard-like
You already have "features" for absolute pointing device and multitouch,
so please extend the protocol properly so you indeed do not code
something implementation-specific (i.e. module parameters).