From owner-freebsd-current@FreeBSD.ORG  Thu Jul 30 19:35:01 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 901E6106566B;
	Thu, 30 Jul 2009 19:35:01 +0000 (UTC) (envelope-from mav@FreeBSD.org)
Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121])
	by mx1.freebsd.org (Postfix) with ESMTP id D5FE18FC1D;
	Thu, 30 Jul 2009 19:35:00 +0000 (UTC) (envelope-from mav@FreeBSD.org)
Received: from [95.109.128.107] (account mav@alkar.net HELO
	mavbook.mavhome.dp.ua)
	by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9)
	with ESMTPSA id 250239329; Thu, 30 Jul 2009 22:34:53 +0300
Message-ID: <4A71F5D3.4040602@FreeBSD.org>
Date: Thu, 30 Jul 2009 22:34:43 +0300
From: Alexander Motin <mav@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.21 (X11/20090405)
MIME-Version: 1.0
To: Mike Tancsa <mike@sentex.net>
References: <4A4517BE.9040504@FreeBSD.org>
	<200907301706.n6UH6HrY047414@lava.sentex.ca>
	<4A71D739.6040308@FreeBSD.org>
	<200907301901.n6UJ1fjV047967@lava.sentex.ca>
In-Reply-To: <200907301901.n6UJ1fjV047967@lava.sentex.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-Current <freebsd-current@freebsd.org>, scottl@freebsd.org
Subject: Re: RFC: ATA to CAM integration patch
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2009 19:35:01 -0000

Mike Tancsa wrote:
> One other detail, on the drive info, why does it show - for NCQ status ?
> 
> Native Command Queuing (NCQ)   yes       -      31/0x1F

NCQ doesn't need to be enabled or disabled on drive. It just can be 
present/used or not. And that is what ada driver reports during attach.

-- 
Alexander Motin