Alan Stern replied:
>On Wed, 5 May 2004, Fulko Hew wrote:
>
>> Well your right. Both coldplug and hotplug does not get me to uhci_irq
(),
>> but then again neither does the unplug. ;-|
>> The unplug does get to core/usb.c:usb_disconnect()
>>
>> Whats the best way to figure out if interrupts are even enabled on the
>> device?
>
>If it works initially, before you unplug the device, then interrupts are
>enabled.
But...
I put in a printk() at the start of the interrupt handler: uhci_irq()
and it _never_ gets called!... ever!
But usb_disconnect() does.
How can you get to usb_disconnect without having gone through uhci_irq?
(wishing I had a print_stack_trace() function.)
For what its worth:
Looking at /proc/interrupts on 2.6.6 (transcribed and edited):
0: timer
1: i8042
2: cascade
8: rtc
9: acpi
10: uhci_hcd, [EMAIL PROTECTED]:1:0:0
11: uhci_hcd, uhci_hcd, eth0, yenta, Intel 82801DB-ICH4
12: i8042
14: ide0
15: ide1
Whereas on RH9 it says:
0: timer
1: keyboard
2: cascade
8: rtc
9: acpi
10: usb_uhci, [EMAIL PROTECTED]:1:0:0
11: ehci_hcd, usb_uhci, usb_uhci, ohci1394, eth0,
PCI device 1524:1410 (Ene Technology Inc)
12: PS/2 Mouse
14: ide0
15: ide1
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
