From: Adriana Kobylak <anoo@linux.ibm.com>
To: Lei YU <mine260309@gmail.com>,
Bright Cheng/WYHQ/Wiwynn <Bright_Cheng@wiwynn.com>
Cc: openbmc@lists.ozlabs.org, Adriana Kobylak <anoo@us.ibm.com>,
Neeraj Ladkani <neladk@microsoft.com>,
Delphine Chiu/WYHQ/Wiwynn <DELPHINE_CHIU@wiwynn.com>,
Jayanth Othayoth <ojayanth@in.ibm.com>,
Gunnar Mills <gmills@linux.vnet.ibm.com>,
Ratan Gupta <ratagupt@linux.vnet.ibm.com>,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: phosphor-bmc-code-memt: Support redfish remote firmware update with static layout image
Date: Fri, 15 Nov 2019 10:00:14 -0600 [thread overview]
Message-ID: <0f356ff58ad9ec48b19e86f9da5eb7cc@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAARXrtnjxJw4S25CoBACzY8A8hQtV+8excmoM2iNR5sLqhxcXg@mail.gmail.com>
>> phosphor-bmc-code-memt doesn’t support static-layout remote update
>> since static layout fw package could only has “image-bmc” in the
>> package.
>
> For now, it does support static layout, you just need to upload the
> tarball contains separated images, instead of the whole "image-bmc"
> tarball.
>
Checking the build files, the *.static.mtd.all.tar contains the
image-bmc, manifest and signature files so yeah we can just upload that
file without any build changes, we just need to add the support in the
bmc-code-mgmt repo.
>>
>>
>> Following are the modifications
>>
>> 1. Add a name list for static layout only has image-bmc in the fw
>> package and modify related image file checking.
>>
>> 2. Add checking ApplyTime property for static layout to decide whether
>> reboot to apply update process or not.
>>
>>
>>
>> Please find the patch for these modifications in the attachment.
Looks good, if you could just break the patch into two separate patches,
one for the supporting image-bmc and one for adding the ApplyTime
property, and submit via gerrit as Lei YU pointed. Let us know if you
have any questions with the process. Thanks!
>
> It may be useful to support the whole image as well, so please submit
> the code to gerrit, and we could review the code.
> Please follow
> https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-server-to-openbmc
> for how to submit changes to gerrit.
> Thanks!
next prev parent reply other threads:[~2019-11-15 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 2:24 phosphor-bmc-code-memt: Support redfish remote firmware update with static layout image Bright Cheng/WYHQ/Wiwynn
2019-11-15 2:51 ` Lei YU
2019-11-15 16:00 ` Adriana Kobylak [this message]
2019-11-21 10:29 ` Bright Cheng/WYHQ/Wiwynn
2019-11-22 1:36 ` Adriana Kobylak
2019-11-28 3:15 ` Bright Cheng/WYHQ/Wiwynn
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=0f356ff58ad9ec48b19e86f9da5eb7cc@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=Bright_Cheng@wiwynn.com \
--cc=DELPHINE_CHIU@wiwynn.com \
--cc=anoo@us.ibm.com \
--cc=gmills@linux.vnet.ibm.com \
--cc=mine260309@gmail.com \
--cc=neladk@microsoft.com \
--cc=ojayanth@in.ibm.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--cc=openbmc@lists.ozlabs.org \
--cc=ratagupt@linux.vnet.ibm.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.