Displaying 4 results from an estimated 4 matches for "rundom".
Did you mean:
random
2015 Mar 19
3
[PATCH 0/1] Add virtio-input driver.
On Do, 2015-03-19 at 14:35 +0100, Michael S. Tsirkin wrote:
> On Thu, Mar 19, 2015 at 10:13:10AM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > This patch adds a virtio driver for input devices.
> >
> > Specification:
> > https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input
> >
2015 Mar 19
3
[PATCH 0/1] Add virtio-input driver.
On Do, 2015-03-19 at 14:35 +0100, Michael S. Tsirkin wrote:
> On Thu, Mar 19, 2015 at 10:13:10AM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > This patch adds a virtio driver for input devices.
> >
> > Specification:
> > https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input
> >
2015 Mar 19
0
[PATCH 0/1] Add virtio-input driver.
...> >
> > Which version?
>
> Latest. As far I know there never ever have been incompatible changes
> to the interface, and given this is userspace/kernel abi I don't expect
> that to happen in the future.
More events are added though, are they not? And distros backport rundom
subsets.
So I worry: what happens e.g. if you migrate between hosts which expose
slightly different subsets of events?
Might e.g. a button get stuck because button-press event was
sent but button-release wasn't?
> > How will non-linux guests know what to implement?
>
> There ar...
2015 Mar 19
0
[PATCH 0/1] Add virtio-input driver.
...> >
> > Which version?
>
> Latest. As far I know there never ever have been incompatible changes
> to the interface, and given this is userspace/kernel abi I don't expect
> that to happen in the future.
More events are added though, are they not? And distros backport rundom
subsets.
So I worry: what happens e.g. if you migrate between hosts which expose
slightly different subsets of events?
Might e.g. a button get stuck because button-press event was
sent but button-release wasn't?
> > How will non-linux guests know what to implement?
>
> There ar...