Next-in-Thread Next Message

None Strange IRQ info on NT

Re: None Need to determine the PCI interrupt (David Hinds)
Date: 2000, Aug 03
From: Sami Pitko spitko

NT Diagnostic gives following information:

IRQ Device Bus Type
...
06 Floppy 0 Isa
10 WVLAN41 0 Internal
11 E100B 0 Pci
...

What surprises me is that WaveLAN interrupt is of type Internal (whatever it means?). Maybe there is some kind of driver to produce/process those interrupts in NT.

Is there a way to find the interrupt which TI-1221 is using on NT? At least "Administrative Tools/Windows NT Diagnostics" only gives IRQ for WaveLAN adapter and on the "Control Panel/PCMCIA" there is only memory area as a resource for PCMCIA Controller.

On the linux side:

If I set the WaveLAN to use IRQ 10, it doesn't work. All PCI interrupts are giving "PCI irq N test failed", unless I set do_scan=0.

I was able to get some pings through when I set it to use the same interrupt as eepro100 is using (IRQ 11), but the ping packets only went through when there were network traffic going on (== interrupts generated by) the eepro100...

Messages Inline: 0 1

None I think you are out of luck

Re: None Strange IRQ info on NT (Sami Pitko)
Date: 2000, Aug 05
From: David Hinds <dhinds@pcmcia.sourceforge.org>

Hmmm.  I was actually surprised that this worked at all under NT.  Now
I think I understand.

I bet that NT has not figured out the interrupt routing either.  And
when it says "Internal", it means that it is faking the interrupt in
software.

Without a datasheet for your PCI bridge chipset (the VLSI one), I
don't think there is anything I can do to help you.

Your best bet would probably be to use an ISA-to-PCMCIA adapter card
instead of this PCI adapter.

-- Dave
Strange IRQ info on NT


Add Message to: "Strange IRQ info on NT"

Members Subscribe Admin Mode No Frames New Base Frame Help for HyperNews at pcmcia-cs.sourceforge.net 1.10