From: Lei YU <mine260309@gmail.com>
To: "Bonnie Lo/WYHQ/Wiwynn" <Bonnie_Lo@wiwynn.com>
Cc: Joseph Reynolds <jrey@linux.ibm.com>,
Neeraj Ladkani <neladk@microsoft.com>,
Alexander Tereschenko <aleksandr.v.tereschenko@linux.intel.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
Patrick Venture <venture@google.com>,
"Aldofo Lin/WYHQ/Wiwynn" <ALDOFO_LIN@wiwynn.com>,
"Delphine Chiu/WYHQ/Wiwynn" <DELPHINE_CHIU@wiwynn.com>
Subject: Re: [EXTERNAL] Re: BMC update via TFTP
Date: Wed, 11 Dec 2019 13:59:30 +0800 [thread overview]
Message-ID: <CAARXrtkKT=KHAQ3DPTh_CoSCCLGjojC73-v6L+a4XY94pbE3RA@mail.gmail.com> (raw)
In-Reply-To: <HK0PR02MB27870548BFF1A91BC86ADC19F85A0@HK0PR02MB2787.apcprd02.prod.outlook.com>
On Wed, Dec 11, 2019 at 12:58 PM Bonnie Lo/WYHQ/Wiwynn
<Bonnie_Lo@wiwynn.com> wrote:
>
> Dear Joseph,
>
> In my understanding, the BMC firmware update flow is as below:
> 1. Trigger reboot
> 2. Systemd stop all service
> 3. Unmount file system
> 4. image is in /run/initramfs
> 5. Do the flashcp command to update the flash
>
> If there is any misunderstanding, please correct me.
>
> Based on the discussion with Neeraj.
> We want to be able to update BMC firmware without having to trigger the BMC reboot command before the system do flashcp command.
> It means that we can do the flashcp first. If the flashcp command complete and success, then we do the reset manually.
> Is it workable on current upstream code?
> If not, why? I means is there any advantage to trigger the reboot before we do the flashcp.
It is not safe to flashcp the flash chip while BMC is running on it,
because BMC's filesystem is mounted on the flash's RO and RW
partitions.
next prev parent reply other threads:[~2019-12-11 5:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 12:02 BMC update via TFTP rgrs
2019-12-03 16:12 ` Gunnar Mills
2019-12-03 17:08 ` Gunnar Mills
2019-12-03 19:55 ` Adriana Kobylak
2019-12-04 15:47 ` Joseph Reynolds
2019-12-04 21:36 ` Vernon Mauery
2019-12-05 11:05 ` Alexander Tereschenko
2019-12-05 22:37 ` Vernon Mauery
2019-12-06 14:03 ` Alexander Tereschenko
2019-12-06 22:52 ` Joseph Reynolds
2019-12-09 16:06 ` Alexander Tereschenko
2019-12-10 1:25 ` Joseph Reynolds
2019-12-10 18:58 ` [EXTERNAL] " Neeraj Ladkani
2019-12-10 21:10 ` Joseph Reynolds
2019-12-11 4:56 ` Bonnie Lo/WYHQ/Wiwynn
2019-12-11 5:59 ` Lei YU [this message]
2019-12-11 21:51 ` Milton Miller II
2019-12-11 11:02 ` Alexander Tereschenko
2019-12-11 20:17 ` Joseph Reynolds
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='CAARXrtkKT=KHAQ3DPTh_CoSCCLGjojC73-v6L+a4XY94pbE3RA@mail.gmail.com' \
--to=mine260309@gmail.com \
--cc=ALDOFO_LIN@wiwynn.com \
--cc=Bonnie_Lo@wiwynn.com \
--cc=DELPHINE_CHIU@wiwynn.com \
--cc=aleksandr.v.tereschenko@linux.intel.com \
--cc=jrey@linux.ibm.com \
--cc=neladk@microsoft.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.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.