hi greg, nope! i had'nt gone thru. the Documentation/pci.txt file, but i guess my driver follows almost all the things mentioned in it (it's a really good doc. quite thorough!). One thing i think i did'nt do is that i'm not exporting the device ID table using the macro as u mentioned. one last thing, do i have to "modify" any of the hotplug scripts in order to support hotplugability for my driver?? thanks for ur time, - /dev/mandeep -----Original Message----- From: Greg KH [mailto:greg@kroah.com] Sent: Wednesday, May 05, 2004 9:19 PM To: Mandeep Singh Sandhu Cc: kernelnewbies@nl.linux.org Subject: Re: how to test hotplugability for pci driver? On Wed, May 05, 2004 at 09:44:59AM +0530, Mandeep Singh Sandhu wrote: > hi list, > > i've written a PCI driver for a 2.4.18 kernel. Why such an old kernel? That one is _years_ old, and has numerous security holes in it. > I want to > test hotplugability of my driver, how do i go about it??? Does your driver follow the rules layed out in Documentation/pci.txt? If so (it has a probe and disconnect function) then you are fine. You also need to have a MODULE_DEVICE_TABLE() defined so that the hotplug scripts know how to pick up your module and load it properly if the hardware is seen (and will cause your driver to be added to the modules.pcimap file automagically.) To test if you can remove your driver properly, in a hotplug situation, use the fakephp driver in the 2.6 kernel. Good luck, greg k-h -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
