From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [ARM ATTEND] DT maintainer
Date: Thu, 15 Aug 2013 17:06:29 +0100 [thread overview]
Message-ID: <20130815160628.GB32265@arm.com> (raw)
In-Reply-To: <CAL_JsqJpxeRbaZ4Uk4YNmN3w8D=XYf3VWX2c4NEqCy40zSdGSA@mail.gmail.com>
On Tue, Aug 13, 2013 at 02:11:06PM +0100, Rob Herring wrote:
> Other topics I'd like to discuss:
> What's left for ARM consolidation work? What further work needed to
> avoid arm64 duplication?
We'll have a better idea once we see more arm64 hardware. In the
meantime, what I know for sure is that we need a PCIe implementation
that is able to share drivers/host/* code between arm and arm64 (and
possibly other architectures). We had some attempts for more unification
between arm64, powerpc, microblaze, mips
(http://lkml.indiana.edu/hypermail/linux/kernel/1304.3/00698.html,
http://www.linux-mips.org/archives/linux-mips/2013-07/msg00031.html) and
work is ongoing.
> Now that we are moving from just compiling multiple platforms together
> to actually running them, what problems have been run into? Are there
> issues around multi-platform kernels such as kernel size or need for
> additional run-time patching?
If size becomes an issue, the next step for multi-platform could be
compiling as much SoC-related code as possible into loadable modules
that can go into initramfs.
--
Catalin
next prev parent reply other threads:[~2013-08-15 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:11 [ARM ATTEND] DT maintainer Rob Herring
2013-08-15 16:06 ` Catalin Marinas [this message]
2013-08-17 16:24 ` [Ksummit-2013-discuss] " Rob Herring
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=20130815160628.GB32265@arm.com \
--to=catalin.marinas@arm.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 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.