From owner-freebsd-hackers Mon Dec 9 13:30:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA01812 for hackers-outgoing; Mon, 9 Dec 1996 13:30:41 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA01802 for ; Mon, 9 Dec 1996 13:30:29 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-10.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA09378 (5.67b/IDA-1.5 for ); Mon, 9 Dec 1996 22:29:44 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id QAA17337; Mon, 9 Dec 1996 16:02:15 +0100 (CET) Message-Id: Date: Mon, 9 Dec 1996 16:00:54 +0100 From: se@FreeBSD.org (Stefan Esser) To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: hackers@FreeBSD.org Subject: Re: VX-aware PCI probe References: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au>; from Michael Smith on Dec 9, 1996 14:50:14 +1030 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Dec 9, msmith@atrad.adelaide.edu.au (Michael Smith) wrote: > > Can someone with a VX-chipset motherboard confirm that this patch correctly > identifies their chipset before I commit it? (beware snarf-n-barf damage). Can't check that, but it doesn't look completely wrong :) > What was the consensus on codenames? I notice that the old "Triton" > comments have gone, but some of the others are still there. There is a problem with using "Triton" in Germany, since some French company got "Tricon" as a registered trademark, and some lawyer is suing anybody violating that trademark ... (That lawyer made a special agreement with Microsoft, BTW, which allows them to identify the Triton chip-set under Win/95. But a lot of motherboards used to print Triton in the boot message, and the dealers had to stop selling them, and to pay $1000 to $7000i ...) > Any interest in a general PCI device ID/name mapping registry? I'd be > happy to collect all the intelligence scattered among the files in > sys/pci and write a small lookup function to return it appropriately. I'm planning to remove most of the verbose PCI probe messages, and have a (easily configurable) user-land program know much more about the different PCI chips, than you'd ever want to put into the kernel. Only information that might be useful for debugging in case of a boot failure should be printed by the probe/attach code, IMHO. This will remove some 7KB from the kernel binary, and will add a few tens of KB to the disk space requirements, if in fact lots more vendors and devices will be known to that code ... > + case 0x70308086: > + return ("Intel 82437VX PCI cache memory controller"); Regards, STefan