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: Sat, 05 May 2012 13:04:33 +0200	[thread overview]
Message-ID: <4f7e5540dd597d8e48fb81a5e1e26313@localhost> (raw)
In-Reply-To: <1336134008.88695.YahooMailNeo@web132504.mail.ird.yahoo.com>

On Fri, 4 May 2012 13:20:08 +0100 (BST), Jemma Jones
<jemmajones81@yahoo.co.uk> wrote:
>> Subject: Re: Development tree for Cortex-A15?
>> 
>> On Fri, 4 May 2012 09:44:07 +0100 (BST), Jemma Jones
>> <jemmajones81@yahoo.co.uk> wrote:
>>>>  Subject: Re: Development tree for Cortex-A15?
>>> 
>>>> 
>>>>  On Thu, 3 May 2012 14:35:55 +0100 (BST), Jemma Jones
>>>>  <jemmajones81@yahoo.co.uk> wrote:
>>>>>> ? Subject: Re: Development tree for Cortex-A15?
>>>>> 
>>>>> ? 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.
>>> 
>>>  I'm just a little confused because under arch/arm/mach-vexpress/
there
>> is
>>>  no A15 tile? On the virtualopensystems.com git (which you quote
above)
>> you
>>>  had to explicitly enable the board and it would show up in the
.config
>> as
>>>  CONFIG_ARCH_VEXPRESS_CA15X4. Is that not the case anymore in your
>>>  kernel
>>>  tree?
>> 
>> No. The ARM tree in general is moving to the device tree, and
>> CONFIG_ARCH_VEXPRESS_CA15X4 was always meant as a temporary hack until
>> the
>> VE-DT port was mature enough to be used.
>> 
>> As Pawe?'s DT work has been merged into 3.4, there is strictly no
reason
>> to keep this hack around, and my recent trees do reflect that fact
>> (kvm-arm-v7-ael and kvm-arm-3.4). Christoffer may decide to keep this
in
>> his tree during a transition period, but CONFIG_ARCH_VEXPRESS_CA15X4 is
>> dead as far as I am concerned.
>> 
>> If you're just starting to play with KVM-ARM now, please don't rely on 
>> the
>> A15 board file, it is a dead end.
> 
> Any chance you can send me a .config file that works on the kernel in
this
> branch which runs on your A15x1 FastModel?

Coming in a private email.

> I'm using the boot-wrapper from
> http://git.linaro.org/gitweb?p=arm/models/boot-wrapper.git;a=summary in
> semi hosting mode.
> 
> I managed to boot Android from that but I don't seem to be able to boot
> your kernel. It just stops after the boot-wrapper says loading uImage.

Which dts file are you using?

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

  reply	other threads:[~2012-05-05 11:04 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
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 [this message]
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=4f7e5540dd597d8e48fb81a5e1e26313@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).