From: Adrian Bunk <bunk@stusta.de>
To: Steve Pavao <stevep@korgrd.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified
Date: Mon, 4 Nov 2019 18:11:27 +0200 [thread overview]
Message-ID: <20191104161127.GC5390@localhost> (raw)
In-Reply-To: <9F6E6EE0-4FF9-4251-9B7B-37A734DA4824@korgrd.com>
On Mon, Nov 04, 2019 at 10:48:57AM -0500, Steve Pavao wrote:
>
> > On Nov 3, 2019, at 1:25 PM, Adrian Bunk <bunk@stusta.de> wrote:
> >
> > On Sun, Nov 03, 2019 at 05:56:45PM +0000, Andrei Gherzan wrote:
> >> On 3 November 2019 13:18:53 GMT, Khem Raj <raj.khem@gmail.com> wrote:
> >>> On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan <andrei@gherzan.ro>
> >>> wrote:
> >>>> I was thinking about this. The erratum seems to show that this
> >>> applies
> >>>> to all revisions of a53. So it sounds like we should add it in
> >>>> `tune-cortexa53.inc`.
> >>>>
> >>>
> >>> Up to r0b4 only so maybe not all a53 implementations are impacted
> >>>
> >>
> >> As far as I know that is the latest revision. Do you mean that newer revision might come up with this fixed?
> >
> > It is fixed in some r0p4 implementations, indicated in REVIDR[8].
>
> I am closer to understanding why I experience an error when building with the ARM errata switches.
>
> I believe it is related to 32-bit app support in my poky Linux 64-bit build (I add this to support vcgencmd and vcdbg 32-bit apps.)
>
> When I remove the 32-bit support, the build completes OK. As of now, adding the following seems to work fine to acheive this:
>
> TARGET_CC_ARCH_append += " -mfix-cortex-a53-843419 -mfix-cortex-a53-835769”
>
> Something in the following block seems to be the culprit.:
>
> # for vcgencmd and vcdbg 32-bit executable support in the OS image (comment out for -c populate_sdk)
> require conf/multilib.conf
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE_virtclass-multilib-lib32 = "armv7a"
> IMAGE_INSTALL_append += " vcgencmd lib32-glibc lib32-libgcc lib32-libstdc++ vcdbg rpi-setup \
> “
>
> I will post again when I have localized the build problem further. Maybe there’s some 64-bit vs. 32-bit build confusion going on, and the armv7a default tune switch for 32-bits is colliding with the errata switches.
The errata switches are only valid for aarch64, not for armv7a.
There is likely some kind of "invalid option" earlier in your build.
> - Steve Pavao
> Korg R&D
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-11-04 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 5:32 [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified Steve Pavao
2019-11-01 8:27 ` Andrei Gherzan
2019-11-01 17:18 ` Khem Raj
2019-11-03 10:46 ` Andrei Gherzan
2019-11-03 13:18 ` Khem Raj
2019-11-03 17:56 ` Andrei Gherzan
2019-11-03 18:14 ` Khem Raj
2019-11-03 18:25 ` Adrian Bunk
2019-11-04 15:48 ` Steve Pavao
2019-11-04 16:11 ` Adrian Bunk [this message]
2019-11-04 16:16 ` Steve Pavao
2019-11-04 16:32 ` Steve Pavao
2019-11-04 21:26 ` Steve Pavao
2019-11-07 18:42 ` Steve Pavao
2019-11-07 18:58 ` Khem Raj
2019-12-03 23:53 ` [yocto] " Steve Pavao
2019-12-04 0:06 ` Khem Raj
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=20191104161127.GC5390@localhost \
--to=bunk@stusta.de \
--cc=stevep@korgrd.com \
--cc=yocto@yoctoproject.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.