Hi
On Wed, Jan 8, 2014 at 5:26 PM, Jiri Kosina wrote:
> On Wed, 8 Jan 2014, David Herrmann wrote:
>
>> >> > I think this is valuable because it will give a better understanding of
>> >> > the
>> >> > actual mapping hardware/inputs. Like a touchscreen with pen + touch
>> >> > will have
>> >> > t
On Wed, 8 Jan 2014, David Herrmann wrote:
> >> > I think this is valuable because it will give a better understanding of
> >> > the
> >> > actual mapping hardware/inputs. Like a touchscreen with pen + touch will
> >> > have
> >> > the same hid parent, and I expect X/Wayland to be able to detect
Hi Jiri
On Fri, Dec 20, 2013 at 11:36 PM, Jiri Kosina wrote:
> On Thu, 19 Dec 2013, David Herrmann wrote:
>
>> wrote:
>> > we used to set the parent of the input device as the parent of
>> > the hid bus. This was introduced when we created hid as a real bus, and
>> > to keep backward compatibili
On Thu, 19 Dec 2013, David Herrmann wrote:
> wrote:
> > we used to set the parent of the input device as the parent of
> > the hid bus. This was introduced when we created hid as a real bus, and
> > to keep backward compatibility. Now, it's time to proper set the parent
> > so that sysfs has an i
Hi
On Thu, Dec 19, 2013 at 5:05 PM, Benjamin Tissoires
wrote:
> we used to set the parent of the input device as the parent of
> the hid bus. This was introduced when we created hid as a real bus, and
> to keep backward compatibility. Now, it's time to proper set the parent
> so that sysfs has an
we used to set the parent of the input device as the parent of
the hid bus. This was introduced when we created hid as a real bus, and
to keep backward compatibility. Now, it's time to proper set the parent
so that sysfs has an idea of which input device is attached to
which hid device.
Signed-off
6 matches
Mail list logo
