From: anshul makkar <anshulmakkar@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: s.kalaga@samsung.com, Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: Running android on Dom U. on ARM Cubieboard2.
Date: Wed, 20 Aug 2014 17:00:41 +0200 [thread overview]
Message-ID: <CACZDEvFXNCmhTvVpYQdLiiHfwBU2FBae6sxAP5RdFchCSCUgQw@mail.gmail.com> (raw)
In-Reply-To: <1408544170.3725.124.camel@Solace.lan>
Hi Dario,
Exactly, I am working on SAMSUNG-alike dual android system.
Yeah, thanks for sharing the information. I had not given thoughts
about these problems and was thinking of Android on Dom0 as well as
DomU.
It will be really helpful if Srinivas and Ian can throw some lights on
the questions raised..
Thanks
Anshul Makkar
www.justkernel.com
On Wed, Aug 20, 2014 at 4:16 PM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> On mer, 2014-08-20 at 10:52 +0200, anshul makkar wrote:
>> Android is basically a GUI/middle layer over and above Linux kernel
>> with some additional, android specific, kernel level patches.
>>
>> Most of the latest androids run on Linux kernel version 3.4 while Xen
>> support for ARM was made upstream from v 3.7.
>>
>> So to run Xen on Android, I will need to port android specific changes
>> to kernel v3.7 or later.
>>
> If your final goal is a SAMSUNG-alike dual android system, I think
> you'll run into userspace/toolstack issues also.
>
> In fact, as long as you have Linux as Dom0 and Android as a guest, then
> fine: you can build libxc, libxl and xl (or some other toolstack) for
> Linux and just use it from your Linux Dom0, as everyone using Xen does.
>
> But if Dom0 has to be Android, the toolstack needs to be built
> for/within Android's userspace, which I don't think is something that
> has been done before.
>
> Actually, this is something I always wanted to try, but never got the
> time to do so. Ian seems (from this message [1]) to at least have
> glanced at it also, but probably nothing more than that (Ian?).
>
> During the last Xen Hackathon, I chatted about this with Srinivas, but I
> never really followed up. So, Srinivas, here we are: do you have any
> help/instructions/pointers that you can share with us? :-)
>
> I know (because you told me yourself) that the toolstack you use in the
> dual-android tablet you demoed in Edinburgh and Brussels is *not* the
> upstream Xen one (i.e., it's not xl), but probably some indication on
> how you build your stuff can help us figure out how to build ours! :-D
>
> Thanks and Regards,
> Dario
>
> [1] http://lists.xen.org/archives/html/xen-devel/2014-04/msg00268.html
>
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>
next prev parent reply other threads:[~2014-08-20 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 10:54 Running android on Dom U. on ARM Cubieboard2 anshul makkar
2014-08-20 8:52 ` anshul makkar
2014-08-20 14:16 ` Dario Faggioli
2014-08-20 15:00 ` anshul makkar [this message]
2014-08-20 17:26 ` Ian Campbell
2014-08-21 17:19 ` Dario Faggioli
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=CACZDEvFXNCmhTvVpYQdLiiHfwBU2FBae6sxAP5RdFchCSCUgQw@mail.gmail.com \
--to=anshulmakkar@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=s.kalaga@samsung.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).