All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lei YU <mine260309@gmail.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc: Alexander Amelkin <a.amelkin@yadro.com>
Subject: Static layout PNOR support in openpower-pnor-code-mgmt
Date: Thu, 28 Feb 2019 15:15:17 +0800	[thread overview]
Message-ID: <CAARXrtmaOQJ9a224iosU1m+5FSryC4TM7qgBT3n9MYPWzZiQrQ@mail.gmail.com> (raw)

As a follow up of [VPNOR discussion][1], the static layout PNOR
support in openpower-pnor-code-mgmt is implemented and pushed to gerrit
starting from https://gerrit.openbmc-project.xyz/#/c/openbmc/openpower-pnor-code-mgmt/+/18747/

Code reviews and tests are welcome.

To test the feature:
1. Pick the above gerrit commits and build with --disable-ubifs_layout
2. Generate pnor in static.tar.gz format, by below command:
    ./generate-squashfs <xxx.pnor>   # xxx.pnor.static.tar.gz will be generated
   This tar.gz will be used to do the code update.
3. Do code update, gard reset, factory reset the same as VPNOR, described in
   [host-code-update.md][2] and [REST-cheatsheet.md][3]

I only tested it on Romulus, and will test it on Palmetto. Hopefully it will
be tested on other OpenPOWER machines before the patches are merged.

Note: image verification feature is not implemented yet.

[1]: https://lists.ozlabs.org/pipermail/openbmc/2019-February/015104.html
[2]: https://github.com/openbmc/docs/blob/master/code-update/host-code-update.md
[3]: https://github.com/openbmc/docs/blob/master/REST-cheatsheet.md

             reply	other threads:[~2019-02-28  7:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28  7:15 Lei YU [this message]
2019-02-28 23:14 ` Static layout PNOR support in openpower-pnor-code-mgmt Andrew Jeffery
2019-03-01  0:18 ` Stewart Smith
2019-03-01  1:19   ` Samuel Mendoza-Jonas
2019-03-01  1:48     ` Stewart Smith
2019-03-01  1:56       ` Lei YU
2019-03-01 12:44 ` Alexander A. Filippov

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=CAARXrtmaOQJ9a224iosU1m+5FSryC4TM7qgBT3n9MYPWzZiQrQ@mail.gmail.com \
    --to=mine260309@gmail.com \
    --cc=a.amelkin@yadro.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.