linux-kernel - Re: Question re hiddev

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>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0703131048100.14144@twin.jikos.cz>
Date:	Tue, 13 Mar 2007 10:54:15 +0100 (CET)
From:	Jiri Kosina <jikos@...os.cz>
To:	Robert Marquardt <marquardt@...emercs.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Question re hiddev

On Tue, 13 Mar 2007, Robert Marquardt wrote:

> > as there are many Bluetooth devices with conform to HID specification
> Namely the Wii controller which is already happily used by many programmers
> through Windows HID API.

Hi Robert,

not only this piece of hardware, but many others - for example almost all 
Bluetooth keyboards and mice are capable of working both in HID and HCI 
modes, etc. The layer introduced in 2.6.20 gives them the possibility of 
using full reporting facilities of the HID layer.

> > There are still pending issues though, one of them being converting 
> > the HID layer to bus, so that individual device that don't wish the 
> > certain device to be handled by generic HID code, register on this HID 
> > bus and handle the HID events from given device in a unified way (for 
> > example current Wacom driver would use this facility, among other). As 
> > a bonus, this is going to shrink the hid_blacklist, which currently 
> > has to contain all devices for which there are specialized drivers.
> Ah, this means our iowarrior driver will be shortlived.

I don't think so. Firstly, it will take some time until the HID layer is 
converted to bus, as I have another things pending. Secondly, the 
iowarrior driver will still be needed to handle the HW-specific reports 
that won't be handled by the generic HID layer, it would only have to be 
changed to register through the HID bus.

> Do you know the Windows HID API? It would be nice to take it into 
> account so that a compatible API can be written. 

No, I don't know Windows HID api at all. Is it worth looking at?

> Mainly this needs a way to add a ReportID of 0x00 to reports from 
> devices without ReportIDs and access to the HID descriptor so the usages 
> can be extracted from a report.

Just a sidenote - this is in fact what I am currently implementing also 
for the new hidraw userspace interface.

Thanks,

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