All of lore.kernel.org
 help / color / mirror / Atom feed
From: anshul makkar <anshulmakkar@gmail.com>
To: xen-devel@lists.xen.org
Subject: Re: Running android on Dom U. on ARM Cubieboard2.
Date: Wed, 20 Aug 2014 10:52:42 +0200	[thread overview]
Message-ID: <CACZDEvF_22JYoYVOg=AQepKUXaXMHztJV-0rWVyT=hoZRwU1hA@mail.gmail.com> (raw)
In-Reply-To: <CACZDEvGgDVroXkE8heAyxMN-VWwCaHTit3Jq0SBq+Dn5UQOBRA@mail.gmail.com>

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.

Got the clarity after reading further. Sorry for making noise with my
query which could have been answered with further more exploration.

On Mon, Aug 18, 2014 at 12:54 PM, anshul makkar <anshulmakkar@gmail.com> wrote:
> Hi,
>
> I have been able to setup Linux running on Dom 0 and DomU on my ARM
> Cubieboard 2.
>
> Now, as I mentioned earlier, my aim is to run 2 simultaneous images of
> Android : 1 in Dom 0  and other in Dom U.
>
> When I google ,what I see is the only presentation from Samsung
> showing two Android's running simultaneously. But no other open source
> contribution which can help me to proceed further. for eg.
> contributions to paravitualized drivers which will help to run Android
> on Dom U.
>
> On CubieBoard2 I have a stock Android which I am able to run in Dom 0.
> Now I want to understand, is it possible to run unmodified Android on
> Dom U (full virtualization) or it will require patching
> (par-virtualization). Is there any links or resources in this
> direction, which I may be missing.
>
> Also found this line in one of the Stefano's presentation :" Android
> is based on the Linux kernel ○ Jelly Bean uses Linux 3.4, when it
> updates to 3.7 will get Xen on ARM support out of the box . So it
> means, I should not need much of an effort to use/port Android on Dom
> U (no new drivers will be needed for PV drivers for network, block,
> console, etc.)
> . Is my understanding right here ?
>
> Sorry for this basic question, but just want to understand whether
> from this point I am on my own or still there are some resources which
> I may be missing which can help me to progress further. Want to
> utilize in best possible manner whatever is already available and then
> contribute from there on.
>
> --
> Thanks
> Anshul Makkar
> www.justkernel.com
> http://www.linkedin.com/groups/Just-Kernel-3033180



-- 
Thanks
Anshul Makkar
www.justkernel.com
http://www.linkedin.com/groups/Just-Kernel-3033180

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-08-20  8:52 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 [this message]
2014-08-20 14:16   ` Dario Faggioli
2014-08-20 15:00     ` anshul makkar
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='CACZDEvF_22JYoYVOg=AQepKUXaXMHztJV-0rWVyT=hoZRwU1hA@mail.gmail.com' \
    --to=anshulmakkar@gmail.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.