From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
Matthias Andree <matthias.andree@gmx.de>,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Fw: 2.6.0-test11 BK: sg and scanner modules not auto-loaded?
Date: Sat, 20 Dec 2003 14:04:59 +1100 [thread overview]
Message-ID: <20031221003020.63E6A2C0B8@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 19 Dec 2003 10:10:39 -0800." <20031219181039.GI3017@kroah.com>
In message <20031219181039.GI3017@kroah.com> you write:
> Please just leave it up to the hotplug code to load such drivers as
> these. Also watch out, if you enable CONFIG_USB_DYNAMIC_MINORS then the
> usb scanner driver will NOT start at minor number 48, but will be
> dynamically created.
Thanks Greg, that's what I figured. Although the hotplug subsystem
could create the device nodes and then have kmod load the actual
drivers on open, I'm not convinced it's worth it for dynamic devices.
It's been argued that kmod should place a request with the hotplug
subsystem, rather than call modprobe, but that's a little too radical
for me just yet.
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-12-21 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031218091404.4b2f743b.akpm@osdl.org>
2003-12-19 0:03 ` Fw: 2.6.0-test11 BK: sg and scanner modules not auto-loaded? Rusty Russell
2003-12-19 18:10 ` Greg KH
2003-12-20 3:04 ` Rusty Russell [this message]
2003-12-21 0:49 ` Greg KH
2003-12-21 1:25 ` Matthias Andree
2003-12-21 12:37 ` Duncan Sands
2003-12-21 12:44 ` Matthias Andree
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=20031221003020.63E6A2C0B8@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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