From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 2 21:51:50 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 C327316A423; Thu, 2 Feb 2006 21:51:50 +0000 (GMT) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1C1543D49; Thu, 2 Feb 2006 21:51:49 +0000 (GMT) (envelope-from mj@feral.com) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.4/8.13.4) with ESMTP id k12LpnE5099427; Thu, 2 Feb 2006 13:51:49 -0800 (PST) (envelope-from mj@feral.com) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.4/8.13.4/Submit) with ESMTP id k12LpnEC099424; Thu, 2 Feb 2006 13:51:49 -0800 (PST) (envelope-from mj@feral.com) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Thu, 2 Feb 2006 13:51:49 -0800 (PST) From: Matthew Jacob X-X-Sender: mjacob@ns1.feral.com To: Scott Long In-Reply-To: <43E27E58.4020606@samsco.org> Message-ID: <20060202135123.K99168@ns1.feral.com> References: <20060130202806.DCC7916A4CA@hub.freebsd.org> <43DEF43A.6090804@root.org> <20060130213338.H79194@ns1.feral.com> <200601311239.10248.flz@xbsd.org> <43E06B06.80405@root.org> <20060202175041.GA92109@nargothrond.kdm.org> <20060202095828.D97756@ns1.feral.com> <43E252EC.1050803@root.org> <43E25C4D.9020804@samsco.org> <43E2650D.1060109@root.org> <20060202130620.A99168@ns1.feral.com> <43E27E58.4020606@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-scsi@freebsd.org, "Kenneth D. Merry" , Florent Thoumie , Matthew Jacob , Nate Lawson Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/dev/usb umass.c usbdevs X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthew Jacob List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2006 21:51:51 -0000 >> >> >> And how will you distinguish between "not currently enabled" and "not >> supported"? >> > > If WCE is not supported, will the device lie and report the WCE bit as > set? > No. But a device could have it turned off and you wouldn't then infer that you *could*.