From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=148.163.129.52; helo=dispatch1-us1.ppe-hosted.com; envelope-from=tpilar@solarflare.com; receiver=edk2-devel@lists.01.org Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id B09BF211CAF56 for ; Fri, 8 Feb 2019 06:43:01 -0800 (PST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (webmail.solarflare.com [12.187.104.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 00958B400A3 for ; Fri, 8 Feb 2019 14:42:58 +0000 (UTC) Received: from tp-desktop.uk.solarflarecom.com (10.17.20.51) by ocex03.SolarFlarecom.com (10.20.40.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 8 Feb 2019 06:42:54 -0800 To: "edk2-devel@lists.01.org" From: "Tomas Pilar (tpilar)" Message-ID: <5c8dff3b-3bbf-f317-efa9-277bc05b8b10@solarflare.com> Date: Fri, 8 Feb 2019 14:42:53 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 X-Originating-IP: [10.17.20.51] X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24416.005 X-TM-AS-Result: No-3.591000-4.000000-10 X-TMASE-MatchedRID: LSi5+Ear6Yho5oZQZR18EOG5dRZCgxC30nXvwjW2mSV3vUA6/Pi03Mpw GTokcqZCitH9Bj8ikdhwKr4htq/x01tMYJ5fPYtaFYJUGv4DL3y7VvS3iihr21pbYq2f4jz+EWX V+0yBxhc41gdHOuAt53k48PxckV+kTX7PJ/OU3vKDGx/OQ1GV8mMVPzx/r2cb+gtHj7OwNO2Ohz Oa6g8KraaExB4hrXKIbyjWCA/iqCwJxVl25oyHf1bW/wZr+I19xNjT8eQjMl83c/7+xjZ10CtZi fdP4vUTm0JAuFMLkcbhJOJ1n/5Ju46/aQqRmceeKXm3t77x1fEnVRXlM7sTMhmmrgGckMPYx+QT rLb3Iqk= X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--3.591000-4.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24416.005 X-MDID: 1549636978-BxInpZiuLtej Subject: Self-replicating image X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2019 14:43:01 -0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Language: en-US Hi, I am currently pondering the most elegant way to implement capsule update for our devices that would work in the presence of multiple devices in the host. Capsule allows embedding a driver that is executed prior to the update, which is very handy. Crypto library is quite large and would not fit into an OptionROM, so being able to supply FMP driver in the capsule is great. However, if only one instance of the driver loads, the FMP upstream is currently written to support only one device per instance. So I wonder if there is a easy, neat way for my image to replicate on DriverBinding so that I end up with one instance per device. It looks like I should be able to do it with gBS->LoadImage() and passing information about currently loaded image though I might have to CopyMem() the image itself to new location. Thoughts? Cheers, Tom