>> As I know, function probe (struct >>usb_driver contains pointer
>> to it) is called, when new device is >>atached to the bus.
>
>> But it's don't calls, when I attach device.
>> May be it needs something more - I don't >>know.
>What USB modules do you have loaded when you >attach the device?
>Enable all kernel logging (Alt-SysRq-9 with >Magic Sys Request
>keys enabled) or boot with "linux debug".
>> usb_register returns OK. That's mean, that >>my driver's callback
>> functions like probe registered >>successfully.
>>
>> I don't understand this mechanism. What's >>happening when device attach
>> to the bus?
>>
>> Is probe calls for each USB driver?
>> If not - than how system know wich probe >>calls?
>Yes, when a new device is attached, >driver_probe() is called
>for each registered driver for each interface >of the new device,
>as long as the interface hasn't been claimed >by another USB
>driver. Could another loaded driver have >already claimed
>your device's interface(s)?
I compile kernel with USB support. It's need uchi and hub drivers. It
built in kernel.
No more USB drivers (modules) loaded.
>> May be I don't use need options in >>compiler/linker? But
>> insmod mymodule works.
>>
>> Please, replay answer to [EMAIL PROTECTED]
>>
>> P.S.: It's my first linux driver.
>~Randy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
