From owner-freebsd-current Tue May 12 22:55:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17742 for freebsd-current-outgoing; Tue, 12 May 1998 22:55:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17724 for ; Tue, 12 May 1998 22:55:03 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA04275; Tue, 12 May 1998 22:52:49 -0700 (PDT) Message-Id: <199805130552.WAA04275@implode.root.com> To: Terry Lambert cc: steve@visint.co.uk, freebsd-current@FreeBSD.ORG Subject: Re: Intel Etherexpress PRO/100+ PCI In-reply-to: Your message of "Wed, 13 May 1998 01:51:29 -0000." <199805130151.SAA26286@usr09.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 12 May 1998 22:52:49 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The int that is reported by FreeBSD should match the PCI mapping. > >For example: > > ... int a irq 10 ... > ... int a irq 11 ... > ... int a irq 12 ... > ... int a irq 13 ... > >Should be reported based on the PCI mapping of PCI bridge pins to >irq's. > >That is, reporting "int a" is incorrect, since "a" is not the PCI >bridge pin, it's the slot pin. Perhaps that should be reported when probing the bridge chip, and I have no problem with that, but the information that comes out for the PCI card is correct in that it is reporting info about the card and not about the bridge mapping. I'm not arguing against what you are saying, just pointing out the way it works, which is different than they way you thought it worked. -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