linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: Development tree for Cortex-A15?
Date: Thu, 03 May 2012 16:56:35 +0200	[thread overview]
Message-ID: <6e4ad6defa33bf693ec45cae819469f0@localhost> (raw)
In-Reply-To: <1336052155.37772.YahooMailNeo@web132504.mail.ird.yahoo.com>

On Thu, 3 May 2012 14:35:55 +0100 (BST), Jemma Jones
<jemmajones81@yahoo.co.uk> wrote:
>> Subject: Re: Development tree for Cortex-A15?
> 
>> 
>> On Thu, 3 May 2012 12:56:39 +0100 (BST), Jemma Jones
>> <jemmajones81@yahoo.co.uk> wrote:
>> 
>> Hi Jemma,
>> 
>>>  Hi, I'm looking for the latest KVM-enabled developer version of the
>> Linux
>>>  kernel for ARM on the Versatile Express board with the Cortex-A15
>>>  CPU.?
>> 
>> It really depends on what you call "developer version". As far as I 
>> know,
>> there is nothing but dev trees around ;-).
>> 
>>>  I have pulled from these two trees
>>> 
>>> 
>>
http://git.kernel.org/?p=linux/kernel/git/cmarinas/linux-arm-arch.git;a=summary
>>> 
>>
http://git.kernel.org/?p=linux/kernel/git/maz/arm-platforms.git;a=summary
>>> 
>>>  But it seems the 2nd one is more up-to-date with KVM enablement while
>>>  it
>>>  doesn't have any support for the A15 VE board? And the 1st one 
>> doesn't
>>>  support KVM on ARM with the ARMv7 virtualization extensions?
>> 
>> First, my tree (the second one) does support the A15. Otherwise I'd
have
>> a
>> hard time testing my own code... Which branch are you looking at?
Please
>> note that the KVM branches in this tree are under heavy development,
and
>> are only suitable if you don't mind frequent rebases and regular
breakage
>> due to bleeding edge code.
> 
> I'm currently on kvm-arm-v7-ael, because it looked like the most
> up-to-date one. Which one should I be using for Cortex-A15 support?

That branch is good enough, if you have a bleeding edge QEMU. Note that
the VE A15 support in that tree is DT only. I'm working on a v3.4 based one
at the moment, but that's not completely ready yet.

        M.
-- 
Fast, cheap, reliable. Pick two.

  reply	other threads:[~2012-05-03 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 11:56 Development tree for Cortex-A15? Jemma Jones
2012-05-03 13:24 ` Marc Zyngier
2012-05-03 13:35   ` Jemma Jones
2012-05-03 14:56     ` Marc Zyngier [this message]
2012-05-04  8:44       ` Jemma Jones
2012-05-04 10:54         ` Marc Zyngier
2012-05-04 12:20           ` Jemma Jones
2012-05-05 11:04             ` Marc Zyngier
2012-05-08 10:13               ` Jemma Jones
2012-05-08 10:52                 ` Marc Zyngier
2012-05-08 11:47                   ` Jemma Jones
2012-05-08 13:54                   ` Jemma Jones
2012-05-08 13:59                     ` Marc Zyngier
2012-05-04 14:30           ` Jemma Jones
2012-05-05 11:08             ` Marc Zyngier

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=6e4ad6defa33bf693ec45cae819469f0@localhost \
    --to=marc.zyngier@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 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).