linux-kernel - Re: HID bus prototype

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: <Pine.LNX.4.64.0704101136330.13232@jikos.suse.cz>
Date:	Tue, 10 Apr 2007 11:40:03 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Li Yu <raise.sail@...il.com>
Cc:	yanghong@...ss.com.cn,
	linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>,
	hongzhiyi@...ss.com.cn, Marcel Holtmann <marcel@...tmann.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: HID bus prototype - 20070408

On Sun, 8 Apr 2007, Li Yu wrote:

> 	The attachment is the latest HID bus prototype. It have such changes:
> 	0. Move the hidp directory from net/bluetooth/ to drivers/hid/.

Hi Li,

we have been discussing this with Marcel previously, and the decission was 
to let the hidp code where it is right now, due to it being very closely 
connected to the bluetooth network stack.

> 	1. HID/Bluetooth support, ONLY FOR HIGHLY EXPERIMENT. I have no 
>          any such device to test yet.

I didn't have time yet to review the patch you sent previously, but I 
don't still quite understand why does the transport layer matter here? The 
generic HID layer, as it is in kernel now, makes an abstraction in a way 
that the HID-specific drivers should not care about the underlying 
transport layer.

> 	I am sorry for it is not in patch form.

That's quite unfortunate. I'll try to review it nevertheless, but it'd be 
much more convenient if you manage to send a patch.

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/