linux-kernel - Re: [PATCH] HID: use generic driver for ThingM blink(1) if !CONFIG_HID

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1508031124400.925@pobox.suse.cz>
Date:	Mon, 3 Aug 2015 11:25:12 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.com>
To:	Reilly Grant <reillyg@...omium.org>
cc:	Pavel Machek <pavel@....cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] HID: use generic driver for ThingM blink(1) if
 !CONFIG_HID_THINGM

On Sun, 2 Aug 2015, Reilly Grant wrote:

> There is existing user space software (not just mine, also from the
> manufacturer) that does not use the special driver and instead uses hidraw
> or usbdevice_fs to control the device. LED class driver support for this
> device is useful but should be optional.

Is there any problem for the userspace software to unbind the kernel 
driver first?

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/