openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Thang Nguyen <thang@amperemail.onmicrosoft.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Fix u-boot 2016.07 env fail on 64MB layout
Date: Mon, 1 Nov 2021 06:39:48 +0000	[thread overview]
Message-ID: <CACPK8XfZBy5cW7QD4OvCMeRB01hzQshGCRP=6A=+U+3y=4nisA@mail.gmail.com> (raw)
In-Reply-To: <dcebf35e-56a3-4f16-0380-841925e093f4@amperemail.onmicrosoft.com>

On Fri, 29 Oct 2021 at 11:16, Thang Nguyen
<thang@amperemail.onmicrosoft.com> wrote:
>
> Hi,
> My platform uses Aspeed2500 BMC with 64MB SPI-NOR. Since the change in
> BMC SPI-NOR layout at
> https://github.com/openbmc/linux/commit/985c3f59cc645c397726ad4ca0872cfaf7ef2579,
> the patch
> meta-phosphor/aspeed-layer/recipes-bsp/u-boot/files/0001-configs-ast-Add-redundnant-env.patch
> becomes incorrect for 64MB layout (but still correct for 32MB SPI-NOR
> layout).
> Do you have any idea on correcting it for 64MB layout?

I suggest deleting the patch. It should not live in meta-phosphor. If
this feature is required, it should be controlled with a configuration
in u-boot defconfig.

I also suggest using the newer u-boot version (2019.04) for your platform.

Cheers,

Joel

>
> Thanks,
> Thang Q. Nguyen

      parent reply	other threads:[~2021-11-01  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 11:15 Fix u-boot 2016.07 env fail on 64MB layout Thang Nguyen
2021-10-29 12:39 ` [External] " Lei Yu
2021-10-30  7:22   ` Thang Nguyen
2021-11-01  6:39 ` Joel Stanley [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='CACPK8XfZBy5cW7QD4OvCMeRB01hzQshGCRP=6A=+U+3y=4nisA@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=thang@amperemail.onmicrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).