From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2a00:1450:4864:20::42d; helo=mail-wr1-x42d.google.com; envelope-from=brad@sensel.com; receiver=edk2-devel@lists.01.org Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 A5FE021A02937 for ; Tue, 5 Feb 2019 12:26:40 -0800 (PST) Received: by mail-wr1-x42d.google.com with SMTP id q15so5092333wro.12 for ; Tue, 05 Feb 2019 12:26:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sensel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3L4jag4GkQqHNBsCFJN5gQm5Se2ay5iEKI9rT6B2ljw=; b=kcmObAP/rZOly8BrxjXr4m50Fiol3ztfNfx7nldo+1sZtZRXZgPvXg4WxHbcgmtnUq 8Gc2Uv/86CZ+NCypnuHkl2ESA0CB927Bfmx0/LwSOF5Vg0gY5qGL9oZ8SaX2nJZOtK/t My3tUQpVutxx3HtNRLgt1x6P5WUIBhk+59zz8+ZEal2boGIvt8aNZKyiqmYvJOzsRtec p0OqYcMrUGthBABoKSVLr6IsnVkwFdL48nFcJzjaadlffpRmcgFBzLaoRdsnXxldeoiJ 00Nib01LbgIg/4ZvKyPdhmitkSQWA788fVOkG73coahAuCzIF4qGeIjcH0kKB6mFYn6j IwcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3L4jag4GkQqHNBsCFJN5gQm5Se2ay5iEKI9rT6B2ljw=; b=bgpPcQGyHvSUSEOlfkrt5Yh3rkUp/teXGeyWFSUnIdkJUhAbtNK/O65+fJ7fHUiBWy +GXi6OSTtDpIOK4mwrGjKVZwE+k+dpNvpiPnFi5s/0T83yo0eFc/dT9LZgKF4TmpqvLt bhq0VYLwf/g+fA7ju316+oGXMhKzBtBbsaQ/K+8A2MOH6Fy4Yf+UnkWjF4TtWv6U2N2I 8ZGfDmkLMTy510WLpZP9xlYEkKcxhT2p1SXDL/KmEcGNHmlem+9x8k1vNgG4c8Xw1gPN 5T+Q2UVuB05mg2MqeqoOffqJVSP782fygeAwco/BJ+RqoClUN7nMWxkn4UW8nRmVbssj CIWg== X-Gm-Message-State: AHQUAub8YoplhgzY3cIH/9P71UvwObm/TLelWFI7JnF8ZsoOQweN0TW3 rr7sE082A5el00xkHZWDFVeSRdKIGyD2m23ARIbBXGUJqSY= X-Google-Smtp-Source: AHgI3IYZ8SIU2h5+CskEy2OoNySz+dwAVxYKc7cMsc7EEyfKLG1U400AXSBRDJ8+TmXCFRHz8M9S+q1WyTMi6aPiWUM= X-Received: by 2002:adf:d146:: with SMTP id b6mr5132653wri.156.1549398398693; Tue, 05 Feb 2019 12:26:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Brad Bozarth Date: Tue, 5 Feb 2019 15:26:27 -0500 Message-ID: To: "Kinney, Michael D" Cc: "edk2-devel@lists.01.org" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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:26:41 -0000 Content-Type: text/plain; charset="UTF-8" Thank you Mike! This is kind of what I thought, but wasn't sure if I was missing 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 produces the Firmware Management Protocol is required. > > There are some protocols to access I2C devices, so the > implementation of the Firmware Management Protocol for > an I2C device can use the I2C protocols to perform the > I2C transactions to update the FW storage device on that > I2C device. > > I am not aware of a standard for updating firmware devices > on I2C busses, so a new UEFI Driver would be required. > > Please let me know if there is a public standard for > this operation that I am not aware of. > > Thanks, > > Mike > > > > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel- > > bounces@lists.01.org] On Behalf 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 a > > standard peripheral fw delivery buit-in, and maybe a > > pointer to a doc or > > source code directory to take a look at? > > > > Thank you, > > Brad > > > > On Tue, Jan 29, 2019 at 4:54 PM Brad Bozarth > > 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 >