From owner-freebsd-current Tue May 12 11:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23877 for freebsd-current-outgoing; Tue, 12 May 1998 11:21:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23863 for ; Tue, 12 May 1998 11:21:30 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id LAA27640; Tue, 12 May 1998 11:21:27 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd027566; Tue May 12 11:21:19 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA23722; Tue, 12 May 1998 11:21:13 -0700 (MST) From: Terry Lambert Message-Id: <199805121821.LAA23722@usr04.primenet.com> Subject: Re: Intel Etherexpress PRO/100+ PCI To: dg@root.com Date: Tue, 12 May 1998 18:21:13 +0000 (GMT) Cc: steve@visint.co.uk, tlambert@primenet.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199805121212.FAA23850@implode.root.com> from "David Greenman" at May 12, 98 05:12:58 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >% 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. ??? Uh, that's what I said. I think it's unlikely that cards in two different slots will have INT a assigned to them, unless the bus lines are *not* cascaded, which I also think is unlikely on a modern motherboard. Why are both cards reported on INT a? > 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. :-) Well, you want them to use a different PCI input line, of which there are four on most chipsets not manufactured by DEC or Apple, and which are lettered a through d. Are we asking the card where it thinks it is? If so, how are we getting the INT b's from slot 2 to the interrupt handler? I think it's more useful to report the ID seen by the handler than the ID seen by the card, especially for something like a dual channel Adaptec controller leaching two interrupts (INT a from it's slot, and INT b from the adjacent slot -- wrapping around at the end of the bus). Am I just not understanding that what's being reported isn't what's being set up in the IRQ handler list? If so, this seems wrong... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message