From: "Mark A. Miller" <mark@mirell.org>
To: linux-kernel@vger.kernel.org
Cc: qemu-devel@nongnu.org,
Embedded Linux mailing list <linux-embedded@vger.kernel.org>
Subject: [Qemu-devel] Versatile PB Board Support for ARMv6 and ARMv7
Date: Tue, 7 Apr 2009 22:35:25 -0500 [thread overview]
Message-ID: <31014a580904072035u7215ab93m41d2205d42c22be@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
In late October 2008, according to the git logs, the methodology for
selecting a processor on several boards, at least the Versatile PB board was
changed so that it automatically selects CPU_ARM926T as a hidden symbol.
The reason I have a question, is since QEMU currently can emulate a
Versatile PB board with other processors than just the ARM926T (Such as the
ARM1136 (ARMv6) and Cortex-A8 (ARMv7), is there a good way to allow that in
the mainstream kernel? Previously the patch was to just add extra potential
dependencies on CPU_V6 and CPU_V7, so that by selecting MACH_VERSATILE_PB,
you could select ARMv6/v7 support.
Currently I'm just deleting the select statement, and having all the CPUs
appear, as no longer hidden symbols. My question is, what is the best way to
allow for other processors for this board in Kconfig, so it could be
submitted to the mainstream kernel?
--
Mark A. Miller
mark@mirell.org
"My greatest strength, I guess it would be my humility. My greatest
weakness, it's possible that I'm a little too awesome" - Barack Obama
[-- Attachment #2: Type: text/html, Size: 1226 bytes --]
next reply other threads:[~2009-04-08 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 3:35 Mark A. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 3:37 [Qemu-devel] Versatile PB Board Support for ARMv6 and ARMv7 Mark Miller
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=31014a580904072035u7215ab93m41d2205d42c22be@mail.gmail.com \
--to=mark@mirell.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.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).