From owner-freebsd-hardware@freebsd.org Fri Nov 2 13:36:58 2018 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A710E10F7211 for ; Fri, 2 Nov 2018 13:36:58 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F0C16AEA2 for ; Fri, 2 Nov 2018 13:36:57 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from roundcube.fjl.org.uk (localhost [127.0.0.1]) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id wA2DaeUt073497 for ; Fri, 2 Nov 2018 13:36:44 GMT (envelope-from frank2@fjl.co.uk) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 02 Nov 2018 13:36:40 +0000 From: Frank Leonhardt To: freebsd-hardware@freebsd.org Subject: Fwd: Re: When is sataIII actually =?UTF-8?Q?sataIII=3F?= Organization: FJL Microsystems Message-ID: X-Sender: frank2@fjl.co.uk User-Agent: Roundcube Webmail/0.9.2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 13:36:58 -0000 On Thu, Nov 1, 2018, at 8:45 AM, spamless@mail-on.us wrote: > I have another Sata 3 drive on the second Sata 3 port, that FreeBSD > actually treats as what it is: > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ACS-2 ATA SATA 3.x device > ada1: Serial Number W1F55VT9 > ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 2861588MB (5860533168 512 byte sectors) > ada1: quirks=0x1<4K> > > note the "quirks" - is that good, or bad? > Forgot to mention (and then the power went off) - the quirks mechanism is to allow work-arounds for flawed implementations of protocols from specific devices. For example, if a particular drive always returns the same serial number to satisfy the protocol, it's a quirk and the driver won't make use of the query serial number command for that type of drive. Regards, Frank.