On Wed, Jun 12, 2002 at 11:05:00AM -0700, Greg KH wrote: > On Wed, Jun 12, 2002 at 11:04:04AM -0700, Tom Rini wrote: > > On Wed, Jun 12, 2002 at 10:29:42AM -0700, Greg KH wrote: > > > On Wed, Jun 12, 2002 at 09:36:42AM -0700, Tom Rini wrote: > > > > On Wed, Jun 12, 2002 at 09:29:47AM -0700, Tom Rini wrote: > > > > > On Wed, Jun 12, 2002 at 12:02:52AM +0200, Jeroen Vreeken wrote: > > > > > > Is it possible to add some printk() calls in the probe function to > > > > > > determine where it goes wrong? > > > > [snip] > > > > > And the prink I inserted at the top of the function never gets called. > > > > > > > > ... which is because se401_probe is __devinit (which turns into __init, > > > > since CONFIG_HOTPLUG=n, and __init turns into '' when in a module). > > > > Here's the lightly tested patch (for 2.4 and 2.5). > > > > > > And here's one that should get all of the __devinit issues for > > > 2.4.19-pre10. I'll go make up a 2.5.21 version of this too. > > > > Oddly enough I couldn't sync my visor (compiled in, CONFIG_HOTPLUG=n) > > unless I changed the id_table_combined in drivers/usb/serial/visor.c to > > not be __devinitdata. I'm not quite sure why, but although dmesg > > printed out all the ususal information about it, pilot-xfer just sat > > around. > > Odd, after the device is bound, the device list is not needed, so this > must be something else.
Well, odder still. I swear I had this repeatidly not working right, but now it's fine. I guess this goes under user-error somewhere. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ _______________________________________________________________ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
