From owner-freebsd-current Mon May 6 20:49:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA06491 for current-outgoing; Mon, 6 May 1996 20:49:08 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA06486 for ; Mon, 6 May 1996 20:49:07 -0700 (PDT) Received: from phantasma.bevc.blacksburg.va.us (phantasma.bevc.blacksburg.va.us [198.82.200.65]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id UAA23711 for ; Mon, 6 May 1996 20:49:05 -0700 (PDT) Received: (from kmitch@localhost) by phantasma.bevc.blacksburg.va.us (8.7.5/8.7.3) id XAA04462 for current@freebsd.org; Mon, 6 May 1996 23:05:37 -0400 (EDT) From: Keith Mitchell Message-Id: <199605070305.XAA04462@phantasma.bevc.blacksburg.va.us> Subject: aic7xxx.c (v1.65) and AHC_TAGENABLE To: current@freebsd.org Date: Mon, 6 May 1996 23:05:37 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL13 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just recompiled my kernel with -current from May 5, and discoverd that even though I had AHC_SCBPAGING_ENABLE in my kernel config, I wasn't getting TAG support. (no little message on boot anymore). After doing some investigation, it appears that the AHC_TAGENABLE option has snuck back in. Just thought I would bring it up in case it wasn't supposed to "sneak" back in.