On Wed, 8 Mar 2017, Benjamin Tissoires wrote:
> It looks like a bunch of devices do not like to be polled for their
> reports at init time. When you look into the details, it seems that for
> those that are requiring the quirk HID_QUIRK_NO_INIT_REPORTS, the driver
> fails to retrieve part of
On Wed, 8 Mar 2017, Benjamin Tissoires wrote:
> It looks like a bunch of devices do not like to be polled for their
> reports at init time. When you look into the details, it seems that for
> those that are requiring the quirk HID_QUIRK_NO_INIT_REPORTS, the driver
> fails to retrieve part of
It looks like a bunch of devices do not like to be polled
for their reports at init time. When you look into the details,
it seems that for those that are requiring the quirk
HID_QUIRK_NO_INIT_REPORTS, the driver fails to retrieve part
of the features/inputs while others (more generic) work.
IMO,
It looks like a bunch of devices do not like to be polled
for their reports at init time. When you look into the details,
it seems that for those that are requiring the quirk
HID_QUIRK_NO_INIT_REPORTS, the driver fails to retrieve part
of the features/inputs while others (more generic) work.
IMO,
4 matches
Mail list logo
