On Thu, Jul 09, 2015 at 01:09:35PM -0700, Bill Spitzak wrote:
> On Wed, Jul 8, 2015 at 8:29 PM, Peter Hutterer
> wrote:
>
> >
> > good point, that does seem to be the best approach here.
> > the resolution claimed was 800 dpi -> 31 u/mm.
> > I'm a bit worried about doing this though, the reporter
On Wed, Jul 8, 2015 at 8:29 PM, Peter Hutterer
wrote:
>
> good point, that does seem to be the best approach here.
> the resolution claimed was 800 dpi -> 31 u/mm.
> I'm a bit worried about doing this though, the reporter in
> https://bugs.freedesktop.org/show_bug.cgi?id=90101
> measured a touchp
On Wed, Jul 08, 2015 at 02:34:43PM +0200, Hans de Goede wrote:
> Hi,
>
> On 01-07-15 08:08, Peter Hutterer wrote:
> >Only firmware v4 (and probably whatever comes in the future) have resolution
> >set, for the first couple of touchpads we need size hints. Add a callout that
> >looks at the propert
Hi,
On 01-07-15 08:08, Peter Hutterer wrote:
Only firmware v4 (and probably whatever comes in the future) have resolution
set, for the first couple of touchpads we need size hints. Add a callout that
looks at the properties on the touchpad and decides the firmware version.
The udev/hwdb is two-
On Wed, Jul 01, 2015 at 04:08:49PM +1000, Peter Hutterer wrote:
> Only firmware v4 (and probably whatever comes in the future) have resolution
> set, for the first couple of touchpads we need size hints. Add a callout that
> looks at the properties on the touchpad and decides the firmware version.
Only firmware v4 (and probably whatever comes in the future) have resolution
set, for the first couple of touchpads we need size hints. Add a callout that
looks at the properties on the touchpad and decides the firmware version.
The udev/hwdb is two-stage: the callout sets LIBINPUT_MODEL_FIRMWARE_
