From: Vijay Khemka <vijaykhemka@fb.com>
To: Ed Tanous <edtanous@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: VR control from the BMC
Date: Tue, 27 Oct 2020 20:11:42 +0000 [thread overview]
Message-ID: <03C3FC4D-083C-4949-9661-35CF6E7561D3@fb.com> (raw)
In-Reply-To: <CAH2-KxDbgY8kozOotA+qjzAP0cqTcK9Ooys9b05Szv4MRk8wrA@mail.gmail.com>
I don't have the need to upgrade VR firmware out of band today, but if
you're interested in helping define interfaces that would work for
firmware upgrade or make it easy to add in the future, I'd appreciate
the help.
I will certainly look into this as this is lower in my priority tasks.
next prev parent reply other threads:[~2020-10-27 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 23:02 VR control from the BMC Ed Tanous
2020-10-27 18:55 ` Vijay Khemka
2020-10-27 19:10 ` Ed Tanous
2020-10-27 20:11 ` Vijay Khemka [this message]
2020-10-27 20:26 ` Patrick Williams
2020-10-27 20:54 ` Ed Tanous
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=03C3FC4D-083C-4949-9661-35CF6E7561D3@fb.com \
--to=vijaykhemka@fb.com \
--cc=edtanous@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).