Re: alpha can't map interrupt

2002-06-07 Thread Dag-Erling Smorgrav
M. Warner Losh [EMAIL PROTECTED] writes: 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? I can easily test it, fire away. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: alpha can't map interrupt

2002-06-07 Thread Dag-Erling Smorgrav
M. Warner Losh [EMAIL PROTECTED] writes: Does this fix things for you? Yep, thanks! DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: alpha can't map interrupt

2002-06-07 Thread Bernd Walter
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

Re: alpha can't map interrupt

2002-06-07 Thread Andrew Gallatin
Bernd Walter writes: 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? Nothing is wrong with it unless you're on an x86, where I assume some (broken) BIOSes assign unrouted interrupts to zero rather than 255.

Re: alpha can't map interrupt

2002-06-07 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Bernd Walter [EMAIL PROTECTED] writes: : 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. 0 is invalid on i386. Somehow I thought drew was

Re: alpha can't map interrupt

2002-06-07 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Andrew Gallatin [EMAIL PROTECTED] writes: : Nothing is wrong with it unless you're on an x86, where I assume some : (broken) BIOSes assign unrouted interrupts to zero rather than 255. That's right. There's supposedly also some hardware that incorrectly

Re: alpha can't map interrupt

2002-06-06 Thread Andrew Gallatin
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. Thanks, Drew Dag-Erling Smorgrav writes: A kernel built from last night's sources fails to allocate an interrupt to the NIC in my Miata:

Re: alpha can't map interrupt

2002-06-06 Thread M. Warner Losh
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,

Re: alpha can't map interrupt

2002-06-06 Thread M. Warner Losh
Please accept my appologies for this, it does look like I messed up the MI code. The following change may mess up the pcib code a little, but I think that the MD code now does the right thing. Does this fix things for you? Warner Index: pcivar.h