From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Toolchain for STM32MP15x
Date: Mon, 25 Nov 2019 17:43:01 +0100 [thread overview]
Message-ID: <CABDcavZaYu_bhrLAXZSxmuohTRW8aVbKUxKnwpv175DC=sQpVA@mail.gmail.com> (raw)
In-Reply-To: <CABDcavZ3+UjUpRyYtXf_zPJVvUZY_rvPAbi6uZ04P7L=Juc5oA@mail.gmail.com>
Hi all,
I have setup the toolchain with the settings from my previous email
(-mcpu=cortex-a7 -mfpu=neon-vfpv4)
When I try to build the Linux kernel I get lots of warnings about
conflicting toolchain options:
arch/arm/kernel/elf.c:1:0: warning: switch -mcpu=cortex-a7 conflicts
with -march=armv5t switch
This is with OSELAS.Toolchain-2016.06.1, using arm-v7a-linux-gnueabihf.
I am not sure where the -march=armv5t is coming from, since this is an
arm-v7a toolchain.
Also if I use -mcpu=cortex-a9 instead of cortex-a7, there are no warnings :-?
Can anyone sehd some light ?
Thank you,
Guillermo
El lun., 25 nov. 2019 a las 13:33, Guillermo Rodriguez Garcia
(<guille.rodriguez@gmail.com>) escribió:
>
> Hi all,
>
> I am trying to setup a toolchain for the STM32MP15x. The main CPU is a
> single or dual (depending on p/n) Cortex-A7, supporting NEON and
> VFPv4.
>
> I'm using the OSELAS arm-v7a-linux-gnueabihf toolchain. As for the
> extra flags I believe I should use -mcpu=cortex-a7 -mfpu=neon-vfpv4.
>
> Does this look correct? Any comments / hints?
>
> BR,
>
> Guillermo Rodriguez Garcia
> guille.rodriguez@gmail.com
--
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-11-25 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 12:33 Guillermo Rodriguez Garcia
2019-11-25 16:43 ` Guillermo Rodriguez Garcia [this message]
2019-11-26 7:24 ` Michael Olbrich
2019-11-26 9:27 ` Guillermo Rodriguez Garcia
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='CABDcavZaYu_bhrLAXZSxmuohTRW8aVbKUxKnwpv175DC=sQpVA@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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