From owner-freebsd-scsi Tue Oct 26 23:27:49 1999 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 98F4C14D54 for ; Tue, 26 Oct 1999 23:27:46 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA05855; Wed, 27 Oct 1999 00:27:26 -0600 (MDT) (envelope-from ken) Message-Id: <199910270627.AAA05855@panzer.kdm.org> Subject: Re: Porting a SCSI driver from 2.2.x to 3.x In-Reply-To: <005e01bf2026$2365bf60$0200a8c0@nts-ts1.aims.private> from Chris Knight at "Oct 27, 1999 01:51:15 pm" To: chris@aims.com.au Date: Wed, 27 Oct 1999 00:27:26 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Knight wrote... > Howdy, > Apart from the source and http://www.freebsd.org/~gibbs/, are there any > other references that would assist me in porting a SCSI driver from 2.2.x to > 3.x in a reasonable timeframe? > If there aren't, I'd be willing to document my process and make it > available for other porters/driver coders. Those are probably the best references available. Other than that, there are a number of folks who have done CAM drivers, and I'm sure they would be willing to give you some advice. (Justin Gibbs, Matt Jacob, Warner Losh, Nicolas Souchu, Nick Hibma, Gerard Roudier and Luoqi Chen have all done CAM HBA drivers, so there's no shortage of people with some knowledge on the subject.) If you're willing to document your process, I'm sure that would be helpful to other folks. It might fit well in the FreeBSD handbook. Also, what driver are you going to port? It might be a good idea to tell someone about it so we can avoid any duplicate efforts. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message