From: Chen Baozi <baozich@gmail.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: OMAP5 port.
Date: Thu, 28 Mar 2013 09:36:31 +0000 [thread overview]
Message-ID: <20130328093631.GA3702@localhost.localdomain> (raw)
In-Reply-To: <514C791A.70305@citrix.com>
On Fri, Mar 22, 2013 at 03:30:34PM +0000, Anthony PERARD wrote:
> On 22/03/13 15:17, Chen Baozi wrote:
> >
> > I've rebuilt Anthony's 3.4 Linux kernel and Xen for ARM on my Chromebook. (If
> > I'm right, the repo is git://xenbits.xen.org/people/aperard/linux-chromebook.git)
> > But I've no idea how to wrap the xen into u-boot format image properly. Is
> > there any brief introductions about it?
>
> Not yet, sorry for that.
>
> I will write some on the wiki soon, hopefully by Monday.
Hi Anthony,
Since Julien has updated the wiki about running Xen on Arndale board, I made
a little progress to boot Xen on Chromebook right now. (It seems that u-boot
has loaded Xen's image and switch the control to it.) However the problem
is still there that it is impossible to get the console output after. Is
there any good ways to catch the booting information to debug?
Thanks,
- Chen Baozi
> --
> Anthony PERARD
next prev parent reply other threads:[~2013-03-28 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 14:55 OMAP5 port Andrii Anisov
2013-03-13 15:01 ` Ian Campbell
2013-03-13 15:51 ` Andrii Anisov
2013-03-13 15:53 ` Ian Campbell
2013-03-13 16:50 ` Andrii Anisov
2013-03-13 16:56 ` Ian Campbell
2013-03-14 16:42 ` Stefano Stabellini
2013-03-14 17:45 ` Anthony PERARD
2013-03-22 13:56 ` Stefano Stabellini
2013-03-22 15:17 ` Chen Baozi
2013-03-22 15:30 ` Anthony PERARD
2013-03-28 9:36 ` Chen Baozi [this message]
2013-04-09 13:39 ` Andrii Anisov
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=20130328093631.GA3702@localhost.localdomain \
--to=baozich@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=anthony.perard@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 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).