search for: input_devic

Displaying 20 results from an estimated 63 matches for "input_devic".

Did you mean: input_device
2011 Apr 01
4
[PATCH 1/5] staging: hv: change camel case funct names to lower case funct in hv_mouse
...dev, struct hv_input_dev_info static void inputreport_callback(struct hv_device *dev, void *packet, u32 len); static void reportdesc_callback(struct hv_device *dev, void *packet, u32 len); -static struct mousevsc_dev *AllocInputDevice(struct hv_device *Device) +static struct mousevsc_dev *alloc_input_device(struct hv_device *Device) { struct mousevsc_dev *inputDevice; @@ -211,7 +211,7 @@ static struct mousevsc_dev *AllocInputDevice(struct hv_device *Device) /* * Set to 2 to allow both inbound and outbound traffics - * (ie GetInputDevice() and MustGetInputDevice()) to proceed. + * (ie ge...
2011 Apr 01
4
[PATCH 1/5] staging: hv: change camel case funct names to lower case funct in hv_mouse
...dev, struct hv_input_dev_info static void inputreport_callback(struct hv_device *dev, void *packet, u32 len); static void reportdesc_callback(struct hv_device *dev, void *packet, u32 len); -static struct mousevsc_dev *AllocInputDevice(struct hv_device *Device) +static struct mousevsc_dev *alloc_input_device(struct hv_device *Device) { struct mousevsc_dev *inputDevice; @@ -211,7 +211,7 @@ static struct mousevsc_dev *AllocInputDevice(struct hv_device *Device) /* * Set to 2 to allow both inbound and outbound traffics - * (ie GetInputDevice() and MustGetInputDevice()) to proceed. + * (ie ge...
2015 Mar 24
1
[PATCH v3] Add virtio-input driver.
On Tue, Mar 24, 2015 at 06:22:36PM +0100, Michael S. Tsirkin wrote: > On Tue, Mar 24, 2015 at 09:23:37AM -0700, Dmitry Torokhov wrote: > > On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > > > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > > > > virtio-input is basically evdev-events-over-virtio, so this driver isn't > >
2015 Mar 24
1
[PATCH v3] Add virtio-input driver.
On Tue, Mar 24, 2015 at 06:22:36PM +0100, Michael S. Tsirkin wrote: > On Tue, Mar 24, 2015 at 09:23:37AM -0700, Dmitry Torokhov wrote: > > On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > > > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > > > > virtio-input is basically evdev-events-over-virtio, so this driver isn't > >
2011 Sep 08
25
[PATCH 0000/0025] Staging: hv: Driver cleanup
Address Greg's VmBus audit comments: 1) Leverage driver_data field in struct hv_vmbus_device_id to simplify driver code. 2) Make the util driver conform to the Linux Driver Model. 3) Get rid of the ext field in struct hv_device by using the driver specific data functionality. 4) Other general cleanup. Regards, K. Y
2011 Sep 08
25
[PATCH 0000/0025] Staging: hv: Driver cleanup
Address Greg's VmBus audit comments: 1) Leverage driver_data field in struct hv_vmbus_device_id to simplify driver code. 2) Make the util driver conform to the Linux Driver Model. 3) Get rid of the ext field in struct hv_device by using the driver specific data functionality. 4) Other general cleanup. Regards, K. Y
2015 Mar 24
2
[PATCH v3] Add virtio-input driver.
On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann 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
2015 Mar 24
2
[PATCH v3] Add virtio-input driver.
On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann 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
2015 Mar 20
2
[PATCH v2] Add virtio-input driver.
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> --- MAINTAINERS | 6 + drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 +
2015 Mar 20
2
[PATCH v2] Add virtio-input driver.
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> --- MAINTAINERS | 6 + drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 +
2015 Mar 19
0
[PATCH 1/1] Add virtio-input driver.
On Thu, Mar 19, 2015 at 01:29:49PM +0100, David Herrmann wrote: > 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
2015 Mar 19
0
[PATCH 1/1] Add virtio-input driver.
On Thu, Mar 19, 2015 at 01:29:49PM +0100, David Herrmann wrote: > 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
2015 Mar 19
5
[PATCH 1/1] Add virtio-input driver.
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> > --- >
2015 Mar 19
5
[PATCH 1/1] Add virtio-input driver.
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> > --- >
2015 Mar 19
5
[PATCH 0/1] Add virtio-input driver.
Hi, This patch adds a virtio driver for input devices. Specification: https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input https://www.kraxel.org/virtio/virtio-v1.0-csprd03-virtio-input.html#x1-2640007 Qemu patches; https://lists.gnu.org/archive/html/qemu-devel/2015-03/threads.html#03973 Gerd Hoffmann (1): Add virtio-input driver. drivers/virtio/Kconfig | 10 ++
2015 Mar 19
5
[PATCH 0/1] Add virtio-input driver.
Hi, This patch adds a virtio driver for input devices. Specification: https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input https://www.kraxel.org/virtio/virtio-v1.0-csprd03-virtio-input.html#x1-2640007 Qemu patches; https://lists.gnu.org/archive/html/qemu-devel/2015-03/threads.html#03973 Gerd Hoffmann (1): Add virtio-input driver. drivers/virtio/Kconfig | 10 ++
2015 Mar 19
0
[PATCH 1/1] Add virtio-input driver.
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> --- drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_input.c | 313
2015 Mar 19
0
[PATCH 1/1] Add virtio-input driver.
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> --- drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_input.c | 313
2015 Mar 24
0
[PATCH v3] Add virtio-input driver.
On Tue, Mar 24, 2015 at 09:23:37AM -0700, Dmitry Torokhov wrote: > On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > > > virtio-input is basically evdev-events-over-virtio, so this driver isn't > > > much more than reading configuration from config space and forwarding > >
2015 Mar 24
0
[PATCH v3] Add virtio-input driver.
On Tue, Mar 24, 2015 at 09:23:37AM -0700, Dmitry Torokhov wrote: > On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > > > virtio-input is basically evdev-events-over-virtio, so this driver isn't > > > much more than reading configuration from config space and forwarding > >