On Tue, Sep 02, 2014 at 04:50:53PM +0200, David Herrmann wrote:
> Hi
>
> On Tue, Sep 2, 2014 at 4:40 PM, Hans de Goede wrote:
> > On 09/02/2014 02:55 PM, David Herrmann wrote:
> >> Hi
> >>
> >> On Tue, Sep 2, 2014 at 2:43 PM, Hans de Goede wrote:
> >>> Hi,
> >>>
> >>> It is useful for userspace
On Tue, Sep 02, 2014 at 10:38:34AM -0400, Benjamin Tissoires wrote:
> On Sep 02 2014 or thereabouts, Hans de Goede wrote:
> > I've not done a full audit of all mouse drivers, I noticed these ones were
> > missing the POINTER property while working on the POINTING_STICK property.
>
> I am not sure
On Tue, Sep 02, 2014 at 02:43:23PM +0200, Hans de Goede wrote:
> It is useful for userspace to know that there not dealing with a regular
> mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
> can e.g. automatically enable middle button scrollwheel emulation.
>
> It is im
>From Jiri Kosina , Tue, Sep 02, 2014 at 11:32:30PM +0200:
> On Tue, 2 Sep 2014, Benjamin Tissoires wrote:
>
> > > Whenever either disconnecting the USB device or simply rmmod'ing the
> > > module
> > > (even when not in use), I get a kernel panic. I haven't managed to
> > > capture a
> > > bac
On Tue, 2 Sep 2014, Benjamin Tissoires wrote:
> > Whenever either disconnecting the USB device or simply rmmod'ing the module
> > (even when not in use), I get a kernel panic. I haven't managed to capture
> > a
> > backtrace, but at least the first two lines were saved after an rmmod:
> >
> > 1
>From Benjamin Tissoires , Tue, Sep 02, 2014 at
>03:58:08PM -0400:
> Hi,
>
> On 09/02/2014 01:46 PM, Dylan Alex Simon wrote:
> > Whenever either disconnecting the USB device or simply rmmod'ing the module
> > (even when not in use), I get a kernel panic. I haven't managed to capture
> > a
> > b
Hi,
On 09/02/2014 01:46 PM, Dylan Alex Simon wrote:
> Whenever either disconnecting the USB device or simply rmmod'ing the module
> (even when not in use), I get a kernel panic. I haven't managed to capture a
> backtrace, but at least the first two lines were saved after an rmmod:
>
> 18:53:17 k
Whenever either disconnecting the USB device or simply rmmod'ing the module
(even when not in use), I get a kernel panic. I haven't managed to capture a
backtrace, but at least the first two lines were saved after an rmmod:
18:53:17 kernel: thingm 0003:27B8:01ED.0004: hidraw3: USB HID v1.01 Devic
Sorry,
I repost this email because I didn't see it in the mailing list
NR
G.Baroncelli
Forwarded Message
Subject: Driver for Logitech M560
Date: Mon, 01 Sep 2014 21:20:20 +0200
From: Goffredo Baroncelli
Reply-To: kreij...@inwind.it
To: Benjamin Tissoires
CC: Nestor Lopez Casado
On 07/29/2014 01:26 PM, Stephen Warren wrote:
On 07/29/2014 11:06 AM, Nick Dyer wrote:
On 29/07/14 17:16, Stephen Warren wrote:
...
I also found that removing the module (even without attempting a FW
update) yields:
After attempted FW update via sysfs:
root@localhost:~# rmmod ./atmel_mxt_ts
Hi
On Tue, Sep 2, 2014 at 4:40 PM, Hans de Goede wrote:
> On 09/02/2014 02:55 PM, David Herrmann wrote:
>> Hi
>>
>> On Tue, Sep 2, 2014 at 2:43 PM, Hans de Goede wrote:
>>> Hi,
>>>
>>> It is useful for userspace to know that they're not dealing with a regular
>>> mouse but rather with a pointing
On Sep 02 2014 or thereabouts, Hans de Goede wrote:
> I've not done a full audit of all mouse drivers, I noticed these ones were
> missing the POINTER property while working on the POINTING_STICK property.
I am not sure about this one. INPUT_PROP_POINTER is the default behavior
when no properties
On Sep 02 2014 or thereabouts, Hans de Goede wrote:
> It is useful for userspace to know that there not dealing with a regular
> mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
> can e.g. automatically enable middle button scrollwheel emulation.
>
> It is impossible to
Hi David,
On Sep 02 2014 or thereabouts, David Herrmann wrote:
> Hi
>
> On Tue, Sep 2, 2014 at 2:43 PM, Hans de Goede wrote:
> > Hi,
> >
> > It is useful for userspace to know that they're not dealing with a regular
> > mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
Hi
On Tue, Sep 2, 2014 at 2:43 PM, Hans de Goede wrote:
> Hi,
>
> It is useful for userspace to know that they're not dealing with a regular
> mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
> can e.g. automatically enable middle button scrollwheel emulation.
>
> It i
It is useful for userspace to know that there not dealing with a regular
mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
can e.g. automatically enable middle button scrollwheel emulation.
It is impossible to tell the difference from the evdev info without resorting
to
I've not done a full audit of all mouse drivers, I noticed these ones were
missing the POINTER property while working on the POINTING_STICK property.
Signed-off-by: Hans de Goede
---
drivers/input/mouse/alps.c | 1 +
drivers/input/mouse/elantech.c | 1 +
drivers/input/mouse/psmouse
Hi,
It is useful for userspace to know that they're not dealing with a regular
mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
can e.g. automatically enable middle button scrollwheel emulation.
It is impossible to tell the difference from the evdev info without resort
On Sep 2, 2014, at 9:43 AM, Daniel Mack wrote:
> On 09/02/2014 08:32 AM, Klaus Goger wrote:
>> Use the correct register address for Calibration Active and Interrupt
>> Enable
>>
>> Signed-off-by: Klaus Goger
>
> These register definitions are currently unused, but your fix is
> correct. Just cu
On 09/02/2014 08:32 AM, Klaus Goger wrote:
> Use the correct register address for Calibration Active and Interrupt
> Enable
>
> Signed-off-by: Klaus Goger
These register definitions are currently unused, but your fix is
correct. Just curious - are you planning to send patches that make use
of th
20 matches
Mail list logo
