From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Wed, 03 Dec 2008 06:55:10 +0000 Subject: Re: usb coldplug problem Message-Id: <20081203065510.GF12378@kroah.com> List-Id: References: <403A9FAC.2010904@free.fr> In-Reply-To: <403A9FAC.2010904@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Dec 01, 2008 at 06:27:30PM +0000, Bernd Porr wrote: > Ok. I'll look into that. So, you mean that I create with the "request > firmware" a new udev event which then could also call "comedi_config"? No. After the firmware is loaded into the device properly, you will then call comedi_config from the driver itself to initialize everything. > The problem just now is that I don't get any udev events during > coldplug. Do you think this will also solve that issue? Yes it will as the startup scripts already know how to handle coldplug firmware events. > One practical thing: it's probably a good idea to work on the driver > version which goes into the kernel and not the one in the comedi CVS. Where > can I check out my module just now? Grab the linux-next tree, your driver and cleanups, are in there. thanks, greg k-h