From: Anssi Hannula <anssi.hannula@gmail.com>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: "raise.sail@gmail.com" <raise.sail@gmail.com>,
greg <greg@kroah.com>, Randy Dunlap <rdunlap@xenotime.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb-devel <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] [PATCH] usb/hid: The HID Simple Driver Interface 0.3.2 (core)
Date: Tue, 10 Oct 2006 01:53:13 +0300 [thread overview]
Message-ID: <452AD2D9.3090001@gmail.com> (raw)
In-Reply-To: <200610082342.26110.dtor@insightbb.com>
Dmitry Torokhov wrote:
> On Sunday 08 October 2006 14:51, Anssi Hannula wrote:
>> (I didn't get Dmitry's original mail, so replying here)
>>
>> raise.sail@gmail.com wrote:
>>> Dmitry Torokhov wrote:
>>>> Then there is issue with automatic loading of these sub-drivers. How
>>>> do they get loaded? Or we force everything to be built-in making HID
>>>> module very fat (like psmouse got pretty fat, but with HID prtential
>>>> for it to get very fat is much bigger).
>>>>
>>>> The better way would be to split hid-input into a library module that
>>>> parses hid usages and reports and is shared between device-specific
>>>> modules that are "real" drivers (usb-drivers, not hid-sub-drivers).
>> One possibility is to do that with symbol_request() and friends. That
>> would not be pretty though, imho.
>>
>> DVB subsystem uses that currently to load frontend modules dynamically,
>> see dvb_attach() and dvb_frontend_detach() in
>> drivers/media/dvb/dvb-core/dvbdev.h and
>> drivers/media/dvb/dvb-core/dvb_frontend.c.
>>
>
> Unfortunately this does not quite work when hid is built-in and the rest
> are modules :(
>
How so? I see nothing obvious.
--
Anssi Hannula
next prev parent reply other threads:[~2006-10-09 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 8:24 [PATCH] usb/hid: The HID Simple Driver Interface 0.3.2 (core) raise.sail
2006-09-29 16:59 ` Randy Dunlap
2006-09-29 17:35 ` Dmitry Torokhov
2006-10-08 3:07 ` raise.sail
2006-10-08 12:41 ` [linux-usb-devel] " Zephaniah E. Hull
2006-10-08 14:09 ` Dmitry Torokhov
2006-10-09 3:28 ` Liyu
2006-10-09 3:28 ` Liyu
2006-10-08 18:51 ` Anssi Hannula
2006-10-09 3:35 ` Liyu
2006-10-09 22:52 ` Anssi Hannula
2006-10-09 3:42 ` Dmitry Torokhov
2006-10-09 22:53 ` Anssi Hannula [this message]
2006-10-10 5:15 ` Dmitry Torokhov
2006-10-10 7:08 ` Liyu
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=452AD2D9.3090001@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=dtor@insightbb.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=raise.sail@gmail.com \
--cc=rdunlap@xenotime.net \
/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