From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: Development tree for Cortex-A15?
Date: Tue, 08 May 2012 11:52:15 +0100 [thread overview]
Message-ID: <4FA8FADF.2070701@arm.com> (raw)
In-Reply-To: <1336472016.29885.YahooMailNeo@web132503.mail.ird.yahoo.com>
On 08/05/12 11:13, Jemma Jones wrote:
>> Subject: Re: Development tree for Cortex-A15?
>>> 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 didn't seem to get anything?
As far as I'm concerned, it was delivered:
2012-05-05 13:09:33 1SQcrl-0006uI-OX <= maz at misterjones.org U=www-data P=local S=59827 id=7da4dd4bd4f768d907094ce4919bfffe@localhost
2012-05-05 13:09:34 1SQcrl-0006uI-OX => jemmajones81 at yahoo.co.uk R=dnslookup T=remote_smtp H=mx-eu.mail.am0.yahoodns.net [77.238.184.241]
2012-05-05 13:09:34 1SQcrl-0006uI-OX Completed
I'll resend it again, but you may want to check your spam folder.
>>> 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?
>
> I don't quite understand yet how the DT stuff is used. When I build the DTB files then I get vexpress-v2p-ca15-tc1.dtb in my arch/arm/boot directory. I assume that one is used then for my kernel image?
>
> My .config has all the DT stuff enabled I think:
> CONFIG_ARCH_VEXPRESS_DT=y
> CONFIG_ARM_APPENDED_DTB=y
> CONFIG_ARM_ATAG_DTB_COMPAT=y
>
> Or is that not correct?
First, you want to forget about anything TC1 related, it isn't what you need for the Fast Model.
Step by step instructions:
- Grab Pawe?'s DTS tree: git://linux-arm.org/arm-dts.git
- Build your zImage
- From your kernel tree, run:
./script/dtc/dtc -O dtb -o rtsm_ve-cortex_a15x2.dtb wherever_your_arm-dts_tree_is/fast_models/rtsm_ve-cortex_a15x2.dts
- cat rtsm_ve-cortex_a15x2.dtb >>arch/arm/boot/zImage
- Build your uImage if that's what you're using.
- Build your boot-wrapper as usual.
That should get you going.
> I have now updated to you latest kvm-arm-3.4 branch.
That's very brave of you... ;-)
> But the kernel still does not boot up properly, or at least I don't seem to get any output. It just goes "Uncompressing Linux... done." and then does nothing.
> I'm using the FastModel Cortex-A15x2 simulation.
Let me know if it gets better with the above. Or not.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2012-05-08 10:52 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
2012-05-08 10:13 ` Jemma Jones
2012-05-08 10:52 ` Marc Zyngier [this message]
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=4FA8FADF.2070701@arm.com \
--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).