From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.43; helo=mga05.intel.com; envelope-from=mark.doran@intel.com; receiver=edk2-devel@lists.01.org Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id BCF3D21A07A82 for ; Tue, 5 Feb 2019 12:42:35 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Feb 2019 12:42:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,336,1544515200"; d="scan'208";a="112644662" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by orsmga007.jf.intel.com with ESMTP; 05 Feb 2019 12:42:34 -0800 Received: from orsmsx159.amr.corp.intel.com (10.22.240.24) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 5 Feb 2019 12:42:34 -0800 Received: from orsmsx109.amr.corp.intel.com ([169.254.11.204]) by ORSMSX159.amr.corp.intel.com ([169.254.11.106]) with mapi id 14.03.0415.000; Tue, 5 Feb 2019 12:42:34 -0800 From: "Doran, Mark" To: Brad Bozarth , "Kinney, Michael D" CC: "edk2-devel@lists.01.org" Thread-Topic: [edk2] Peripheral FW capsule delivery? Thread-Index: AQHUuB55vxE7YSrPBUK8KYBd7LqjhqXSIbsAgAAOZgCAAAfigP//fMcQ Date: Tue, 5 Feb 2019 20:42:33 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDY1MzBmYmMtNzJmMC00MjliLWI5YmMtZDAzMzIzM2I4NzEzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTjhwVlFjSHlqNER0QUpQTkFhUHNxNXhKY3lXUHZpUlVtXC9cL08yVjV2Tkc2S0o4R1lXUDJ0OFZKaENZd09PcDVMIn0= x-originating-ip: [10.22.254.140] MIME-Version: 1.0 Subject: Re: Peripheral FW capsule delivery? 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: Tue, 05 Feb 2019 20:42:36 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Brad: One other possible path you might be able to consider. Have you looked at = Component Firmware Update as a way to manage in-device firmware?? While th= at originates with Microsoft, it's open source and OS neutral and might be = an easier overall.=20 https://blogs.windows.com/buildingapps/2018/10/17/introducing-component-f= irmware-update/ As a general rule of thumb, I'd always advise that your first choice should= be to move any work out of the Pre-OS space and into OS-present space wher= ever possible. -- Cheers, Mark. -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Brad= Bozarth Sent: Tuesday, February 5, 2019 12:26 PM To: Kinney, Michael D Cc: edk2-devel@lists.01.org Subject: Re: [edk2] Peripheral FW capsule delivery? Thank you Mike! This is kind of what I thought, but wasn't sure if I was mi= ssing something. I will let you know if I come across any standard. -Brad On Tue, Feb 5, 2019 at 2:58 PM Kinney, Michael D wrote: > Hi Brad, > > In order to update a FW storage device in UEFI, a UEFI driver that=20 > produces the Firmware Management Protocol is required. > > There are some protocols to access I2C devices, so the implementation=20 > of the Firmware Management Protocol for an I2C device can use the I2C=20 > protocols to perform the I2C transactions to update the FW storage=20 > device on that I2C device. > > I am not aware of a standard for updating firmware devices on I2C=20 > busses, so a new UEFI Driver would be required. > > Please let me know if there is a public standard for this operation=20 > that I am not aware of. > > Thanks, > > Mike > > > > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel- bounces@lists.01.org] On Behalf=20 > > Of Brad Bozarth > > Sent: Tuesday, February 5, 2019 11:07 AM > > To: edk2-devel@lists.01.org > > Subject: Re: [edk2] Peripheral FW capsule delivery? > > > > I would really appreciate a small pointer on this - yes/no on if is=20 > > a standard peripheral fw delivery buit-in, and maybe a pointer to a=20 > > doc or source code directory to take a look at? > > > > Thank you, > > Brad > > > > On Tue, Jan 29, 2019 at 4:54 PM Brad Bozarth =20 > > wrote: > > > > > Hi! > > > > > > I am implementing firmware for a touchpad that will > > be going into a > > > laptop, connected via i2c. We would like to take > > advantage of the UEFI > > > firmware capsule delivery method for firmware updates > > if possible. I am > > > struggling to find out how to do this. In particular, > > I'd like to know > > > whether there is a "standard" delivery mechanism we > > can take advantage of > > > and communicate with from the firmware side over i2c, > > or if we need to > > > write UEFI driver code of some sort to pass the > > update down. We'd love to > > > leverage a standard pipe that dumps an update over > > i2c if possible and > > > implement what we need to on the firmware side. We > > are supplying our > > > touchpad to the laptop OEM and they are distant and > > have their own software > > > teams, so if we need to write UEFI code, it > > complicates matters! > > > > > > This is the page that I'd love to read, if it were > > filled out :) > > > https://github.com/mdkinney/edk2/wiki/Capsule-Based- > > Device-Firmware-Update > > > > > > Thank you! > > > Brad > > > > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel