From owner-freebsd-drivers@FreeBSD.ORG Thu Sep 22 17:46:33 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 469A31065673; Thu, 22 Sep 2011 17:46:33 +0000 (UTC) (envelope-from david.somayajulu@qlogic.com) Received: from TX2EHSOBE001.bigfish.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by mx1.freebsd.org (Postfix) with ESMTP id ED2168FC0A; Thu, 22 Sep 2011 17:46:32 +0000 (UTC) Received: from mail162-tx2-R.bigfish.com (10.9.14.246) by TX2EHSOBE001.bigfish.com (10.9.40.21) with Microsoft SMTP Server id 14.1.225.22; Thu, 22 Sep 2011 17:31:26 +0000 Received: from mail162-tx2 (localhost.localdomain [127.0.0.1]) by mail162-tx2-R.bigfish.com (Postfix) with ESMTP id 8D5CD16B0246; Thu, 22 Sep 2011 17:31:26 +0000 (UTC) X-SpamScore: -6 X-BigFish: VPS-6(zzc85fh14ffOzz1202hzz8275bh8275dhz2ei2a8h668h839h61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: CIP:198.70.193.64; KIP:(null); UIP:(null); IPVD:NLI; H:avexcashub1.qlogic.com; RD:avexcashub2.qlogic.com; EFVD:NLI Received-SPF: neutral (mail162-tx2: 198.70.193.64 is neither permitted nor denied by domain of qlogic.com) client-ip=198.70.193.64; envelope-from=david.somayajulu@qlogic.com; helo=avexcashub1.qlogic.com ; 1.qlogic.com ; Received: from mail162-tx2 (localhost.localdomain [127.0.0.1]) by mail162-tx2 (MessageSwitch) id 1316712685878289_22446; Thu, 22 Sep 2011 17:31:25 +0000 (UTC) Received: from TX2EHSMHS045.bigfish.com (unknown [10.9.14.235]) by mail162-tx2.bigfish.com (Postfix) with ESMTP id C76329F004E; Thu, 22 Sep 2011 17:31:25 +0000 (UTC) Received: from avexcashub1.qlogic.com (198.70.193.64) by TX2EHSMHS045.bigfish.com (10.9.99.145) with Microsoft SMTP Server (TLS) id 14.1.225.22; Thu, 22 Sep 2011 17:31:18 +0000 Received: from avexmb1.qlogic.org ([fe80::9545:3a4f:c131:467d]) by avexcashub2.qlogic.org ([::1]) with mapi; Thu, 22 Sep 2011 10:31:17 -0700 From: David Somayajulu To: "freebsd-current@freebsd.org" , "freebsd-drivers@freebsd.org" Date: Thu, 22 Sep 2011 10:31:15 -0700 Thread-Topic: Recommended methods to upgrade firmware on HBAs Thread-Index: Acx5TW4ghoylo64wQjGQ7FegAezJ7g== Message-ID: <75E1A2A7D185F841A975979B0906BBA67BCCAB75FA@AVEXMB1.qlogic.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-OriginatorOrg: qlogic.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Recommended methods to upgrade firmware on HBAs X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 17:46:33 -0000 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 a= s a separate file, which is then made accessible to the corresponding devi= ce driver during device initialization? 3. Is there a restriction on the size of driver.ko file? If not, is i= t acceptable to provide the firmware as fw_file.c which is then compiled in= to the driver. Thanks david S. ________________________________ This message and any attached documents contain information from QLogic Cor= poration 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 n= otify the sender immediately by reply e-mail and then delete this message.