From owner-freebsd-current Thu May 14 03:22:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26613 for freebsd-current-outgoing; Thu, 14 May 1998 03:22:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26602; Thu, 14 May 1998 03:22:36 -0700 (PDT) (envelope-from steve@visint.co.uk) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id LAA16444; Thu, 14 May 1998 11:22:43 +0100 (BST) Date: Thu, 14 May 1998 11:22:02 +0100 (BST) From: Stephen Roome To: Stefan Esser cc: Terry Lambert , David Greenman , freebsd-current@FreeBSD.ORG Subject: Re: Intel Etherexpress PRO/100+ PCI In-Reply-To: <19980513232233.49213@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 13 May 1998, Stefan Esser wrote: > > Mouse IRQ12: disabled > > Interrupt Routing: A: disabled, B: IRQ11, C: IRQ10, D: IRQ9 > > ^^^^^^^^^ > > Those A, B, C, D are chip-set pins, which are not directly > related to PCI interrupt names! I've got this straight in my head now, it's an unfortunate naming system and it's really unhelpful for newbies. (I know that's not a FreeBSD problem!) > > de0 rev 32 int a irq 11 on pci0:10 > > ^^^^^^^^^^^^ > > That looks wrong to me, shouldn't that de0 be on int b ? > > No. It just tells you, that chip-set pin B is wired to the PCI > interrupt trace which is connected to PCI IntA on the connector > that got a slot ID of 10 in config space. I follow this now, or at least I think so.. Will the first interrupt assigned to a PCI device always be int a (according to the card) and the second int b. If so then it's not really very helpful, in fact it's just confusing, to display it in the probe (did someone else mention this already, I'm probably running a bit behind on brainpower!?) > A single function device (e.g. the DEC Ethernet chip) is not > allowed to use any interrupt other than "a". I don't fully understand the distinction of "single function device", does a midi/FM sound card count as multi-function ? How about Anyway, I've changed my pciconf so it gives me verbose listing and tells me whats going on without me having to refer/remember sys/pcireg.h. I might try and obtain the PCI specs, as it's looking worth reading. Many thanks to you and all others who've helped explain all this. Steve Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message