From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 16:08:19 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F38D916A403 for ; Sat, 28 Oct 2006 16:08:18 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E4143D6D for ; Sat, 28 Oct 2006 16:08:18 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9SG8IIY069039 for ; Sat, 28 Oct 2006 09:08:18 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9SG8IAp069036 for ; Sat, 28 Oct 2006 09:08:18 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Sat, 28 Oct 2006 09:08:17 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-scsi@freebsd.org In-Reply-To: <20061027184143.GA70768@nargothrond.kdm.org> Message-ID: <20061028090155.R69020@ns1.feral.com> References: <20061027090957.V60559@ns1.feral.com> <20061027183235.GA70290@nargothrond.kdm.org> <20061027113922.M61368@ns1.feral.com> <20061027184143.GA70768@nargothrond.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 16:08:19 -0000 There a number of SIMs that need changes for the CAM_NEW_TRAN code- I can't test them all, but it's a pretty straightforward exercise to do this. My plan is to add all of the changes so that LINT+CAM_NEW_TRAN_CODE compiles and otherwise test what I have h/w for and check that in. Once that's done, I'll send an announcement out about a cutover date in -current to the CAM_NEW_TRAN_CODE which is going to be the only way to actually get this in place and actually tested, and either remove the non-CAM_NEW_TRAN_CODE or change the definition so we have CAM_OLD_TRAN_CODE. Questions: a) If anyone wants reviews of the changes, please say so now. I'll try and send diffs to all and sundry as I go along, but I may forget. Again, the changes are expected relatively small b) Should I retain the old code? I would think not. I mean, this stuff has been around for years and it just clutters up the screen for the old stuff. -matt