From: David Laight <david.laight.linux@gmail.com>
To: Romain Naour via buildroot <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@smile.fr>,
Julien Olivain <ju.o@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 01/12] support/config-fragments: remove nios2 toolchain
Date: Fri, 10 Jan 2025 13:06:25 +0000 [thread overview]
Message-ID: <20250110130625.245ef276@pumpkin> (raw)
In-Reply-To: <20250108230521.1345210-1-romain.naour@smile.fr>
On Thu, 9 Jan 2025 00:05:10 +0100
Romain Naour via buildroot <buildroot@buildroot.org> wrote:
> The nios2 architecture was deprecated in gcc-14 and has been removed
> in the upcoming gcc-15 [1][2].
>
> Our last and only nios2 defconfig "qemu_nios2_10m50_defconfig" was
> removed in 2024.11 due to nios2 removal from Qemu 9.1.0 [3].
...
Interesting, I've not seen an indication that nios2 support is being removed
from the Linux kernel.
Not that I've ever considered running Linux on nios2 a sane idea.
(Better to get an fpga with a 'proper' cpu in it.)
I know Intel deprecated nios2 in quartus 23.04 (suggesting that RISC-V was a
suitable alternative), but I suspect that some major telco hardware supplies
objected (I believe they use a lot of nios2 for embedded control code in
mobile base stations - they'll be running with a few kB of code and data).
We certainly found it possible to get a free nios2 licence for our fpga builds
(after being told earlier it wasn't possible to get one).
In any case I spent a few weeks writing a compatible cpu we can use for
our embedded hardware.
(We also use the first gcc that supported it - good enough for the code
we have, especially after some local patches.)
David
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-10 13:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 23:05 [Buildroot] [PATCH 01/12] support/config-fragments: remove nios2 toolchain Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 02/12] support/scripts/gen-bootlin-toolchains: " Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 03/12] toolchain/toolchain-external: remove Bootlin nios2 external toolchain Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 04/12] package/glibc: remove nios2 support Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 05/12] package/gcc: remove nios2 handling Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 06/12] arch: disable nios2 Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 07/12] package: remove BR2_nios2 symbol Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 08/12] linux: " Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 09/12] toolchain: remove BR2_TOOLCHAIN_HAS_GCC_BUG_93847 (nios2 only) Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 10/12] toolchain: remove BR2_TOOLCHAIN_HAS_GCC_BUG_99410 " Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 11/12] toolchain: remove remaining BR2_nios2 from toolchain bugs Romain Naour via buildroot
2025-01-08 23:05 ` [Buildroot] [PATCH 12/12] arch/nios2: drop architecture Romain Naour via buildroot
2025-01-10 13:06 ` David Laight [this message]
2025-01-10 20:15 ` [Buildroot] [PATCH 01/12] support/config-fragments: remove nios2 toolchain Romain Naour via buildroot
2025-01-15 20:40 ` Julien Olivain
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=20250110130625.245ef276@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
/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