From owner-freebsd-drivers@FreeBSD.ORG Thu Sep 22 18:57:01 2011 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F84F106564A for ; Thu, 22 Sep 2011 18:57:01 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 1304D8FC12 for ; Thu, 22 Sep 2011 18:57:00 +0000 (UTC) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p8MIemjJ089528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Sep 2011 11:40:48 -0700 (PDT) (envelope-from mj@feral.com) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.4/8.14.4/Submit) with ESMTP id p8MIelV8089525; Thu, 22 Sep 2011 11:40:47 -0700 (PDT) (envelope-from mj@feral.com) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Thu, 22 Sep 2011 11:40:47 -0700 (PDT) From: Matthew Jacob To: David Somayajulu In-Reply-To: <75E1A2A7D185F841A975979B0906BBA67BCCAB75FA@AVEXMB1.qlogic.org> Message-ID: References: <75E1A2A7D185F841A975979B0906BBA67BCCAB75FA@AVEXMB1.qlogic.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (ns1.feral.com [127.0.0.1]); Thu, 22 Sep 2011 11:40:48 -0700 (PDT) Cc: "freebsd-current@freebsd.org" , "freebsd-drivers@freebsd.org" Subject: Re: Recommended methods to upgrade firmware on HBAs X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 18:57:01 -0000 The current firmware(9) mechanism might work for you. The QLogic FC/SCSI cards in FreeBSD use that for loading firmware images to download to the cards, albeit to just load and reset, to update flash. This allows the drivers themselves to request updates. Note that the root filesystem has to be mounted for this mechanism to work. Other mechanisms include ioctl mechanisms as per what the LSI cards do via the mpiutil and mfiutil programs. On Thu, 22 Sep 2011, David Somayajulu wrote: > Hi All, > > 1. What is the current recommended method for upgrading firmware for HBAs? > > 2. Is there a mechanism wherein the firmware binary can be provided as a separate file, which is then made accessible to the corresponding device driver during device initialization? > > 3. Is there a restriction on the size of driver.ko file? If not, is it acceptable to provide the firmware as fw_file.c which is then compiled into the driver. > Thanks > david S. > > > ________________________________ > This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >