From owner-freebsd-arch Tue Jun 13 10:37:12 2000 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 484CB37B72A; Tue, 13 Jun 2000 10:37:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA11714; Tue, 13 Jun 2000 19:37:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Terry Lambert , arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h In-reply-to: Your message of "Tue, 13 Jun 2000 10:34:28 PDT." <200006131734.KAA22492@mass.cdrom.com> Date: Tue, 13 Jun 2000 19:37:01 +0200 Message-ID: <11712.960917821@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006131734.KAA22492@mass.cdrom.com>, Mike Smith writes: >> The PCI issue is unique, in that PCI devices can be identified by >> a generic routine. And case in point: Just because you have identified a PCI chip doesn't mean that you know what's next to it on the board. The AMCC "PCI Matchmaker" is a very good example. (If you know what this chip is, search ebay for "pci matchmaker" :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message