On Thu, Jun 06, 2002 at 08:31:33PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Andrew Gallatin <[EMAIL PROTECTED]> writes:
> :
> :
> : Warner -- a pci interupt line of 0 is valid. Please back out your
> : "PCI_INTERRUPT_VALID" changes in pci.c, or change that macro
> : to allow a value of 0.
>
> An interrupt line of 0 is *NOT* valid. However, the check for zero
OK - it's fixed for now, but what is wrong with zero?
Many alphas differentiate between ISA and PCI intlines.
PCI intlines are startet counting with 0.
[52]cicely9> devinfo -r
cia0
pcib0
pci0
sym0
PCI Mapped Interrupts:
0x2
I/O memory:
0x82030000-0x82030fff
0x82031200-0x820312ff
sym1
PCI Mapped Interrupts:
0x0
I/O memory:
0x82031100-0x820311ff
sym2
PCI Mapped Interrupts:
0x1
I/O memory:
0x82031000-0x820310ff
isab0
isa0
atkbdc0
fdc0
ISA Interrupt request lines:
6
ISA DMA request lines:
2
I/O ports:
0x3f0-0x3f5
0x3f7
fd0
mcclock0
I/O ports:
0x70-0x71
ppc0
sc0
sio0
ISA Interrupt request lines:
4
I/O ports:
0x3f8-0x3ff
sio1
vga0
xl0
PCI Mapped Interrupts:
0x3
I/O ports:
0x10300-0x1037f
miibus0
xlphy0
atapci0
ata0
I/O ports:
0x1f0-0x1f7
0x3f6
0x10380-0x10387
ata1
I/O ports:
0x170-0x177
0x376
0x10388-0x1038f
> should only be on the i386 port. Where did I have it? Oh, I see now.
> I didn't change the PCI_INTERRUPT_VALID to include zero, I just
> changed some code to use it. It was used in pcib.
>
> But I'll make sure that it works on alpha. Is that something that you
> can test for me if I come up with a fix for?
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
