From owner-freebsd-scsi Mon Feb 12 19:33:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4BF1A37B491; Mon, 12 Feb 2001 19:33:53 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA56588; Mon, 12 Feb 2001 20:33:52 -0700 (MST) (envelope-from ken) Date: Mon, 12 Feb 2001 20:33:52 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: XPT_GET_TRAN_SETTINGS Message-ID: <20010212203352.A56560@panzer.kdm.org> References: <200102130237.f1D2bum02828@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200102130237.f1D2bum02828@mass.dis.org>; from msmith@FreeBSD.ORG on Mon, Feb 12, 2001 at 06:37:56PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Feb 12, 2001 at 18:37:56 -0800, Mike Smith wrote: > > Just adding support for this to the 'mly' driver, and I've noticed > something odd. I am *not* setting the CCB_TRANS_SYNC_RATE_VALID > bit in the valid field of the reply, but I'm still getting a transfer > speed printed. Any idea what's going on here? Well, the code in xpt_announce_periph() looks to see if the sync offset is valid. If it is, it uses the supplied sync period (without checking the valid bit...) to calculate the transfer speed. Otherwise, it issues a path inquiry CCB and prints out the base transfer speed for the device, multiplied by the bus width in bytes. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message