Date: Sun, 29 Oct 2006 09:48:26 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: "Matthew Jacob" <lydianconcepts@gmail.com> Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN Message-ID: <E1Ge5P9-000Eab-2b@cs1.cs.huji.ac.il> In-Reply-To: <7579f7fb0610281836t4f13efcfm15c1b238cff96a7@mail.gmail.com> References: <E1GdoR8-0007SG-Re@cs1.cs.huji.ac.il> <7579f7fb0610281836t4f13efcfm15c1b238cff96a7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Ge5P9-000Eab-2b>