From owner-freebsd-current Fri Jan 26 14:54:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA04163 for current-outgoing; Fri, 26 Jan 1996 14:54:08 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA04144 for ; Fri, 26 Jan 1996 14:53:49 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA29598; Fri, 26 Jan 1996 23:52:01 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA20026; Fri, 26 Jan 1996 23:52:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id XAA20785; Fri, 26 Jan 1996 23:24:02 +0100 (MET) From: J Wunsch Message-Id: <199601262224.XAA20785@uriah.heep.sax.de> Subject: Re: More on NEC diffs in scsiconf.c To: freebsd@hopf.math.purdue.edu (Clarence Wilkerson) Date: Fri, 26 Jan 1996 23:24:02 +0100 (MET) Cc: current@freebsd.org, wilker@hopf.math.purdue.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601261905.OAA07332@hopf.math.purdue.edu> from "Clarence Wilkerson" at Jan 26, 96 02:05:02 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org Precedence: bulk As Clarence Wilkerson wrote: > Thanks for the suggested diffs. As given, there is a complaint > in the compile for -current. It appears that the data structures > have included another field since the diffs suggested were test. > The compile complaint and comparison to other entries suggest that > this should be > {T_READONLY, T_READONLY, T_REMOV, "NCR", "MBR-7" .........}. > for -current . Yup. In order to provide support for weird devices that claim to be something else than they actually are (magneto-optical drives that claim to be T_DIRECT, CD recorders that pretend T_READONLY (CD-ROM)), i've included an additional field there in -current. The first one is used to match the device (together with the vendor and model strings), while the second one assigns it to a particular driver. -- 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. ;-)