From: Oliver Neukum <firstname.lastname@example.org> To: Alan Stern <email@example.com>, Greg KH <firstname.lastname@example.org> Cc: David Brownell <email@example.com>, <firstname.lastname@example.org>, <email@example.com> Subject: Re: [linux-usb-devel] [RFC] consolidate /sbin/hotplug call for pciand usb Date: Fri, 27 Sep 2002 01:35:17 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <Pine.LNX.4.33L2.email@example.com> > This raises a generally interesting question: When should a driver > module be loaded? It is an interesting question, but it is not a kernel problem :-) [..] > I think it's clear that the answer must depend on the particular driver, > and that no single scheme involving usage counts (or the equivalent) can > suffice for every situation. > > Is there a way to let the kernel provide a variety of mechanisms and let > the device driver (or even the user) select which one gets used? That is more or less what is in place. There's a kernel aspect to the problem, because the kernel needs to implement an unload if nothing is bound to method, as user space cannot do that without a race. Regards Oliver
next prev parent reply other threads:[~2002-09-26 23:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-25 21:29 [RFC] consolidate /sbin/hotplug call for pci and usb Greg KH 2002-09-25 22:04 ` Kai Germaschewski 2002-09-25 22:48 ` Greg KH 2002-09-26 0:11 ` [linux-usb-devel] " David Brownell 2002-09-26 0:25 ` Greg KH 2002-09-26 2:44 ` David Brownell 2002-09-26 4:27 ` Greg KH 2002-09-26 16:14 ` David Brownell 2002-09-26 18:43 ` Greg KH 2002-09-26 19:32 ` David Brownell 2002-09-26 19:34 ` Alan Stern 2002-09-26 23:35 ` Oliver Neukum [this message] 2002-09-26 17:48 ` [RFC] consolidate /sbin/hotplug call for pci and usb - take 2 Greg KH
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [linux-usb-devel] [RFC] consolidate /sbin/hotplug call for pciand usb' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).