From owner-freebsd-hackers Fri Aug 23 18:38:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA20390 for hackers-outgoing; Fri, 23 Aug 1996 18:38:15 -0700 (PDT) Received: from ottawa.net (ppp-67.ottawa.net [205.211.4.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA20359 for ; Fri, 23 Aug 1996 18:38:09 -0700 (PDT) Received: (from brianc@localhost) by ottawa.net (8.7.5/8.7.3) id VAA00256 for freebsd-hackers@FreeBSD.org; Fri, 23 Aug 1996 21:38:01 -0400 (EDT) From: Brian Campbell Message-Id: <199608240138.VAA00256@ottawa.net> Subject: Triton II chipsets To: freebsd-hackers@FreeBSD.org (FreeBSD Hackers) Date: Fri, 23 Aug 1996 21:38:01 -0400 (EDT) Reply-to: brianc@pobox.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm running on a Triton II VX chipset and wanted the chipset probe to recognize and display my chipset. So, in chipset_probe() I added: case 0x70308086: return ("Intel 82437 PCI cache memory controller"); I also copied the conf82437fx[] block into a conf82437vx[] block. It's identical to the former except that it doesn't include the block for register offset 0x50. Also, the PIIX3 on the Triton II chipset supports the same registers displayed for the PIIX. So, in chipset_attach() I added: case 0x70308086: writeconfig (config_id, conf82437vx); break; case 0x70108086: case 0x122e8086: where the second last case falls into the (already present) last case label for the PIIX. I suspect the HX chipset will support the same configuration registers as the VX, and FX, but I haven't got one to try it with. [I can generate a patch if necessary]