All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Julien Grall" <julien.grall@citrix.com>,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Claudio Scordino" <claudio@evidence.eu.com>,
	xen-devel@lists.xen.org
Subject: Re: Best board for ARM ?
Date: Mon, 9 Dec 2013 17:48:51 +0100	[thread overview]
Message-ID: <1386607731.5488.10.camel@Solace> (raw)
In-Reply-To: <1386604414.7812.32.camel@kazak.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1787 bytes --]

[Adding Julien]

On lun, 2013-12-09 at 15:53 +0000, Ian Campbell wrote:
> On Mon, 2013-12-09 at 16:44 +0100, Claudio Scordino wrote:
> > Our question at this point is: which is the most tested and
> > recommended ARM platform among the ones listed ?
> 
> Arndale and midway are probably the best. However both are difficult to
> get hold of in their own way... Arndale's seem to take ages to ship,
> while I don't think Midway is available to buy yet, and in any case they
> are server class (i.e. not cheap).
> 
Since it's embedded, midway is particularly bad suited, I think, even
for prototypes (apart it being expensive and not yet available). :-)

> Arndale is probably the best bet. Allwinner based stuff (aka sunxi) is
> less well tested overall but might have better availability, it is also
> super cheap in most cases (e.g. cubieboard2/truck).
> 
Ok, thanks Ian for the info!

In case one wants to go for cubie, this is where all the information
lives, right?
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner

Is it still current? Have things got any better lately, from either
Linux or Xen side?

While this is, I think, the same for Arndale:
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale
which does look less "hacky", at least at a first glance...

Claudio, perhaps you can investigate how easy it would be for you to get
an Arndale board, and fallback on cubie2/truck if it's actually that
hard?

Thanks again Ian,
Dario

-- 
<<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)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2013-12-09 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 15:44 Best board for ARM ? Claudio Scordino
2013-12-09 15:53 ` Ian Campbell
2013-12-09 16:48   ` Dario Faggioli [this message]
2013-12-09 16:59     ` Ian Campbell
2013-12-10  8:11     ` Claudio Scordino
2013-12-10  9:45       ` Ian Campbell
2013-12-10  9:54         ` Roger Pau Monné
2013-12-10 10:16           ` 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=1386607731.5488.10.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=claudio@evidence.eu.com \
    --cc=julien.grall@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@eu.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.