Re: [linux-usb-devel] driver module loading

2002-02-06 Thread Greg KH
On Wed, Feb 06, 2002 at 03:01:25PM +0530, Ravi Kumar B S wrote: > hi i found why the driver is not listed as being used. when i connect > the device. the probe function is getting called. in that first it makes > check on the device class signature. there it is immediately returning > as i am g

Re: [linux-usb-devel] driver module loading

2002-02-06 Thread Ravi Kumar B S
Dmitri wrote: >Quoting Ravi Kumar B S <[EMAIL PROTECTED]>: > >>Dmitri wrote: >> > >>>In worst case, presence of printk's moves the memory around, and you have >>>a stray pointer somewhere that reads or writes past the allocated >>>memory. With printks in place, this pointer happens to point to a

Re: [linux-usb-devel] driver module loading

2002-02-06 Thread Dmitri
Quoting Ravi Kumar B S <[EMAIL PROTECTED]>: > Dmitri wrote: > >In worst case, presence of printk's moves the memory around, and you have > >a stray pointer somewhere that reads or writes past the allocated > >memory. With printks in place, this pointer happens to point to a safe > >place; withou

Re: [linux-usb-devel] driver module loading

2002-02-06 Thread Ravi Kumar B S
Dmitri wrote: >Quoting Ravi Kumar B S <[EMAIL PROTECTED]>: > >>i am using the usb bluetooth driver. i have configured the usb bluetooth >>driver as a module. i have two versions of the driver. one with the >>comments, extensive debug statements(printks) etc. the other one is the >>one which is

Re: [linux-usb-devel] driver module loading

2002-02-05 Thread Dmitri
Quoting Ravi Kumar B S <[EMAIL PROTECTED]>: > i am using the usb bluetooth driver. i have configured the usb bluetooth > driver as a module. i have two versions of the driver. one with the > comments, extensive debug statements(printks) etc. the other one is the > one which is cleaned does not

[linux-usb-devel] driver module loading

2002-02-05 Thread Ravi Kumar B S
hi, i am using the usb bluetooth driver. i have configured the usb bluetooth driver as a module. i have two versions of the driver. one with the comments, extensive debug statements(printks) etc. the other one is the one which is cleaned does not have that many debug statements. now the proble