linux-kernel - Re: How to use an usb interface than is claimed by 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0701211821530.21127@twin.jikos.cz>
Date:	Sun, 21 Jan 2007 18:28:02 +0100 (CET)
From:	Jiri Kosina <jikos@...os.cz>
To:	Ivan Ukhov <uvsoft@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: How to use an usb interface than is claimed by HID?

On Sun, 21 Jan 2007, Jiri Kosina wrote:

> > It's a tiny driver and it hardy can be a part of the mainline kernel 
> > because of its useless for everyone but me, beside I don't want to 
> > make someone modify the kernel code.
> Then, when this is a non-standard situation anyway, would calling 
> hid_disconnect() for the usb_interface of your driver be enough?

.. which wouldn't help you either, supposing that you don't want to touch 
the kernel sources at all, because this function is unexported and static.

So I think that there is no straightforward way, sorry.

Is this a device that doesn't exist anywhere else than on your table? I 
still think that putting the code in kernel (if possible) and blacklisting 
the device on the hid_blacklist[] is the simplest way.

The other possibility is writing the driver completely in userspace, using 
libhid/hiddev. Would that suit your needs?

-- 
Jiri Kosina
-
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/