From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] VEXPRESS64 ARMv8 U-Boot maintenance
Date: Fri, 12 Dec 2014 09:48:27 -0800 [thread overview]
Message-ID: <548B2A6B.7030704@broadcom.com> (raw)
In-Reply-To: <CACRpkdYMyw9wpF6jNaQCGBivyueRzZ_tFVYjBQiun5iGVMQauQ@mail.gmail.com>
On 14-12-11 01:48 AM, Linus Walleij wrote:
> Hi folks
> (David & Steve listed as AArch64/v8 maintainers),
>
> are you actively maintaining and reviewing ARM64 board
> patches?
Sadly, no.
If you would take over being maintainer for the "vexpress_aemv8a_semi"
board, that would be appreciated.
Thanks, Steve
>
> I am working on support for the ARM Juno Development
> Platform real hardware, which is now up and running on my
> desk. I will add this board with myself as maintainer.
>
> But who takes care of the code in arch/arm/cpu/armv8?
>
> I have some questions about the rendez-vous code in the
> armv8 start.S file, as if two CPUs (master & slave) would come
> running into U-Boot, which is not what ARM Trusted Firmware
> does, it arrives only on the master CPU. Can any of you explain
> why that code is there?
>
> Else I will start looking at it and add myself as maintainer for
> this.
>
> Please also have a look at my patches to the Semihosting code:
> http://patchwork.ozlabs.org/patch/412628/
> http://patchwork.ozlabs.org/patch/412629/
> http://patchwork.ozlabs.org/patch/412630/
I will look at these -- Thanks, Steve
>
> Yours,
> Linus Walleij
>
prev parent reply other threads:[~2014-12-12 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 9:48 [U-Boot] VEXPRESS64 ARMv8 U-Boot maintenance Linus Walleij
2014-12-12 16:31 ` Tom Rini
2014-12-12 17:48 ` Steve Rae [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=548B2A6B.7030704@broadcom.com \
--to=srae@broadcom.com \
--cc=u-boot@lists.denx.de \
/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