search for: bus_usb

...mouse/tablet at the moment. Suggestions how to pick IDs? > > There will also be pass-through support, i.e. qemu > opening /dev/input/event<nr> and forwarding everything to the guest. > How should that be handled best? Copy all four from the host? Even > though the bustype is BUS_USB? Not sure this actually improves things > because the guest can match the device, or whenever this confuses apps > due to BUS_USB being applied to virtio devices ... Lemme give an example: We have databases in user-space, that allow applications to figure out the mouse DPI values of a devic...

...mouse/tablet at the moment. Suggestions how to pick IDs? > > There will also be pass-through support, i.e. qemu > opening /dev/input/event<nr> and forwarding everything to the guest. > How should that be handled best? Copy all four from the host? Even > though the bustype is BUS_USB? Not sure this actually improves things > because the guest can match the device, or whenever this confuses apps > due to BUS_USB being applied to virtio devices ... Lemme give an example: We have databases in user-space, that allow applications to figure out the mouse DPI values of a devic...

...ce. There are keyboard/mouse/tablet at the moment. Suggestions how to pick IDs? There will also be pass-through support, i.e. qemu opening /dev/input/event<nr> and forwarding everything to the guest. How should that be handled best? Copy all four from the host? Even though the bustype is BUS_USB? Not sure this actually improves things because the guest can match the device, or whenever this confuses apps due to BUS_USB being applied to virtio devices ... cheers, Gerd

Hi, > > There will also be pass-through support, i.e. qemu > > opening /dev/input/event<nr> and forwarding everything to the guest. > > How should that be handled best? Copy all four from the host? Even > > though the bustype is BUS_USB? Not sure this actually improves things > > because the guest can match the device, or whenever this confuses apps > > due to BUS_USB being applied to virtio devices ... > > Lemme give an example: We have databases in user-space, that allow > applications to figure out the mo...

...ce. There are keyboard/mouse/tablet at the moment. Suggestions how to pick IDs? There will also be pass-through support, i.e. qemu opening /dev/input/event<nr> and forwarding everything to the guest. How should that be handled best? Copy all four from the host? Even though the bustype is BUS_USB? Not sure this actually improves things because the guest can match the device, or whenever this confuses apps due to BUS_USB being applied to virtio devices ... cheers, Gerd

Hi, > > There will also be pass-through support, i.e. qemu > > opening /dev/input/event<nr> and forwarding everything to the guest. > > How should that be handled best? Copy all four from the host? Even > > though the bustype is BUS_USB? Not sure this actually improves things > > because the guest can match the device, or whenever this confuses apps > > due to BUS_USB being applied to virtio devices ... > > Lemme give an example: We have databases in user-space, that allow > applications to figure out the mo...

Hi (CC: Dmitry) On Thu, Mar 19, 2015 at 10:13 AM, Gerd Hoffmann <kraxel at redhat.com> wrote: > virtio-input is basically evdev-events-over-virtio, so this driver isn't > much more than reading configuration from config space and forwarding > incoming events to the linux input layer. > > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> > --- >

Hi (CC: Dmitry) On Thu, Mar 19, 2015 at 10:13 AM, Gerd Hoffmann <kraxel at redhat.com> wrote: > virtio-input is basically evdev-events-over-virtio, so this driver isn't > much more than reading configuration from config space and forwarding > incoming events to the linux input layer. > > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> > --- >