On Tue, Nov 04, 2014 at 09:00:06AM -0600, Derek Foreman wrote:
> On 03/11/14 09:51 PM, Peter Hutterer wrote:
> > On Mon, Nov 03, 2014 at 11:56:59AM +0100, David Herrmann wrote:
> >> Hi
> >>
> >> On Fri, Oct 31, 2014 at 5:33 AM, Peter Hutterer
> >> wrote:
> >>> On Thu, Oct 30, 2014 at 04:34:12PM -0
On 03/11/14 09:51 PM, Peter Hutterer wrote:
> On Mon, Nov 03, 2014 at 11:56:59AM +0100, David Herrmann wrote:
>> Hi
>>
>> On Fri, Oct 31, 2014 at 5:33 AM, Peter Hutterer
>> wrote:
>>> On Thu, Oct 30, 2014 at 04:34:12PM -0500, Derek Foreman wrote:
The acceleration filter currently isn't partic
Hi
On Tue, Nov 4, 2014 at 4:51 AM, Peter Hutterer wrote:
> On Mon, Nov 03, 2014 at 11:56:59AM +0100, David Herrmann wrote:
>> I haven't spent much time thinking it through, but so far I'd prefer a
>> solid, but basic, heuristic to guess the DPI and then use hwdb for
>> anything that doesn't fit.
Hi
On Fri, Oct 31, 2014 at 5:33 AM, Peter Hutterer
wrote:
> On Thu, Oct 30, 2014 at 04:34:12PM -0500, Derek Foreman wrote:
>> The acceleration filter currently isn't particularly pleased with gaming
>> mice.
>>
>> They generally have high DPI (can be over 8000 DPI) and can have high update
>> ra
On Thu, Oct 30, 2014 at 04:34:12PM -0500, Derek Foreman wrote:
> The acceleration filter currently isn't particularly pleased with gaming mice.
>
> They generally have high DPI (can be over 8000 DPI) and can have high update
> rates (1000+ per second). This can result in the accel curve being bia
The acceleration filter currently isn't particularly pleased with gaming mice.
They generally have high DPI (can be over 8000 DPI) and can have high update
rates (1000+ per second). This can result in the accel curve being biased
heavily towards the high points on the accel curve.
This patch set
