From owner-freebsd-scsi@FreeBSD.ORG Thu Oct 31 21:03:59 2013 Return-Path: Delivered-To: FreeBSD-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 49EA0762; Thu, 31 Oct 2013 21:03:59 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1335E22C2; Thu, 31 Oct 2013 21:03:58 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id r9VKrHDC029624; Thu, 31 Oct 2013 14:53:17 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id r9VKrH7H029623; Thu, 31 Oct 2013 14:53:17 -0600 (MDT) (envelope-from ken) Date: Thu, 31 Oct 2013 14:53:17 -0600 From: "Kenneth D. Merry" To: sbruno@freebsd.org Subject: Re: lsi mps(4) vs freebsd mps(4) Message-ID: <20131031205317.GA28812@nargothrond.kdm.org> References: <1383250205.1773.11.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1383250205.1773.11.camel@localhost> User-Agent: Mutt/1.4.2i Cc: "FreeBSD-scsi@freebsd.org" X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Oct 2013 21:03:59 -0000 On Thu, Oct 31, 2013 at 13:10:05 -0700, Sean Bruno wrote: > I just realized that lsi is offering to download FreeBSD drivers for > mps(4) on their website. I also note that the code is substantially > different from our version. > > Is anyone "about to update" mps(4) or should I spend the time and do an > audit? What we have in the tree now is a combination of their Phase 16 driver and our modifications. They have Phase 17 on their web site, and it does have some changes from Phase 16, but not a huge number. I don't know of anyone currently working on integrating their Phase 17 changes into our in-tree driver, so feel free if you have the time. What they need to do at this point is take our changes and integrate them into their driver, so the drivers don't continue to diverge more. Ken -- Kenneth Merry ken@FreeBSD.ORG