linux-kernel - Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

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

Message-ID: <4577A5C4.90703@gmail.com>
Date:	Thu, 07 Dec 2006 13:25:24 +0800
From:	Liyu <raise.sail@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	Li Yu <raise.sail@...il.com>,
	Dmitry Torokhov <dmitry.torokhov@...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>,
	Marcel Holtmann <marcel@...tmann.org>
Subject: Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

Jiri Kosina wrote:
> Do you think that you could wait a little bit more, after the split has 
> been done? (it's currently planned approximately after 2.6.20-rc1). It 
> seems to me that your patches will apply almost cleanly on top of the 
> split patches (you will have to change the pathnames, of course).  
Of course, I interest to wait this. If they have other weakless, tell me
too.
I also think the HID split plan is a great idea.

Dmitry wrote:
> I still have the same objection - the "simple'" code will have to be
> compiled into the driver instead of being a separate module and
> eventyally will lead to a monster-size HID module. We have this issue
> with psmouse to a degree but with HID the growth potential is much
> bigger IMO.

As you guess;), I do not agree with your words very much. We can image,
there
are many devices use some HID base layer, however they even do not merge
into
mainstream kernel source tree for some reasons. and in fact, I do not
like the
mainstream kernel source tree include every drivers. For such devices
out of core,
we should have such feature that let developer write such driver
quickly. I think
it allows many monster-size driver modules is a better means than
all-in-one.But we
need resolve /dev/input/event? switching problem in principle first,
else we still
encounter same problem when new hidraw come.

Good luck.

-Li Yu
www.co-create.com.cn

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