From owner-freebsd-scsi@freebsd.org Fri May 12 06:09:36 2017 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D1E5D69B51 for ; Fri, 12 May 2017 06:09:36 +0000 (UTC) (envelope-from ram.vegesna@broadcom.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FA8B124C for ; Fri, 12 May 2017 06:09:36 +0000 (UTC) (envelope-from ram.vegesna@broadcom.com) Received: by mail-wr0-x22e.google.com with SMTP id l50so36637054wrc.3 for ; Thu, 11 May 2017 23:09:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zI3DjAYSEC0m9SRcQvo5lAEgqzLTcCpScMxIBsGU8rQ=; b=Ow2Qxa18PvNx3Nc+8w3PFktWAHfi+Gb069+P/+TiTiduZDI4wsqgFGw+IH4I137pdL LP4aup821E+HOv1lIy8y1DkBejOFLbYwCX3t/aXA/C5IqY9L0pW2nHqtHGu8OzaVGpb2 EdMswRmD4Zw08hnAclC95/br+WgVsBU5qqzbI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zI3DjAYSEC0m9SRcQvo5lAEgqzLTcCpScMxIBsGU8rQ=; b=ui43OQ2hZHCkD5xgdH7p3D5YhvX+6tYU23YNQ/b09uImXoHKc6l1E0NSwf6xYAYgoC ZaYvzrL0GysNcGPPKTXCfUEPgeAYs7toqZtMPK2XbVgmr42fpfMxzzCvmm6w5qJWWauG MzoYMq0egguJ8v47INGtSjJgCssIg6q1yyyk+rhG5Qo4ObbpWkiuKCUi8/jbAt28gCq1 rNg9aJocsNnUCgrUuknpjmJrYT4tlitrZR3ZihfCu4hCsBwWc1Wr0nLBwOgAH0qbIcxx y/n4XdfpR/+U4sRNKThZ4bIHjOtRR5J+LbcAh8YR0so4wS4/kKlDNHPTHkjNUWpMMOLH 9OZw== X-Gm-Message-State: AODbwcCzviteJDgY4uBVXex7nRsJh73vyHHgbpnOY9NM/GI0SFKHPizG RRI8Tiwx6oYzI/phLCzYTG5zbJ9DHCCK X-Received: by 10.46.21.15 with SMTP id s15mr535232ljd.50.1494569374275; Thu, 11 May 2017 23:09:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.80.70 with HTTP; Thu, 11 May 2017 23:09:33 -0700 (PDT) In-Reply-To: <964F0DBF-DEEB-4CD8-844D-1099FF5AB383@freebsd.org> References: <964F0DBF-DEEB-4CD8-844D-1099FF5AB383@freebsd.org> From: Ram Kishore Vegesna Date: Fri, 12 May 2017 11:39:33 +0530 Message-ID: Subject: Re: Fiber channel driver for Broadcom/Emulex FC host bus adapters. To: Ken Merry Cc: freebsd-scsi@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2017 06:09:36 -0000 Hi Ken, Thanks for the quick response. I am working on restructuring the driver code which will be good for integrating into FreeBSD. Will post the driver for review once its done. -Ram On Fri, May 12, 2017 at 12:33 AM, Ken Merry wrote: > That is good news! It will be good to have the driver in the tree. > > As for how to get it into FreeBSD: > > 1. Make sure it is BSD-licsened. GPLed code isn=E2=80=99t allowed in the= kernel. > Other licenses (MIT, CDDL) might be possible. Here is an example license= : > > https://svnweb.freebsd.org/base/head/share/examples/etc/ > bsd-style-copyright?revision=3D180207&view=3Dmarkup > > 2. Get a committer to review it. I can do that if you like. I may still > have some 16Gb boards from when I was reviewing the Emulex FC driver in > 2012. > > 3. Once you get past the review, you can either have the committer put it > in the tree, or wait until we get one or more Emulex developers approved = as > committers. See #4. > > 4. Decide on one or more Emulex developers to maintain the driver as > FreeBSD committers. These should be people who are likely to stay on the > project for a while, so new folks don=E2=80=99t need to be brought up to = speed too > often. The new committers will need one or more current committers as > mentors, and all commits will have to be approved until the mentor is > satisfied that the new committer is ready to go on their own. The > committers=E2=80=99 guide will give you an idea of what is involved: > > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ > > The eventual goal will be to have one or more Emulex folks who are > committers and can maintain the driver in the FreeBSD tree. > > There are two FreeBSD committers (at least) from Broadcom, Steve McConnel= l > and Kashyap Desai. They work on the SAS and MegaRAID products. > > As for timelines, we=E2=80=99re about to start the process for FreeBSD 11= .1. > Depending on the state of the driver, it may be possible to get it into > 11.1, but it=E2=80=99s hard to say that with any certainty until we see t= he driver. > > Ken > =E2=80=94 > Ken Merry > ken@FreeBSD.ORG > > > > On May 11, 2017, at 10:16 AM, Ram Kishore Vegesna via freebsd-scsi < > freebsd-scsi@freebsd.org> wrote: > > Hi all, > > We are planning to upstream/inbox our FreeBSD cam driver which supports > Emulex FC host bus adapters (LPe16xx and LPe32xx family). > > Please provide me the inputs on process of up-streaming driver. If you ca= n > share any documents related to that will be of great help. > > Note: Please correct me if I am posting the request on wrong mailing list= . > If possible provide the maintainer contact. > > Thanks, > Ram > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > >