From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Sagun Garg <sagun@nexchanges.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Install Xen on ARM in a bare metal fashion on a Nexus Phone/Tablet or an ARM emulator
Date: Fri, 05 Dec 2014 11:16:45 +0000 [thread overview]
Message-ID: <5481941D.6050106@linaro.org> (raw)
In-Reply-To: <1417771940.22808.39.camel@citrix.com>
Hello,
On 05/12/2014 09:32, Ian Campbell wrote:
> On Fri, 2014-12-05 at 14:51 +0530, Sagun Garg wrote:
> Not sure what sorts of risks you mean, I don't think there is anything
> Xen specific here, just the usual stuff with running an untested OS on
> any new platform.
>
> I don't know if Nexus devices are brickable, but if so then that might
> be an issue with trying any untested OS on them.
Nexus platform tend to be a good platform for development. I would be
surprised if you can brick it with untested OS. Though, I would not try
to change the bootloader and I don't know if they support HYP mode.
>
> Phones and the like aren't typically very good debug platforms (i.e. no
> serial, no JTAG etc) so running an untested OS on them can end up being
> hard (but not impossible) to debug if it doesn't work, that's why
> platforms such as the Arndale exist -- they are mobile phones with all
> the extra useful debug stuff brought out to headers.
Nexus smartphone (at least 4) has an UART hidden in the headphone jack.
I don't know it's possible to buy the specific cable but you would be
able to build your own. Though, I haven't tried myself.
The Linux kernel provided on AOSP has the code to enable the UART. So
you should be able to get the log.
For Xen, you will have to implement yourself the debug UART.
--
Julien Grall
next prev parent reply other threads:[~2014-12-05 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 10:14 Install Xen on ARM in a bare metal fashion on a Nexus Phone/Tablet or an ARM emulator Sagun Garg
2014-12-04 10:29 ` Ian Campbell
2014-12-05 9:21 ` Sagun Garg
2014-12-05 9:32 ` Ian Campbell
2014-12-05 11:16 ` Julien Grall [this message]
2014-12-06 8:58 ` Sagun Garg
2014-12-08 12:43 ` Ian Campbell
[not found] ` <CALwCXQBxLZnX1JX10JDEtA7whUZohFSb2jutNghU33SEwZ3gJQ@mail.gmail.com>
2014-12-08 12:47 ` 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=5481941D.6050106@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=sagun@nexchanges.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.