From: Ian Campbell <ian.campbell@citrix.com>
To: "Korupol, Naveen (EXT)" <Naveen.Korupol@ext.us.panasonic.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Failed to launch xen on J6 evm
Date: Mon, 9 Mar 2015 09:54:54 +0000 [thread overview]
Message-ID: <1425894894.14353.68.camel@citrix.com> (raw)
In-Reply-To: <BY2PR02MB1401BEB356B5A985676010EDE1C0@BY2PR02MB140.namprd02.prod.outlook.com>
On Fri, 2015-03-06 at 20:03 +0000, Korupol, Naveen (EXT) wrote:
> I am using J6 evm.
What is one of them?
> played with couple different u-boots
Does your u-boot launch the kernel (AKA Xen in this case) in NS.HYP
mode?
> If there are any probable fixes/hints for bringing up XEN on J6 evm.
Given where things are apparently hanging I think the first step would
be to enable early printk for your platform.
See docs/misc/arm/early-printk.txt and the long ifeq chain in
xen/arch/arm/Rules.mk.
If the UART on your platform is one of the existing ones in
xen/arch/arm/arm*/debug*.inc then this is pretty easy.
If not then you just need to provide two ASM macros early_uart_ready and
early_uart_transmit which is pretty trivial for every UART I've ever
seen -- see the existing debug*.inc for examples.
Ian.
next prev parent reply other threads:[~2015-03-09 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 20:03 Failed to launch xen on J6 evm Korupol, Naveen (EXT)
2015-03-09 9:54 ` Ian Campbell [this message]
2015-03-09 16:51 ` Korupol, Naveen (EXT)
2015-03-09 17:07 ` Ian Campbell
2015-03-10 8:24 ` M A Young
2015-03-10 20:42 ` Korupol, Naveen (EXT)
2015-03-10 20:52 ` Korupol, Naveen (EXT)
2015-03-11 9:40 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2015-03-11 19:38 Korupol, Naveen (EXT)
2015-03-11 19:46 ` M A Young
2015-03-12 9:38 ` Ian Campbell
2015-03-12 14:01 ` Korupol, Naveen (EXT)
2015-04-15 22:21 ` Korupol, Naveen (EXT)
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=1425894894.14353.68.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Naveen.Korupol@ext.us.panasonic.com \
--cc=xen-devel@lists.xenproject.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.