public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Brad Bozarth <brad@sensel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: Peripheral FW capsule delivery?
Date: Tue, 5 Feb 2019 19:58:14 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B8B9008E@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <CABP0pR-3uUz-1NJz7g0vwsGJYiQbMOVfZmFm1ounDnseKGqwFA@mail.gmail.com>

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
> <brad@sensel.com> 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


  reply	other threads:[~2019-02-05 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 21:54 Peripheral FW capsule delivery? Brad Bozarth
2019-02-05 19:06 ` Brad Bozarth
2019-02-05 19:58   ` Kinney, Michael D [this message]
2019-02-05 20:26     ` Brad Bozarth
2019-02-05 20:42       ` Doran, Mark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E92EE9817A31E24EB0585FDF735412F5B8B9008E@ORSMSX113.amr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox