From owner-freebsd-scsi@FreeBSD.ORG Sun Aug 12 00:40:16 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22EEC106568B; Sun, 12 Aug 2012 00:40:16 +0000 (UTC) (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 CB8CC8FC08; Sun, 12 Aug 2012 00:40:09 +0000 (UTC) Received: from [192.168.135.103] (c-76-126-166-136.hsd1.ca.comcast.net [76.126.166.136]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q7C0e3cf071378 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Aug 2012 17:40:04 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <5026FB5E.8010800@feral.com> Date: Sat, 11 Aug 2012 17:39:58 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: John References: <4FDB6F06.6080108@feral.com> <201208102144.25605.bruce@cran.org.uk> <5026772D.9040502@feral.com> <20120811215848.30d107ae@parvati.thanelange.no> <20120811202623.GA29895@FreeBSD.org> In-Reply-To: <20120811202623.GA29895@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Sat, 11 Aug 2012 17:40:05 -0700 (PDT) Cc: Bruce Cran , freebsd-scsi@FreeBSD.ORG Subject: Re: headsup on enclosure driver X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Jacob List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2012 00:40:16 -0000 On 8/11/2012 1:26 PM, John wrote: > ----- Gyrd Thane Lange's Original Message ----- >> ..e messages. :-) > Reducing these msgs is straight forward. However, is their implementation > incorrect, or are they returning a format the driver doesn't understand? > > Thoughts? > > Cheers! > John Looks like noncompliant hardware. What a surprise.