All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zev Weiss <zweiss@equinix.com>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Ryan Chen <ryan_chen@aspeedtech.com>,
	Andrew Jeffery <andrew@aj.id.au>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Zhang Jian <zhangjian.3032@bytedance.com>,
	Joel Stanley <joel@jms.id.au>,
	Dylan Hung <dylan_hung@aspeedtech.com>,
	Chia-Wei Wang <chiawei_wang@aspeedtech.com>
Subject: Re: [PATCH u-boot v2019.04-aspeed-openbmc] Revert "config/ast2500: Enable RAM devices"
Date: Wed, 9 Nov 2022 11:47:51 +0000	[thread overview]
Message-ID: <20221109114748.GE18848@packtop> (raw)
In-Reply-To: <20221026064021.16683-1-zev@bewilderbeest.net>

On Tue, Oct 25, 2022 at 11:40:21PM PDT, Zev Weiss wrote:
>This reverts commit ba91e9df1e16db0d209177148e864c65e58eb00f.
>
>CONFIG_RAM=y currently breaks DRAM initialization on ast2500; Aspeed
>recommends against using it [0].
>
>[0] https://lore.kernel.org/openbmc/HK0PR06MB2834AE1581020A5B7CE191839C5B9@HK0PR06MB2834.apcprd06.prod.outlook.com/
>
>Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
>---
>
>Note that I'm not at all tied to this particular patch as the fix if
>the interested parties can agree on better course of action; I'm
>mostly just hoping to spur some further conversation given that
>currently a vanilla OpenBMC build bricks my ast2500 systems in a way
>that's not real easy to recover without a flash programmer.
>

Ping...I'm hoping to get e3c246d4i migrated to u-boot-aspeed-sdk soon
(bearing in mind the end-of-year deadline suggested in Joel's email a
few months ago [0]), but with this issue outstanding doing so will make
any such systems self-bricking unless I hack around it with a bandaid
kconfig fragment in a bbappend, which doesn't seem like a great fix
since it's not really an e3c246d4i-specific problem.


Thanks,
Zev

[0] https://lore.kernel.org/openbmc/CACPK8Xe4ijKWnURT4T9em2pUqifNdkZUfg0dd5osATYnqqutSw@mail.gmail.com/

  reply	other threads:[~2022-11-09 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  6:40 [PATCH u-boot v2019.04-aspeed-openbmc] Revert "config/ast2500: Enable RAM devices" Zev Weiss
2022-11-09 11:47 ` Zev Weiss [this message]
2022-11-10  0:13   ` Joel Stanley

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=20221109114748.GE18848@packtop \
    --to=zweiss@equinix.com \
    --cc=andrew@aj.id.au \
    --cc=chiawei_wang@aspeedtech.com \
    --cc=dylan_hung@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ryan_chen@aspeedtech.com \
    --cc=zev@bewilderbeest.net \
    --cc=zhangjian.3032@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.