From: Patrick Williams <patrick@stwcx.xyz>
To: Nikhil V <nikhil.vu@zohocorp.com>
Cc: openbmc <openbmc@lists.ozlabs.org>, akartashev <a.kartashev@yadro.com>
Subject: Re: [ERROR: Nothing RPROVIDES 'u-boot-default-env']
Date: Wed, 5 Jan 2022 11:01:42 -0600 [thread overview]
Message-ID: <YdXO9vLJP6pJRjGm@heinlein> (raw)
In-Reply-To: <17e29ef3ecb.f538ffea22697.1377643688691911450@zohocorp.com>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Wed, Jan 05, 2022 at 04:40:52PM +0530, Nikhil V wrote:
> Trying to implement openbmc on SAMA5D27 development board and to use secure boot feature provided by microchip. To make openbmc more secure.
I don't have much help on your specific problem, but I think there is some
surprise in your use of this chip for a few reasons.
- This isn't really a BMC-oriented chip and is likely missing hardware that
a BMC would typically have for interacting with the host processors.
- The A5 core in this chip is probably slower than the AST2500 (or maybe in
the same ballpark) which is already a generation behind.
- Aspeed has secure boot support also / already.
This isn't to say that you might not be able to get the SAMA5D27 working as a
BMC-like device for your system, but the fact that nobody else has decided to
build a server around it would give me a bit of concern if it showed up in a
system design I was working on.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-05 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 10:04 [ERROR: Nothing RPROVIDES 'u-boot-default-env'] Nikhil V
2022-01-03 11:10 ` Andrei Kartashev
2022-01-03 11:36 ` Nikhil V
2022-01-03 12:30 ` Andrei Kartashev
2022-01-03 13:15 ` Nikhil V
2022-01-05 11:10 ` Nikhil V
2022-01-05 17:01 ` Patrick Williams [this message]
2022-01-06 6:13 ` Nikhil V
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=YdXO9vLJP6pJRjGm@heinlein \
--to=patrick@stwcx.xyz \
--cc=a.kartashev@yadro.com \
--cc=nikhil.vu@zohocorp.com \
--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.