Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 May 1998 05:12:58 -0700
From:      David Greenman <dg@root.com>
To:        Stephen Roome <steve@visint.co.uk>
Cc:        Terry Lambert <tlambert@primenet.com>, freebsd-current@FreeBSD.ORG
Subject:   Re: Intel Etherexpress PRO/100+ PCI 
Message-ID:  <199805121212.FAA23850@implode.root.com>
In-Reply-To: Your message of "Tue, 12 May 1998 11:56:49 BST." <Pine.BSF.3.96.980512102848.18433C-100000@dylan.visint.co.uk> 

next in thread | previous in thread | raw e-mail | index | archive | help
>On Mon, 11 May 1998, Terry Lambert wrote:
>% I find it unlikely that they are both on INT a.  This may be a bug in
>% the probe routines, or in your motherboard BIOS.  It could also account
>% for the start IRQ (say one was on 'INT b', but it wasn't seen).
>
>I think this is possibly probe related, although I can't be sure, but I've
>just checked another six machines none of which use are probed as using
>anything but int A.

   Terry just doesn't understand how interrupts work on the PCI bus, despite
providing a nice picture. :-) All of the PCI cards with a single interrupt
will use INT A - that's just how it works and is the reason for the interrupts
being cascaded the way they are on the bus. INT A on one slot is not the same
interrupt on another.

>Which is really unlikely! Especially machines like this:
>
>chip1 <Intel 82371SB PCI-ISA bridge> rev 1 on pci0:7:0
>        I/O Recovery Timing: 8-bit 3 clocks, 16-bit 2 clocks
>        Extended BIOS: enabled
>        Lower BIOS: enabled
>        Coprocessor IRQ13: enabled
>        Mouse IRQ12: disabled
>        Interrupt Routing: A: disabled, B: IRQ11, C: IRQ10, D: IRQ9
>					^^^^^^^^^
>               MB0: IRQ15, MB1: 
>chip2 <Intel 82371SB IDE interface> rev 0 on pci0:7:1
>        mapreg[20] type=1 addr=0000f000 size=0010.
>        Primary IDE: enabled
>        Secondary IDE: enabled
>de0 <Digital 21140A Fast Ethernet> rev 32 int a irq 11 on pci0:10
>					  ^^^^^^^^^^^^
>That looks wrong to me, shouldn't that de0 be on int b ?
>(I've got more machines that tell me this as well.)

   No. INT A on one slot is another's INT B.

>I moved everything around as you suggest, but everything always comes up
>as int A in the card probe, if what you say is true then it looks like
>it's got to be the probe code, in more than one version.

   That's not your goal. You want them to each use a different _irq_ not
a different INT letter. ...but none of this matters because it's not what
is causing your problem. :-)

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805121212.FAA23850>