Hi Dmitry.
On Thu, Jan 30, 2014 at 10:29:45AM +0100, Christian Gmeiner wrote:
This driver is quite simple and only supports the Touch
Reporting Protocol.
Pretty clean and neat, just a few comments.
Thanks for the review.
Signed-off-by: Christian Gmeiner christian.gmei...@gmail.com
---
Here's a series of patches from Pierre-Loup and I that rework the xpad
driver to fix the issue where when a wireless xpad controller is plugged
in, 4 joystick devices are created, no matter how many are really
attached to the system. Pierre-Loup's patches fix this by dynamically
creating the
From: Pierre-Loup A. Griffais pgriff...@valvesoftware.com
Add the logic to set the LEDs on XBox Wireless controllers. Command
sequence found by sniffing the Windows data stream when plugging the
device in.
Signed-off-by: Pierre-Loup A. Griffais pgriff...@valvesoftware.com
Signed-off-by: Greg
From: Pierre-Loup A. Griffais pgriff...@valvesoftware.com
The LED number should not just be incremented every time, that doesn't
work, set the number based on the number it actually is.
Note, the joydev subsystem doesn't allow us to easily find out the minor
number, so we have to walk all
On Thu, Jan 30, 2014 at 11:31 PM, Stephan Mueller smuel...@chronox.de wrote:
Am Donnerstag, 30. Januar 2014, 22:50:25 schrieb Benjamin Tissoires:
Hi Benjamin,
Can you please help me how to do that? I install Windows in a KVM with
the mouse device as a USB-passthrough device -- shall I
Hi Chrisitian,
On Fri, Jan 31, 2014 at 12:40:19PM +0100, Christian Gmeiner wrote:
--- /dev/null
+++ b/drivers/input/touchscreen/ar1021_i2c.c
@@ -0,0 +1,201 @@
+/*
+ * Microchip AR1021 driver for I2C
+ *
+ * Author: Christian Gmeiner christian.gmei...@gmail.com
+ *
+ * License:
On Fri, Jan 31, 2014 at 09:15:21AM -0800, Dmitry Torokhov wrote:
Hi Chrisitian,
On Fri, Jan 31, 2014 at 12:40:19PM +0100, Christian Gmeiner wrote:
--- /dev/null
+++ b/drivers/input/touchscreen/ar1021_i2c.c
@@ -0,0 +1,201 @@
+/*
+ * Microchip AR1021 driver for I2C
+ *
+ *
Add the client_addr member to the hid_device struct for storing the client
address of a connected device.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
include/linux/hid.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/hid.h b/include/linux/hid.h
index
Add a new HIDIOCGRAWCLIENTADDR ioctl to hidraw for retrieving the client
address.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
drivers/hid/hidraw.c| 19 +++
include/uapi/linux/hidraw.h | 1 +
2 files changed, 20 insertions(+)
diff --git
Have hidp store the client device MAC address in client_addr
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
net/bluetooth/hidp/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net/bluetooth/hidp/core.c b/net/bluetooth/hidp/core.c
index 292e619..f256f33 100644
---
Add the HIDIOCGRAWCLIENTADDR ioctl to the hidraw sample program.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
samples/hidraw/hid-example.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/samples/hidraw/hid-example.c b/samples/hidraw/hid-example.c
index
Add support for setting the client address of a device in uhid.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
drivers/hid/uhid.c| 5 +
include/uapi/linux/uhid.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/drivers/hid/uhid.c b/drivers/hid/uhid.c
index
Currently there is no reliable way for a device module or hidraw application to
retrieve the client MAC address of the associated wireless device. This series
of patches adds a stable way of retrieving this information.
The first patch adds a new client_addr member to the hid_device struct.
Add the HIDIOCGRAWCLIENTADDR ioctl to the hidraw documentation.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
Documentation/hid/hidraw.txt | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/hid/hidraw.txt b/Documentation/hid/hidraw.txt
index 029e6cb..737fd1f 100644
On Fri, Jan 31, 2014 at 12:32 PM, Frank Praznik frank.praz...@oh.rr.com wrote:
Add the client_addr member to the hid_device struct for storing the client
address of a connected device.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
include/linux/hid.h | 1 +
1 file changed, 1
On Fri, Jan 31, 2014 at 12:32 PM, Frank Praznik frank.praz...@oh.rr.com wrote:
Add the HIDIOCGRAWCLIENTADDR ioctl to the hidraw sample program.
I would personally squash this one with the previous one, but this is
more a matter of taste IMO.
Signed-off-by: Frank Praznik
On Fri, Jan 31, 2014 at 12:32 PM, Frank Praznik frank.praz...@oh.rr.com wrote:
Add the HIDIOCGRAWCLIENTADDR ioctl to the hidraw documentation.
This one should be squashed with the previous one (same reason in 1/6)
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
On Fri, Jan 31, 2014 at 12:32 PM, Frank Praznik frank.praz...@oh.rr.com wrote:
Add a new HIDIOCGRAWCLIENTADDR ioctl to hidraw for retrieving the client
address.
Signed-off-by: Frank Praznik frank.praz...@oh.rr.com
---
drivers/hid/hidraw.c| 19 +++
In HID sensor hub, HID physical ids are used to represent different
sensors. For example physical id of 0x73 in usage page = 0x20, represents
an accelerometer. The HID sensor hub driver uses this physical ids to
create platform devices using MFD. There is 1:1 correspondence between
an phy id and a
On 1/31/2014 14:10, Benjamin Tissoires wrote:
Hi Frank,
just a quick review:
On Fri, Jan 31, 2014 at 12:32 PM, Frank Praznik frank.praz...@oh.rr.com wrote:
Currently there is no reliable way for a device module or hidraw application to
retrieve the client MAC address of the associated
On Fri, Jan 31, 2014 at 3:04 PM, Frank Praznik frank.praz...@oh.rr.com wrote:
On 1/31/2014 14:10, Benjamin Tissoires wrote:
Hi Frank,
just a quick review:
On Fri, Jan 31, 2014 at 12:32 PM, Frank Praznik frank.praz...@oh.rr.com
wrote:
Currently there is no reliable way for a device module
On Wed, Jan 29, 2014 at 10:35 AM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Wed, Jan 29, 2014 at 4:28 PM, Frank Praznik frank.praz...@oh.rr.com
wrote:
Add David Herrmann's documentation for the new low-level HID transport driver
functions.
Signed-off-by: Frank Praznik
Am Freitag, 31. Januar 2014, 05:31:53 schrieb Stephan Mueller:
Hi,
The middle mouse button works in Linux, but very differently than you may
expect: I still do not see any events when only pressing the middle mouse
button.
Out of luck, I pressed the middle button and moved the mouse. And
23 matches
Mail list logo
