kJ4iWdfEUUXTp5y32AC4
>> LRNVlzSJrP76/zSZWmz1vlG8ZzO68CWMpU48aOJYggM5nTFRqQvuDYMctP1x0XcOMPGZ
>> Ti4Q==
>> X-Gm-Message-State:
>> AOPr4FWjen4+Tr0Nl3aoO4eF8gbDP9sc8FqDtNTsrXsHl/7I+Zmd++0Vn4Kk+/9vPL+EuG9EA/DzTRMtx+nQEQ==
>> X-Received: by 10.129.161.19 with
00:03 -0500
>> From: Chase Davis
>>
>> Forgive my ignorance, but what bearing does -release and -current have
>> on whether or not the HID is found by the match function?
>
> Because the code that the HID matching depends on was reworked
> after 5.9 was released.
--
Chase Davis
Forgive my ignorance, but what bearing does -release and -current have
on whether or not the HID is found by the match function?
On Wed, May 4, 2016 at 9:58 AM, Mark Kettenis wrote:
>> Date: Wed, 4 May 2016 09:41:18 -0500
>> From: Chase Davis
>>
>> It looks like other
It looks like other devices have: Name (_HID, EisaId ("PNP0501")
instead of: Name (_HID, "SEL0002")
I'm not sure what the significance of EisaId is, but it doesn't show
up for our device.
On Wed, May 4, 2016 at 9:34 AM, Chase Davis wrote:
> Mike,
>
> Yes
