From: Lei YU <mine260309@gmail.com>
To: Stewart Smith <stewart@linux.ibm.com>
Cc: Samuel Mendoza-Jonas <sam@mendozajonas.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Alexander Amelkin <a.amelkin@yadro.com>
Subject: Re: Static layout PNOR support in openpower-pnor-code-mgmt
Date: Fri, 1 Mar 2019 09:56:28 +0800 [thread overview]
Message-ID: <CAARXrtmX6np4jaeDnv_EAMfrLCKi+xGOX6rmy17ov2kLrP+qrg@mail.gmail.com> (raw)
In-Reply-To: <87pnrbqs8r.fsf@linux.vnet.ibm.com>
> >> Is this a new format? Why? Where is it documented?
> >>
> >
> > Looking on gerrit this just appears to be the PNOR and a MANIFEST file in
> > a tarball. Considering it's just a call to 'tar', having it be generated
> > by something called 'generate-squashfs' is confusing. I guess this is
> > because generate-squashfs creates the MANIFEST file?
>
> Yeah, that sounds odd. The current format is just the pnor file.
Yeah, it is a bit odd, I just want to re-use the code in 'generate-squashfs'
to generate a tar that contains MANIFEST and the pnor.
Possibly it could be renamed to `generate-tar`or similar.
Be noted that this file is used to generate Witherspoon's PNOR tarball in
op-build. So renaming it should cause op-build to pick the new name.
next prev parent reply other threads:[~2019-03-01 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 7:15 Static layout PNOR support in openpower-pnor-code-mgmt Lei YU
2019-02-28 23:14 ` 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 [this message]
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=CAARXrtmX6np4jaeDnv_EAMfrLCKi+xGOX6rmy17ov2kLrP+qrg@mail.gmail.com \
--to=mine260309@gmail.com \
--cc=a.amelkin@yadro.com \
--cc=openbmc@lists.ozlabs.org \
--cc=sam@mendozajonas.com \
--cc=stewart@linux.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.