From owner-aic7xxx@FreeBSD.ORG Mon Nov 13 03:10:20 2006 Return-Path: X-Original-To: aic7xxx@freebsd.org Delivered-To: aic7xxx@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FBE116A407 for ; Mon, 13 Nov 2006 03:10:20 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from ns1.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5249E43D46 for ; Mon, 13 Nov 2006 03:10:20 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from [192.168.0.6] (tumnus.scsiguy.org [192.168.0.6]) (authenticated bits=0) by ns1.scsiguy.com (8.13.6/8.13.6) with ESMTP id kAD3AFj0067262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 12 Nov 2006 20:10:16 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-ID: <4557E20A.4030603@scsiguy.com> Date: Sun, 12 Nov 2006 20:10:02 -0700 From: "Justin T. Gibbs" User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: admin@cordef.net.pl References: <455632E8.5020301@cordef.net.pl> <4557484D.4050505@scsiguy.com> <45574C1C.5070404@cordef.net.pl> <45576259.9040605@scsiguy.com> <45579283.7080302@cordef.net.pl> In-Reply-To: <45579283.7080302@cordef.net.pl> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: aic7xxx@freebsd.org Subject: Re: Adaptec 29160 + Fujitsu MAS3367NC - cannot force U160 X-BeenThere: aic7xxx@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Adaptec Device Drivers in FreeBSD and Linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 03:10:20 -0000 > Well, I don't think devices are forced to SE, at lest not because of > jumper setting. I checked - on IBM drive this jumper is opened and > Fujitsu doesn't have one at all. The only one source of problems I can > see is adapter. It has the DIFFSNS signal left not connected. > Theoretically it means device is set to differential. But what if > controller forces it to low? Tomorrow I'll try to connect it to the +5V > and see what will happen. I wouldn't force the state of that line without better understanding what's going on here. > Justin, let me ask you one more question: I wonder where is the setting > "GOAL" taken from? I understand that "USER" is a maximum possible > transfer for the interface and "CURR" is maximum possible transfer for > the device (calculated at DV stage). Is this setting connected with > state of bus - i.e. if bus is SE then GOAL is forced to be 40.0 instead > of 160.0? Or it is set somewhere in device EEPROM? USER = settings in the eeprom or set via /proc GOAL = device/bus limited version of USER (see ahc_devlimited_syncrate()) CURR = Active negotiated state (both the controller and the end device believe this is the current transfer agreement) -- Justin