From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 16 Sep 2003 16:43:12 +0000 Subject: Re: [ANN] dummyphp 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, Sep 04, 2003 at 02:38:39PM +0200, Rolf Eike Beer wrote: > > If you are using kernel 2.[56] and drivers using the new driver model it's not > necessary to unload the driver of the card before, the kernel will tell the > driver that the adapter has been removed and the driver will release his > internal stuff. With kernel 2.4 it's not that easy, dummyphp will refuse to > deactivate an adapter with loaded driver. Why? Why can't it just disconnect the device like the other pci hotplug drivers do in 2.4? > It does the same as fakephp.c which is in 2.6 now, with 2 differences: > > -it does not remove the slot directory from sysfs on disable > -you can reenable slots > > Any feedback welcome. Greg, it would be nice if you push this to Marcelo and > Linus. I really don't like the way the slots are named here, that's why I made fakephp to only show the existing devices in the system. I'd really like a change to fakephp that just rescans the pci bus to see if any new devices have been added by the bios, to handle the "add a new device" issue. I'll go add a patch to the pci hotplug core to export the sysfs directory to make this easier to support. Oh, and this is probably the wrong mailing list for this, there is a pci hotplug linux mailing list that you might want to post this to (that's where the other pci hotplug driver authors are.) thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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