linux-kernel - Re: [DOC] The documentation for HID Simple Driver Interface 0.5.0

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: <d120d5000703060525x26da3274r5cc4ac724e1f0beb@mail.gmail.com>
Date:	Tue, 6 Mar 2007 08:25:59 -0500
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Marcel Holtmann" <marcel@...tmann.org>
Cc:	"Li Yu" <raise.sail@...il.com>,
	"Greg Kroah Hartman" <greg@...ah.com>,
	linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>,
	"Vincent Legoll" <vincentlegoll@...il.com>,
	"Zephaniah E. Hull" <warp@...allh.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Harold Sargeant" <harold-sargeant@...world.com>,
	liyu <liyu@...ss.com.cn>
Subject: Re: [DOC] The documentation for HID Simple Driver Interface 0.5.0

Hi Marcel,

On 3/5/07, Marcel Holtmann <marcel@...tmann.org> wrote:
> Hi Dmitry,
>
> > > This also means that the current keyboard and mouse
> > > input devices will become a HID driver.
> >
> > Are you talking about usbmouse and usbkbd?
>
> no, because if I recall correctly these are the boot mode drivers and
> actually not used at all in any modern distribution.
>
> For me the task of converting HID reports into input events shouldn't be
> actually the job of the HID core layer. My understanding is that the HID
> core should support multiple transport layers. This is currently
> achieved through the hid_device abstraction and used by the USB and by
> the Bluetooth subsystem. This is the lower interface to HID. On the
> upper interface I like to see a driver like interface. So we can
> register specific drivers that can handle specific use cases or vendor
> specific reports. For standard keyboard and mouse reports we however
> should have a standard driver that can handle most of them.
>
> For identification we actually do have the bus type, vendor id and
> product id available. We also can register drivers for specific report
> ids or usages.
>
> I do like the HID simple driver idea, but it is not a simple driver, it
> should be a generic driver interface.
>

Ah, OK. Then we are in complete agreement ;)

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