From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>,
Leon Anavi <leon.anavi@konsulko.com>,
Jagan Teki <jagan@amarulasolutions.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/8] Olimex boards u-boot/linux update
Date: Sun, 24 Oct 2021 16:09:40 +0200 [thread overview]
Message-ID: <20211024160940.4d4b6706@windsurf> (raw)
In-Reply-To: <20211021220023.68288-1-giulio.benetti@benettiengineering.com>
Hello Giulio,
On Fri, 22 Oct 2021 00:00:15 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Giulio Benetti (8):
> configs/olimex_a10_olinuxino: bump to Linux kernel 5.14.13 and u-boot
> 2021.10
> configs/olimex_a10_olinuxino: use FPU NEON strategy
> configs/olimex_a13_olinuxino: bump to Linux kernel 5.14.13 and u-boot
> 2021.10
> configs/olimex_a13_olinuxino: use FPU NEON strategy
> configs/olimex_a20_olinuxino_lime2: bump to Linux kernel 5.14.13 and
> u-boot 2021.10
> configs/olimex_a20_olinuxino_lime: bump to Linux kernel 5.14.13 and
> u-boot 2021.10
> configs/olimex_a20_olinuxino_micro: bump to Linux kernel 5.14.13 and
> u-boot 2021.10
> configs/olimex_a33_olinuxino: bump to Linux kernel 5.14.13 and u-boot
> 2021.10
I have applied all the patches bumping U-Boot/Linux, I hope that you
were able to test them on real hardware. Make sure to monitor the next
Gitlab CI build results to see if there's any new build failure.
However, for the two patches enabling NEON as the FPU, I marked them as
rejected. Indeed, using NEON as the FPU is not always a good idea, as
it explained in the Config.in.help text:
This option allows to use the NEON SIMD unit, as available
in some ARMv7 processors, as a floating-point unit. It
should however be noted that using NEON for floating point
operations doesn't provide a complete compatibility with the
IEEE 754.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-24 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 22:00 [Buildroot] [PATCH 0/8] Olimex boards u-boot/linux update Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 1/8] configs/olimex_a10_olinuxino: bump to Linux kernel 5.14.13 and u-boot 2021.10 Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 2/8] configs/olimex_a10_olinuxino: use FPU NEON strategy Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 3/8] configs/olimex_a13_olinuxino: bump to Linux kernel 5.14.13 and u-boot 2021.10 Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 4/8] configs/olimex_a13_olinuxino: use FPU NEON strategy Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 5/8] configs/olimex_a20_olinuxino_lime2: bump to Linux kernel 5.14.13 and u-boot 2021.10 Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 6/8] configs/olimex_a20_olinuxino_lime: " Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 7/8] configs/olimex_a20_olinuxino_micro: " Giulio Benetti
2021-10-21 22:00 ` [Buildroot] [PATCH 8/8] configs/olimex_a33_olinuxino: " Giulio Benetti
2021-10-24 14:09 ` Thomas Petazzoni [this message]
2021-10-24 14:40 ` [Buildroot] [PATCH 0/8] Olimex boards u-boot/linux update Giulio Benetti
2021-10-25 12:28 ` Giulio Benetti
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=20211024160940.4d4b6706@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=jagan@amarulasolutions.com \
--cc=leon.anavi@konsulko.com \
--cc=luca@lucaceresoli.net \
/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