From: Liyu <raise.sail@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Li Yu <raise.sail@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Greg Kroah Hartman <greg@kroah.com>,
linux-usb-devel <linux-usb-devel@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
Vincent Legoll <vincentlegoll@gmail.com>,
"Zephaniah E. Hull" <warp@aehallh.com>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)
Date: Thu, 07 Dec 2006 13:25:24 +0800 [thread overview]
Message-ID: <4577A5C4.90703@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612061114560.28502@twin.jikos.cz>
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
prev parent reply other threads:[~2006-12-07 5:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 10:03 [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core) Li Yu
2006-12-06 10:24 ` Jiri Kosina
2006-12-06 14:24 ` Dmitry Torokhov
2006-12-06 14:38 ` Marcel Holtmann
2006-12-06 14:56 ` Dmitry Torokhov
2006-12-06 15:07 ` Marcel Holtmann
2006-12-06 15:00 ` Jiri Kosina
2006-12-06 15:13 ` Dmitry Torokhov
2006-12-06 15:18 ` Marcel Holtmann
2006-12-07 5:16 ` Greg KH
2006-12-06 15:18 ` Jiri Kosina
2006-12-06 15:25 ` Marcel Holtmann
2006-12-06 15:31 ` Dmitry Torokhov
2006-12-06 15:39 ` Jiri Kosina
2006-12-07 5:25 ` Liyu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4577A5C4.90703@gmail.com \
--to=raise.sail@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=vincentlegoll@gmail.com \
--cc=warp@aehallh.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox