From: Patrick Williams <patrick@stwcx.xyz>
To: Lei Yu <yulei.sh@bytedance.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Unify the 64MiB flash layout
Date: Thu, 27 May 2021 07:33:28 -0500 [thread overview]
Message-ID: <YK+RmDRspsfjeTp2@heinlein> (raw)
In-Reply-To: <CAGm54UGMSVkT=3WLVLrJwcW8OGcQJZOGYnhVvOrF1qVC7xtdvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Thu, May 27, 2021 at 03:13:44PM +0800, Lei Yu wrote:
> With the above changes, g220a system works fine with the new u-boot
> and the updated flash layout.
Does it work for the flash0 u-boot to be able to boot flash1's system?
Maybe this doesn't affect g220a but in general we've found issues with
changing these kind of layouts and not updating both flash banks. Due
to our secureboot implementation, we're not able to update the primary
flash bank (since it is write-protected).
This change doesn't currently affect us right now, but if we're making
a breaking change anyhow should we increase the u-boot partition
sufficiently that it won't become an issue later on as ast2600 systems
go into production? We've found that over time the size tends to get
bigger with newer (more optimizing?) compilers, so I think we should
ensure there is some buffer there.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-05-27 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 7:13 Unify the 64MiB flash layout Lei Yu
2021-05-27 12:33 ` Patrick Williams [this message]
2021-06-03 5:59 ` Joel Stanley
2021-06-09 5:30 ` Troy Lee
2021-06-09 6:43 ` Lei Yu
2021-06-09 8:32 ` Troy Lee
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=YK+RmDRspsfjeTp2@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.org \
--cc=yulei.sh@bytedance.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.