All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Lee <troy_lee@aspeedtech.com>
To: Joel Stanley <joel@jms.id.au>
Cc: "Klaus Heinrich Kiwi" <klaus@linux.vnet.ibm.com>,
	"Andrew Jeffery" <andrew@aj.id.au>,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
	"Ryan Chen" <ryan_chen@aspeedtech.com>,
	"Cédric Le Goater" <clg@kaod.org>
Subject: Re: u-boot update for ast2600
Date: Thu, 22 Apr 2021 01:26:28 +0000	[thread overview]
Message-ID: <20210422012628.GA1315@aspeedtech.com> (raw)
In-Reply-To: <CACPK8XcXTq1tzQ=aLa8pEKyt3WBWWfj18vhh9ks1DxDn+T+i7g@mail.gmail.com>

Hi Joel,

The 04/22/2021 07:50, Joel Stanley wrote:
> Hello OpenBMCers who care about u-boot,
> 
> I've updated OpenBMC u-boot tree to use ASPEED's latest SDK,
> v00.03.03. I've also applied the series to support for FIT
> verification including use of the HACE to perform SHA hashing that
> I've been working on with Klaus. The bump is here:
> 
>  https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/42502
> 
> I've sent a set of fixes backported from mainline to ASPEED for
> merging in a future SDK release:
> 
>  https://github.com/AspeedTech-BMC/u-boot/pull/7
> 
> We still have a number of patches carried that are specific to
> OpenBMC, and of course the new FIT and HACE support.
> 
> My focus is on supporting u-boot on ast2600 with eMMC. I test this
> mostly in Qemu with Cédric's aspeed-6.0 branch:
> 
> https://github.com/shenki/qemu-boot-test/
> 
> I do  run u-boot from NOR on the ast2600a2 evb I have, but I would
> encourage testing from others if they care about this platform setup
> as it gets much less attention from me.
> 
> Cheers,
> 
> Joel

I have a ast2600a2 evb configured with boot from eMMC, so I could help to
verify it.  Could you provid me the image or the instructions to build
it?

Thanks,
Troy Lee

      reply	other threads:[~2021-04-22  1:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 23:50 u-boot update for ast2600 Joel Stanley
2021-04-22  1:26 ` Troy Lee [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=20210422012628.GA1315@aspeedtech.com \
    --to=troy_lee@aspeedtech.com \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=joel@jms.id.au \
    --cc=klaus@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ryan_chen@aspeedtech.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.