From: Patrick Williams <patrick@stwcx.xyz>
To: tandehui <dehuitan1988@hotmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: ARM aarch64 confuse
Date: Tue, 9 Nov 2021 11:47:46 -0600 [thread overview]
Message-ID: <YYq0QvdarGn3TG5/@heinlein> (raw)
In-Reply-To: <ME3PR01MB808110CCBC2434149E0265F8C9929@ME3PR01MB8081.ausprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Tue, Nov 09, 2021 at 03:53:20PM +0800, tandehui wrote:
> So does OpenBMC support 64-bit processors? If yes, what special
> attention should be paid to it?
I believe the latest Nuvoton chips are already aarch64. In theory, our code
should be fairly 32/64-bit agnostic. There have been a few bugs where the code
made 32-bit assumptions, especially around serializing data to/from files.
There could certainly be more.
> I am running openbmc on a ARM aarch64 cpu. I'm experiencing
> some webui-related issues that seem to be related to 64-bit processors.
The webui executes on browser (it is all javascript) and shouldn't care what
kind of processor is exposing the REST/Redfish APIs. Can you elaborate on what
kind of problems you are seeing? It is certainly possible that there are bugs
in the Redfish APIs themselves (see above), but it is hard to know without some
more details on what you mean by "some webui-related issues"...
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-11-09 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 7:53 ARM aarch64 confuse tandehui
2021-11-09 17:47 ` Patrick Williams [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=YYq0QvdarGn3TG5/@heinlein \
--to=patrick@stwcx.xyz \
--cc=dehuitan1988@hotmail.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 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).