|
OK, here is the info that I used to (in my mind) eliminate the possibility of an IO overlap, other than bugging the HW manufacturer. I may have missed something, so here it is:
swlr# cat interrupts ioports
CPU0
0: 25356934 XT-PIC timer
1: 0 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 2107 XT-PIC serial
8: 2 XT-PIC rtc
11: 30250 XT-PIC SMC9194
13: 0 XT-PIC fpu
NMI: 0
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(auto)
0300-030f : SMC9194
03d4-03d5 : cga
03f8-03ff : serial(auto)
swlr# insmod /lib/modules/pcmcia_core.o;insmod /lib/modules/i82365.o ignore=1
swlr# insmod /lib/modules/ds.o
swlr# cat interrupts ioports
CPU0
0: 25364560 XT-PIC timer
1: 0 XT-PIC keyboard
2: 0 XT-PIC cascade
4: 2107 XT-PIC serial
8: 2 XT-PIC rtc
11: 30697 XT-PIC SMC9194
13: 0 XT-PIC fpu
NMI: 0
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(auto)
0300-030f : SMC9194
03d4-03d5 : cga
03e0-03e1 : i82365
03f8-03ff : serial(auto)
swlr# # Inserting Aironet modules. You can find them in the 2.3.newest kernel, I'm using the 2.2.13 version.
swlr# cat interrupts
CPU0
0: 25374716 XT-PIC timer
1: 0 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 0 XT-PIC aironet4500_cs
4: 2107 XT-PIC serial
8: 2 XT-PIC rtc
11: 31301 XT-PIC SMC9194
13: 0 XT-PIC fpu
NMI: 0
swlr# cat ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0100-013f : aironet4500_cs
02f8-02ff : serial(auto)
0300-030f : SMC9194
03d4-03d5 : cga
03e0-03e1 : i82365
03f8-03ff : serial(auto)
As you can see, I'm running at IRQ 3, IO 0x100. This is on my 'special' hardware. Now, the stats from a different HW platform running 2.0.37, and a slightly older pcmcia-cs:
dts-dtn-rtr# cat interrupts ioports 0: 1026540671 timer 1: 8 keyboard 2: 0 cascade 3: 2552978658 aironet4500_cs 4: 10 + serial 8: 0 + rtc 11: 2409110548 eth0 13: 0 math error 15: 2 i82365 0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-009f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : npu 0100-013f : aironet4500_cs 03b0-03bb : mda 03bf-03bf : mda 03e0-03e1 : i82365 03f8-03ff : serial(set) ff80-ff9f : eth0 As you can see CS assigns the HW the same IO/IRQ for both platforms. Both platforms have been verified by the HW manufacturer to have no IO conflicts at these addresses. I'll let you guys puzzle over that. In the meantime, I'm going to upgrade to kernel 2.3.latest and see what happens re: these cards.
|
Not a kernel issue; maybe timing?
| |
|
Clarification
| |
|