From owner-freebsd-hackers Sun Dec 8 20:56:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA27695 for hackers-outgoing; Sun, 8 Dec 1996 20:56:03 -0800 (PST) Received: from netrover.com (ottawa24.netrover.com [205.209.19.33]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA27682 for ; Sun, 8 Dec 1996 20:56:00 -0800 (PST) Received: (from brianc@localhost) by netrover.com (8.8.2/8.8.2) id XAA02109; Sun, 8 Dec 1996 23:55:24 -0500 (EST) Message-ID: Date: Sun, 8 Dec 1996 23:55:23 -0500 From: brianc@netrover.com (Brian Campbell) To: hackers@FreeBSD.org Subject: Re: VX-aware PCI probe References: <199612090420.OAA06973@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.51 Mime-Version: 1.0 Reply-to: brianc@pobox.com 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 Michael Smith writes: > Can someone with a VX-chipset motherboard confirm that this patch correctly > identifies their chipset before I commit it? (beware snarf-n-barf damage). That's exactly the code I've been using for the last several revisions. It detects my VX reliably. Is there a similar "patch" in chipset_attach? How about the same two patches for the 82371FB IDE interface on the Triton IIs?