From: Patrick Venture <venture@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Uploading firmware in-band
Date: Fri, 9 Mar 2018 16:01:23 -0800 [thread overview]
Message-ID: <CAO=notykSOGC0DbHeY_4bZZ2oCw=rcpfT=kK3=0f-WSOOjFx+Q@mail.gmail.com> (raw)
I've pushed this for comments,
https://gerrit.openbmc-project.xyz/#/c/9497/1 - it's the BMC-side of
our implementation for receiving the BMC image. It supports LPC, PCI,
and in-band IPMI as a transport mechanism. it doesn't dig into the
signature stuff or the flashing portions, however it does assume there
is a signature verification service, and can receive the signature
itself.
Regards,
Patrick
reply other threads:[~2018-03-10 0:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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='CAO=notykSOGC0DbHeY_4bZZ2oCw=rcpfT=kK3=0f-WSOOjFx+Q@mail.gmail.com' \
--to=venture@google.com \
--cc=openbmc@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.