From owner-freebsd-current Thu Apr 23 07:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09106 for freebsd-current-outgoing; Thu, 23 Apr 1998 07:47:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero-fddi.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA09081 for ; Thu, 23 Apr 1998 07:47:36 -0700 (PDT) (envelope-from shimon@sendero-fddi.simon-shapiro.org) Received: (qmail 14866 invoked by uid 1000); 23 Apr 1998 13:57:07 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-040798 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980416100139.T1090@freebie.lemis.com> Date: Thu, 23 Apr 1998 06:57:07 -0700 (PDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Greg Lehey Subject: Re: A CAM of worms Cc: freebsd-current@FreeBSD.ORG, Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Apr-98 Greg Lehey wrote: ... > I agree. Although I use CAM, and it works for me, and it seems a > whole lot better than the old driver, it's not finished yet. I > currently have both the old and new drivers in my source tree. If > it's too much trouble to keep the old version after the new one has > taken up its final place, maybe it should be left where it is at the > moment (/sys/cam) until CAM can do everything the old driver could do. > This would have the advantage for Justin that it's almost no work. I am sorry to have joined this discussion so late. I was on the road and no access to the net for all this time. My exceptions to the proposed plan: * No migration path; The is no mechanism to migrate at all. We need a way to have the same system boot either way. We need a mechanism to maintain source for the old systems and switch back. * No migration guide; The is no documentation on the new mechanism, its interfeaces, requirements, etc. I asked, several times, politely, and privately, for at least a list of functions, their intended purpose and the entry points into both HBA drivers and personality drivers. The ``I do not have time'' answer is simply not enough. If there is no time to list the API's maybe the code change should be held until there is time. * The idea of overnight obsolesence of all the existing SCSI code is a bit, shall we say, aggressive. Although I have all the confidence in the world that the CAM code is wonderfully reliable, efficient and great, sone of us earthly mortals would like to have a chance to compile and run the two systems side by side, at least until the porting is done. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message