Re: [PATCH 26/31] usb: Auto-load cdc_acm module when device opened.

From: Kay Sievers
Date: Tue Mar 10 2009 - 14:34:21 EST


On Tue, Mar 10, 2009 at 18:18, Scott James Remnant <scott@xxxxxxxxxxxxx> wrote:
> On Tue, 2009-03-10 at 10:08 -0700, Greg KH wrote:
>> On Mon, Mar 02, 2009 at 06:46:15PM +0000, Scott James Remnant wrote:
>> > The cdc_acm module is missing the char-major-166-* alias that would
>> > cause it to be auto-loaded when a device of that type is opened. ÂThis
>> > patch adds the alias.
>>
>> You really have users that are using a static /dev that need this kind
>> of fix? ÂI thought we were phasing out the char-major- aliases as they
>> don't make any sense anymore.
>>
> I don't think so.
>
> But since we had aliases to support users, I wasn't going to drop them
> without at least sending a patch upstream to see if they cared about
> such things.
>
> (and there are many modules which do have the char-major aliases, so at
> least someone is trying to put them in).
>
> As noted in the cover, feel free to drop these - I can use your reply
> when a user complains <g>

Yeah, we should put them into the module, where they belong, or just
remove them all. :) They surely do not belong into disconnected
userspace config files.

We are going to delete all kernel module configurations from the
userspace packages, and the only alternative for the kernel to provide
the autoload-by-open facility to users who like to use that, would be
that the kernel installs a modprobe config file which is maintained by
the kernel maintainers. Not sure if someone wants to do that instead.
:)

The new modprobe does not really care how many aliases we have, the
time to lookup the aliases depends mainly on the length of the alias
lookup string, not the number of strings to match against, so this
should all be fine.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/