From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linas Vepstas Date: Tue, 22 Mar 2005 18:09:05 +0000 Subject: Re: Rework of request firmware Message-Id: <20050322180905.GB498@austin.ibm.com> List-Id: References: <9e473391050319200625032789@mail.gmail.com> In-Reply-To: <9e473391050319200625032789@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Mar 22, 2005 at 11:27:33AM +0300, Roman Kagan was heard to remark: > Unloading the driver has undesired side effects, like unbinding other > devices handled by the same driver, and takeover of the device by > another matching driver. Heh. Unhappiness ensues if the device is e.g. a disk controller, and there is a mounted file system on top of it. Current unix semantics don't allow a post-facto unmount if the block device under it disappears. This is a bit off-topic, but we are having a discussion on the PCI mailing list about how to auto-recover from PCI bus errors. Currently, (and this is very arch & driver specific) drivers do things like post/bist and probe again to recover, and get back to a reasonable working state (without unbinding the driver). Any interest in disucussing this from a generic bus viewpoint? Or would this be a distraction at this point? --linas ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_idh82&alloc_id148&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