[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <452AD2D9.3090001@gmail.com>
Date: Tue, 10 Oct 2006 01:53:13 +0300
From: Anssi Hannula <anssi.hannula@...il.com>
To: Dmitry Torokhov <dtor@...ightbb.com>
CC: "raise.sail@...il.com" <raise.sail@...il.com>,
greg <greg@...ah.com>, Randy Dunlap <rdunlap@...otime.net>,
LKML <linux-kernel@...r.kernel.org>,
linux-usb-devel <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] [PATCH] usb/hid: The HID Simple Driver Interface
0.3.2 (core)
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@...il.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
-
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/
Powered by blists - more mailing lists