From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Nottingham Date: Thu, 04 Mar 2004 03:58:56 +0000 Subject: Re: [ANNOUNCE] udev 021 release Message-Id: <20040304035856.GA31986@devserv.devel.redhat.com> List-Id: References: <20040303225305.GB30608@weiser.dinsnail.net> <20040304012531.GC2207@kroah.com> In-Reply-To: <20040304012531.GC2207@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: Michael Weiser , Ed Tomlinson , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Greg KH (greg@kroah.com) said: > Sorry, but you're a bit late. We've been moving this way since before > 2.4.0. > > The fact that module unload even works today is a blessing due to all of > the well-documented issues involved. I doubt any distro will enable > module unloading because of it. So, then, answer this question. In previous kernels, 2.4 and otherwise, a driver or piece of hardware may get into a 'confused' state. You unload the driver, reload it, it resets, everything is peachy. How do I reinitialize a driver or hardware in your 'no-unload' scenario? Bill ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel