From: Adriana Kobylak <anoo@linux.ibm.com>
To: Andrew Geissler <geissonator@gmail.com>
Cc: Lei YU <mine260309@gmail.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>
Subject: Re: Romulus to use Virtual PNOR
Date: Thu, 14 Feb 2019 15:31:11 -0600 [thread overview]
Message-ID: <c8633af8ba717f0812cf55b8eb458084@linux.vnet.ibm.com> (raw)
In-Reply-To: <CALLMt=q_Pb=TpzR353dTMyP=cpkf9FPJCFiSxu+Q3_ntK5no2Q@mail.gmail.com>
On 2019-02-14 07:13, Andrew Geissler wrote:
> On Wed, Feb 13, 2019 at 9:03 PM Lei YU <mine260309@gmail.com> wrote:
>>
>> Based on the discussion, let's keep using static flash layout for PNOR
>> on
>> Romulus.
>>
>> This brings the questions:
>> 1. Shall we move the legacy code update service
>> (org.openbmc.control.Flash.service) to the new one
>> (xyz.openbmc_project.Software.xxx.service)?
>
> Yes please. I asked Adriana to open a story to track doing this.
https://github.com/ibm-openbmc/dev/issues/417
The first step would be to support just updating the pnor using the
libflash library that the legacy code uses. We can look into the
other features like signature validation afterwards.
prev parent reply other threads:[~2019-02-14 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 7:40 Romulus to use Virtual PNOR Lei YU
2019-01-29 15:01 ` Alexander Amelkin
2019-02-06 0:39 ` Stewart Smith
2019-02-06 15:01 ` Alexander Amelkin
2019-02-11 5:07 ` Andrew Jeffery
2019-02-06 0:38 ` Stewart Smith
2019-02-12 3:57 ` Joel Stanley
2019-02-14 3:03 ` Lei YU
2019-02-14 11:03 ` Alexander Amelkin
2019-02-15 6:48 ` Lei YU
2019-02-15 15:36 ` Alexander Amelkin
2019-02-14 13:13 ` Andrew Geissler
2019-02-14 21:31 ` Adriana Kobylak [this message]
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=c8633af8ba717f0812cf55b8eb458084@linux.vnet.ibm.com \
--to=anoo@linux.ibm.com \
--cc=geissonator@gmail.com \
--cc=mine260309@gmail.com \
--cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
--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.