From owner-freebsd-arch Tue Jun 13 11:14:13 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 AF39937BFA5; Tue, 13 Jun 2000 11:14:02 -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 UAA11882; Tue, 13 Jun 2000 20:13:58 +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:57:10 PDT." <200006131757.KAA22609@mass.cdrom.com> Date: Tue, 13 Jun 2000 20:13:58 +0200 Message-ID: <11880.960920038@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006131757.KAA22609@mass.cdrom.com>, Mike Smith writes: >> The AMCC "PCI Matchmaker" is a very good example. >> >> (If you know what this chip is, search ebay for "pci matchmaker" :-) > >I've designed hardware using this device (and similar from PLX). > >In each case, you stuff your new PCI IDs into the EEPROM. > >More importantly, to comply with PCI 2.1, which is required for the >Windows Logo Program, you *have* to have a unique ID. Right, but so far the batting average I've seen is that 1 in 3 uses of the matchmaker doesn't do that. -- 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