From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] Following discussions, ARM64 SoC support, DT backward compat
Date: Wed, 26 Mar 2014 19:46:54 +0100 [thread overview]
Message-ID: <20140326194654.72beb639@skate> (raw)
Hello,
I'm a regular contributor to the Marvell EBU platform, mainly regarding
the support of the most recent processors Armada 370, Armada XP, Armada
375 and Armada 38x.
For this reason, I'm interested in following discussions with the other
ARM kernel maintainers and contributors, simply to ensure I remain
up-to-date with the latest directions in the ARM kernel world.
Also, I'm interested specifically in:
* Hearing a bit about ARM64, and how the SoC support is going to work.
For example how code is shared between ARM and ARM64 when you have
two SoCs that are similar, but one has a 32 bits ARM core and the
other a 64 bits ARM core. And generally the status of ARM64 support.
* Discussing practical examples of Device Tree backward compatibility,
and how to handle them. Discuss whether improvements to the FDT API
are not needed to help in coping with those backward compatibility
problems.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
reply other threads:[~2014-03-26 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140326194654.72beb639@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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