From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RESEND][PATCH 1/3] meta: add new qemuarma9 machine definition
Date: Tue, 12 May 2015 16:47:49 +0200 [thread overview]
Message-ID: <20150512144749.GD2714@jama> (raw)
In-Reply-To: <CAJTo0LZUd4bcbfTL+TbtiXOU1wc9ZaFGP0mTM_Y0hVMb1eMqWg@mail.gmail.com>
On Tue, May 12, 2015 at 03:25:43PM +0100, Burton, Ross wrote:
> On 11 May 2015 at 20:52, Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
> wrote:
>
> > Currently qemuarm is limited to 256 Mb of RAM. Sometimes this is too
> > little to run necessary applications. Add a new arm configuration based
> > on Versatile Express board, Cortex-A9 CPU, allowing up to 1Gb of RAM.
> >
>
> Not sure I'm keen on oe-core having two almost-identical qemuarm machines.
> Why not just change the qemuarm machine to use the A9?
Then we should officially drop thumb1 support, because current qemuarm
builds are quite broken when thumb is enabled and dropping current
qemuarm or replacing it with A9 variant will prevent oe-core to be
testable on autobuilder. See
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7717
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2015-05-12 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 19:52 [RESEND][PATCH 1/3] meta: add new qemuarma9 machine definition Dmitry Eremin-Solenikov
2015-05-11 19:52 ` [RESEND][PATCH 2/3] scripts/runqemu: factor out some qemuarm configuration options Dmitry Eremin-Solenikov
2015-05-11 19:52 ` [RESEND][PATCH 3/3] scripts/runqemu: add qemuarma9 support Dmitry Eremin-Solenikov
2015-05-12 14:25 ` [RESEND][PATCH 1/3] meta: add new qemuarma9 machine definition Burton, Ross
2015-05-12 14:47 ` Martin Jansa [this message]
2015-05-14 1:17 ` Andre McCurdy
2015-05-14 13:46 ` Richard Purdie
2015-05-14 14:37 ` Bruce Ashfield
2015-05-15 7:18 ` Dmitry Eremin-Solenikov
2015-05-15 14:38 ` Bruce Ashfield
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=20150512144749.GD2714@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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