From owner-freebsd-scsi@FreeBSD.ORG Sun Oct 29 07:48:29 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DACF16A403 for ; Sun, 29 Oct 2006 07:48:29 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E01543D4C for ; Sun, 29 Oct 2006 07:48:28 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1Ge5P9-000Eab-2b; Sun, 29 Oct 2006 09:48:27 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: "Matthew Jacob" In-reply-to: <7579f7fb0610281836t4f13efcfm15c1b238cff96a7@mail.gmail.com> References: <7579f7fb0610281836t4f13efcfm15c1b238cff96a7@mail.gmail.com> Comments: In-reply-to "Matthew Jacob" message dated "Sat, 28 Oct 2006 18:36:33 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Oct 2006 09:48:26 +0200 From: Danny Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2006 07:48:29 -0000 > Documentation: > > Not really. There really is very little documentation about CAM in > FreeBSD. The best documentation is the code, followed closely by > asking the opinion of all who develop within the framework about what > *they* think something means. > ah, now i feel ok, I haven't started to write iscsi.man yet > The switch to CAM_NEW_TRAN_CODE is way overdue. It's been around now > for years and was an attempt to make the CAM layer more accomodating > of different types of transports and protocols. > > iSCSI: > I don't know - I haven't played with your iSCSI driver yet. I would > actually expect things to be substantially easier as you can then make > iSCSI a transport protocol and do transport specific things within it > which are awkward otherwise. > ok, i'll bite the bullet, any driver I can use as guidline? danny