From: Khem Raj <raj.khem@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] qemu.bbclass: duplicate armv7a over-ride for armv7ve
Date: Mon, 11 Jan 2016 16:29:04 -0800 [thread overview]
Message-ID: <8C1C6409-C8B8-43EE-AE9A-8F376177AA00@gmail.com> (raw)
In-Reply-To: <CAJ86T=V71XZfoY54VgBJP2=Ec6ycpi2YSF6FcR6tTuow4eBaVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
> On Jan 7, 2016, at 1:17 PM, Andre McCurdy <armccurdy@gmail.com> wrote:
>
> On Thu, Jan 7, 2016 at 1:09 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> On Thu, Jan 07, 2016 at 12:53:10PM -0800, Andre McCurdy wrote:
>>> Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
>>> ---
>>> meta/classes/qemu.bbclass | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/meta/classes/qemu.bbclass b/meta/classes/qemu.bbclass
>>> index 315c17f..4ec7657 100644
>>> --- a/meta/classes/qemu.bbclass
>>> +++ b/meta/classes/qemu.bbclass
>>> @@ -43,6 +43,7 @@ QEMU_OPTIONS[vardeps] += "QEMU_EXTRAOPTIONS_${PACKAGE_ARCH}"
>>> QEMU_EXTRAOPTIONS_iwmmxt = " -cpu pxa270-c5"
>>> QEMU_EXTRAOPTIONS_armv6 = " -cpu arm1136"
>>> QEMU_EXTRAOPTIONS_armv7a = " -cpu cortex-a8"
>>> +QEMU_EXTRAOPTIONS_armv7ve = " -cpu cortex-a8"
>>
>> would it make sense to use cortex-a15 here? It's supported at least in qemu-2.5.0
>
> Yes, I think you're right. If qemu configured for cortex-a8 is going
> to barf on armv7ve integer division instructions then we should enable
> an armv7ve cpu such as cortex-a15.
>
> To avoid unnecessary diversity, should we then also use cortex-a15 for armv7a ?
I think yes.
>
>>> QEMU_EXTRAOPTIONS_ppce500v2 = " -cpu e500v2"
>>> QEMU_EXTRAOPTIONS_ppce500mc = " -cpu e500mc"
>>> QEMU_EXTRAOPTIONS_ppce5500 = " -cpu e5500"
>>> --
>>> 1.9.1
>>>
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>> --
>> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-01-12 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 20:53 [PATCH 0/4] duplicate armv7a over-rides for armv7ve Andre McCurdy
2016-01-07 20:53 ` [PATCH 1/4] qemu.bbclass: duplicate armv7a over-ride " Andre McCurdy
2016-01-07 21:09 ` Martin Jansa
2016-01-07 21:17 ` Andre McCurdy
2016-01-12 0:29 ` Khem Raj [this message]
2016-01-07 20:53 ` [PATCH 2/4] gcc-configure-common.inc: " Andre McCurdy
2016-01-07 20:53 ` [PATCH 3/4] libav.inc: duplicate armv7a over-rides " Andre McCurdy
2016-01-07 20:53 ` [PATCH 4/4] libpostproc: " Andre McCurdy
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=8C1C6409-C8B8-43EE-AE9A-8F376177AA00@gmail.com \
--to=raj.khem@gmail.com \
--cc=armccurdy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox