From: Birin Sanchez <birintxo@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Help on getting serial output on the arndale board
Date: Tue, 18 Jun 2013 13:58:00 +0200 [thread overview]
Message-ID: <51C04B48.70206@gmail.com> (raw)
In-Reply-To: <1371551656.9810.34.camel@zakaz.uk.xensource.com>
> Do you have a dtuart=<something> in your Xen bootargs (in the dtb)?
>
> This is mentioned in
> http://wiki.xen.org/wiki/Xen_ARMv7_with_Virtualization_Extensions
> but not
> http://wiki.xen.org/wiki/Xen_ARMv7_with_Virtualization_Extensions/Arndale
>
> If you are using the dts from Julien's Linux tree it should have this
> already, so maybe this is a red herring but I'd have expected the logs
> to contain
> "Looking for UART console %s\n", devalias);
> from dt_uart_init() and they don't.
Yes. arch/arm/boot/dts/exynos5250-arndale.dts contains this:
chosen {
bootargs = "dom0_mem=256M sync_console console=dtuart
dtuart=serial0";
xen,dom0-bootargs = "console=hvc0,115200n8 debug
root=/dev/mmcblk1p2 ignore_loglevel rw rootwait earlyprintk=xen";
modules {
module@0 {
compatible = "xen,linux-zimage",
"xen,multiboot-module";
reg = <0x60000000 0x400000>;
};
};
};
and serial0 is an alias:
serial0 = "/serial@12C20000";
I guess that's OK.
>
> I find that the build system is not great at picking up changes to the
> DTB, I habitually rm xen/arch/arm/dtb.o before rebuilding Xen.
I did 'make distclean' every time before compiling again. Checking the
date on dtb.o shows same date as the generated xen-uImage.
I will compile against every change in
arch/arm/boot/dts/exynos5250-arndale.dts to see if I can find what made
it stop working.
Also I recently upgraded to Ubuntu 13.04 could this be the issue?
Birin
> Ian.
>
next prev parent reply other threads:[~2013-06-18 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 3:39 Help on getting serial output on the arndale board Birin Sanchez
2013-06-18 10:34 ` Ian Campbell
2013-06-18 11:58 ` Birin Sanchez [this message]
[not found] ` <51C04A48.9080401@gmail.com>
2013-06-18 11:58 ` Ian Campbell
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=51C04B48.70206@gmail.com \
--to=birintxo@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=xen-devel@lists.xen.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.