From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] VEXPRESS64 ARMv8 U-Boot maintenance
Date: Fri, 12 Dec 2014 11:31:03 -0500 [thread overview]
Message-ID: <20141212163103.GY20704@bill-the-cat> (raw)
In-Reply-To: <CACRpkdYMyw9wpF6jNaQCGBivyueRzZ_tFVYjBQiun5iGVMQauQ@mail.gmail.com>
On Thu, Dec 11, 2014 at 10:48:43AM +0100, Linus Walleij wrote:
> Hi folks
> (David & Steve listed as AArch64/v8 maintainers),
>
> are you actively maintaining and reviewing ARM64 board
> patches?
>
> 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.
Oh good. I was hoping someone would get a chance to do this. I had a
few more ideas about what might have been needed but haven't been able
to cycle back around to hooking mine up and playing again.
> But who takes care of the code in arch/arm/cpu/armv8?
Currently it falls under Albert's care as the overall core ARM
maintainer.
> 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 think the overall answer here is that as the code base and
implementation evolves everywhere, we'll need some adjustments to match
up. Please make sure to keep York Sun in the loop too as Freescale is
active in this area as well (and the other Freescale folks too as they
transition from multi-core PowerPC to multi-core ARMv8 :)). Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141212/2fff8a6c/attachment.pgp>
next prev parent reply other threads:[~2014-12-12 16:31 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 [this message]
2014-12-12 17:48 ` Steve Rae
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=20141212163103.GY20704@bill-the-cat \
--to=trini@ti.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