From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Hinds Date: Thu, 11 Jan 2001 17:18:21 +0000 Subject: Re: hotplug TTD Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Jan 11, 2001 at 08:40:44AM -0800, David Brownell wrote: > > Though when I started to think about how to do that stuff robustly, I > began to wish a kernel "module" didn't stop being a visible component > when it gets statically linked. There's a rather arbitrary line between > static linking (build tools) and dynamic linking (modutils). Hotplugging > a device shouldn't need to care so much how the driver module is linked. Yes this is useful. For PCMCIA, I created /proc/bus/pccard/drivers to list what drivers are present, as static or modules. But a kernel wide solution would be better (even if it is /proc/bus/*/drivers). > David Hinds at one point spoke in favor of having more info passed > to the network hotplug events than just the interface name. That's > critical for statically configured hardware (servers); dynamically > configured ones (pure DHCP clients, say) should not care. Yes, I can tell you that if only the interface name is passed, it is going to frustrate some people who are used to having more information from PCMCIA. It isn't entirely bad... at least, you can get the interface's hardware address, and use that to choose configurations. But I find it quite useful to know that eth0 is "the 3C575 card in PCMCIA socket 1", or vice versa. -- Dave _______________________________________________ Linux-hotplug-devel mailing list Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel