From: Joseph Reynolds <jrey@linux.ibm.com>
To: Timothy Pearson <tpearson@raptorengineering.com>,
Milton Miller II <miltonm@us.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC on RCS platforms - remote media
Date: Wed, 28 Apr 2021 16:24:59 -0500 [thread overview]
Message-ID: <4f9a94a5-bafb-aec8-f229-95a2fdf480c2@linux.ibm.com> (raw)
In-Reply-To: <405234093.18656550.1619641318362.JavaMail.zimbra@raptorengineeringinc.com>
On 4/28/21 3:21 PM, Timothy Pearson wrote:
>
> ----- Original Message -----
>> From: "Milton Miller II" <miltonm@us.ibm.com>
>> To: "Timothy Pearson" <tpearson@raptorengineering.com>
>> Cc: "Patrick Williams" <patrick@stwcx.xyz>, "openbmc" <openbmc@lists.ozlabs.org>
>> Sent: Monday, April 26, 2021 4:42:16 PM
>> Subject: RE: OpenBMC on RCS platforms
> [snip]
>
>
...snip...
>>> I just need to launch a GUI tool with host administrative privileges,
>>> select the upgrade file, and queue an upgrade to happen when I reboot
>>> the machine. I queue the update, start the reboot, and stick around
>>> to see the upgrade progress on the screen while it's booting back up.
>>> Because I can see the status on the screen, I know what is happening
>>> and don't pull the power plug due to only seeing a black screen and
>>> power LED for 10 minutes. Finally, the machine loads the OS and I
>>> verify the new control widget is working properly.
>> If the gui is on the host, with todays stock phosphor-initfs, you need
>> 1) a connection from the host to the bmc
>> ethernet, serial, usb ethernet etc
>> (to copy files from host to BMC RAM and to monitor command output)
> Precisely. USB would be an interesting control channel, but I don't think OpenBMC currently supports this kind of access?
If (if) I am following correctly, you want the OpenBMC virtual media
(aka remote media) implementation?
https://github.com/openbmc/docs/blob/master/designs/virtual-media.md
Is there an implementation? I didn't find one listed here:
https://github.com/openbmc/docs/blob/master/features.md
- Joseph
next prev parent reply other threads:[~2021-04-28 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 14:30 OpenBMC on RCS platforms Timothy Pearson
2021-04-23 17:11 ` Patrick Williams
2021-04-23 18:46 ` Timothy Pearson
2021-04-26 21:42 ` Milton Miller II
2021-04-28 20:21 ` Timothy Pearson
2021-04-28 21:24 ` Joseph Reynolds [this message]
2021-06-03 12:29 ` OpenBMC on RCS platforms - remote media Konstantin Klubnichkin
2021-04-29 7:54 ` OpenBMC on RCS platforms Milton Miller II
2021-04-23 17:23 ` Ed Tanous
2021-04-23 19:00 ` Timothy Pearson
2021-04-23 19:23 ` 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=4f9a94a5-bafb-aec8-f229-95a2fdf480c2@linux.ibm.com \
--to=jrey@linux.ibm.com \
--cc=miltonm@us.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tpearson@raptorengineering.com \
/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.