From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Vincent Stehlé via buildroot" <buildroot@buildroot.org>
Cc: "Vincent Stehlé" <vincent.stehle@laposte.net>,
"Julien Olivain" <ju.o@free.fr>,
"Giulio Benetti" <giulio.benetti@benettiengineering.com>,
"Romain Naour" <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH 0/5] Add support for HPPA (PA-RISC)
Date: Fri, 30 May 2025 22:04:09 +0200 [thread overview]
Message-ID: <20250530220409.5187b93a@windsurf> (raw)
In-Reply-To: <20250523174313.7056-1-vincent.stehle@laposte.net>
Hello Vincent,
On Fri, 23 May 2025 19:43:08 +0200
Vincent Stehlé via buildroot <buildroot@buildroot.org> wrote:
> This patch series adds minimal support for a "new" architecture: HP/PA
> (a.k.a. PA-RISC); one of the RISC architectures of the late 80ies.
>
> This architecture is still well supported by gcc, Linux and some other
> distros; therefore it should not be too much of a burden to support in
> Buildroot.
>
> With those patches we have enough to build and run a Linux kernel with
> busybox on Qemu, which makes it easily testable.
>
> I plan to add support later on for running on actual hardware; the HP
> 9000 712 PA-RISC Workstation.
I have nothing against HPPA, but is this going to be used in practice?
We already support quite a lot of "exotic" architectures in Buildroot,
and they are a fairly heavy maintenance burden, due to:
- Architecture dependencies in several core packages. For example,
libffi, libcap, are used by zillions of packages and they have
architecture dependencies.
- GCC issues. Our autobuilders are flooded by GCC issues affecting
SuperH, Microblaze and other exotic architectures, and those issues
are never fixed because nobody cares.
So while I find it nice that we support so many architectures, I think
we should all wonder whether it makes sense to support even more and
for what use-case.
Thanks for your feedback!
Thomas
--
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:[~2025-05-30 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 17:43 [Buildroot] [PATCH 0/5] Add support for HPPA (PA-RISC) Vincent Stehlé via buildroot
2025-05-23 17:43 ` [Buildroot] [PATCH 1/5] hppa: Add new architecture Vincent Stehlé via buildroot
2025-05-23 20:42 ` Romain Naour via buildroot
2025-05-23 17:43 ` [Buildroot] [PATCH 2/5] package/gcc: enable hppa support Vincent Stehlé via buildroot
2025-05-23 20:43 ` Romain Naour via buildroot
2025-05-23 17:43 ` [Buildroot] [PATCH 3/5] package/glibc: " Vincent Stehlé via buildroot
2025-05-23 20:45 ` Romain Naour via buildroot
2025-05-23 17:43 ` [Buildroot] [PATCH 4/5] package/qemu: enable host-qemu " Vincent Stehlé via buildroot
2025-05-23 20:49 ` Romain Naour via buildroot
2025-05-23 17:43 ` [Buildroot] [PATCH 5/5] configs/qemu_hppa_b160l: new defconfig Vincent Stehlé via buildroot
2025-05-23 20:53 ` Romain Naour via buildroot
2025-06-01 12:59 ` Vincent Stehlé via buildroot
2025-05-23 17:49 ` [Buildroot] [PATCH 2/5] package/gcc: enable hppa support Vincent Stehlé via buildroot
2025-05-23 17:49 ` [Buildroot] [PATCH 5/5] configs/qemu_hppa_b160l: new defconfig Vincent Stehlé via buildroot
2025-05-30 20:04 ` Thomas Petazzoni via buildroot [this message]
2025-06-01 13:23 ` [Buildroot] [PATCH 0/5] Add support for HPPA (PA-RISC) Vincent Stehlé via buildroot
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=20250530220409.5187b93a@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vincent.stehle@laposte.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 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.