From owner-freebsd-scsi Sun Dec 3 16:44:52 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA09748 for freebsd-scsi-outgoing; Sun, 3 Dec 1995 16:44:52 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA09741 for ; Sun, 3 Dec 1995 16:44:38 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id QAA02303; Sun, 3 Dec 1995 16:35:12 -0800 From: Julian Elischer Message-Id: <199512040035.QAA02303@ref.tfs.com> Subject: Re: /sys/scsi/st.c and NEW_SCSICONF? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 3 Dec 1995 16:35:12 -0800 (PST) Cc: jkh@time.cdrom.com, freebsd-scsi@freebsd.org In-Reply-To: <199512031609.RAA02736@uriah.heep.sax.de> from "J Wunsch" at Dec 3, 95 05:09:40 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 814 Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > As Jordan K. Hubbard wrote: > > > > If you have NEW_SCSICONF defined in -current, it disables a block of > > defines in /sys/scsi/scsi_tape.h. All well and good, but one of those > > defines is "QIC_3080" which gets referenced in st.c regardless. > > > > I've conditionalized the QIC_3080 references in st.c on !NEW_SCSICONF > > as well and gotten past the problem for now, but I'm not sure if > > that's what the author(s) intended. > > NEW_SCSICONF should die (one way or the other), but apparently > everybody is too busy to kill it... I've scheduled some of my time in the upcoming holiday to cleaning up the SCSI code.. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) >