From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RESEND][PATCH 1/3] meta: add new qemuarma9 machine definition
Date: Thu, 14 May 2015 14:46:37 +0100 [thread overview]
Message-ID: <1431611197.30971.212.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=X08DRhpZjH8Ge0vjXXuk1dfa2RbXiDarNX153-oE1Cmw@mail.gmail.com>
On Wed, 2015-05-13 at 18:17 -0700, Andre McCurdy wrote:
> On Tue, May 12, 2015 at 7:47 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > 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
>
> +1 for updating qemuarm to an ARMv7 CPU.
One thing I did notice about the new proposed arm machine was the lack
of graphics support. We really do need a machine with graphics. If we
could get a machine which had graphics and more memory that would be
much more attractive to switch to.
This also has implications on the kernel support (cc Bruce).
> As for dropping thumb1 support that's probably fine too - although
> technically (if someone really did want to keep thumb1 support alive)
> I guess nothing prevents testing thumb1 binaries on an ARMv7 CPU?
Just guessing but they might work in some cases an a v7 CPU but fail on
older ones due to alignment constraints?
Cheers,
Richard
next prev parent reply other threads:[~2015-05-14 13:46 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
2015-05-14 1:17 ` Andre McCurdy
2015-05-14 13:46 ` Richard Purdie [this message]
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=1431611197.30971.212.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=dmitry_eremin@mentor.com \
--cc=openembedded-core@lists.openembedded.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.