From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brian Cain <brian.cain@oss.qualcomm.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC v2 00/14] add hexagon architecture
Date: Wed, 5 Feb 2025 11:49:09 +0100 [thread overview]
Message-ID: <20250205114909.18e5f9dd@windsurf> (raw)
In-Reply-To: <20241219053053.2389046-1-brian.cain@oss.qualcomm.com>
Hello Brian,
On Wed, 18 Dec 2024 21:30:39 -0800
Brian Cain <brian.cain@oss.qualcomm.com> wrote:
> I'm sharing this series with the list for the sake of discussion about
> how the approach taken could improve. It's likely not quite ready for
> upstreaming yet.
Thanks for this series. Could you share some more details about the
Hexagon architecture, what is its current usage and use cases, roadmap?
Indeed, adding support for a new architecture in Buildroot means that
our autobuilders will try building all packages for this architecture,
which will certainly raise a large number of issues, which you will
have to address as a maintainer of this CPU architecture. How committed
are you to this effort?
This is even more significant as your proposal is to support this
architecture with Clang as a compiler, which will certainly break a LOT
of packages, causing even more troubles.
So what you're proposing here is certainly very interesting, but it's a
really large endeavor, and we need to understand whether you'll still
be around in 6 or 12 months to support this and address issues.
I'm going to reply to the individual patches with some more comments,
but I think this top-level discussion is the most important.
Thanks!
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-02-05 10:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 14:07 [Buildroot] [RFC 00/12] add hexagon architecture Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 01/12] arch: add hexagon architecture support Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 02/12] toolchain/toolchain-external: add hexagon toolchain support Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 03/12] toolchain/toolchain-external: add hexagon support for toolchain-wrapper Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 04/12] toolchain/toolchain-external: add support for clang Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 05/12] toolchain/toolchain-external: skip "-march=" for hexagon Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 06/12] linux: add support for hexagon clang Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 07/12] arch: add hexagon ARCH definition Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 08/12] package/hexagonMVM: new package Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 09/12] board/qcom/sa8775: add support for qcom sa8775-cdsp0 Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 10/12] configs: add hexagon QEMU config Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 11/12] DEVELOPERS: add myself as developer for hexagon Brian Cain
2024-10-25 14:07 ` [Buildroot] [RFC 12/12] package: disable -ztext " Brian Cain
2024-12-19 5:30 ` [Buildroot] [RFC v2 00/14] add hexagon architecture Brian Cain
2024-12-19 5:30 ` [Buildroot] [RFC v2 01/14] arch: add hexagon architecture support Brian Cain via buildroot
2025-02-05 10:54 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 02/14] toolchain/toolchain-external: add hexagon toolchain support Brian Cain via buildroot
2025-02-05 10:58 ` Thomas Petazzoni
2024-12-19 5:30 ` [Buildroot] [RFC v2 03/14] toolchain/toolchain-external: add hexagon support for toolchain-wrapper Brian Cain via buildroot
2025-02-05 11:01 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 04/14] toolchain/toolchain-external: add support for clang Brian Cain via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 05/14] toolchain/toolchain-external: skip "-march=" for hexagon Brian Cain via buildroot
2025-02-05 11:03 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 06/14] linux: add support for hexagon clang Brian Cain via buildroot
2025-02-05 11:04 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 07/14] arch: add hexagon ARCH definition Brian Cain via buildroot
2025-02-05 11:05 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 08/14] package/hexagonMVM: new package Brian Cain via buildroot
2025-02-05 11:08 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 09/14] board/qcom/sa8775: add support for qcom sa8775-cdsp0 Brian Cain
2025-02-05 11:28 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 10/14] configs: add hexagon QEMU config Brian Cain via buildroot
2025-02-05 11:26 ` Thomas Petazzoni
2025-03-04 21:16 ` Brian Cain via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 11/14] DEVELOPERS: add myself as developer for hexagon Brian Cain via buildroot
2025-02-05 11:28 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 12/14] toolchain: disable PIE " Brian Cain
2025-02-05 11:29 ` Thomas Petazzoni
2024-12-19 5:30 ` [Buildroot] [RFC v2 13/14] configs: switch hexagon QEMU to SHARED Brian Cain via buildroot
2025-02-05 11:30 ` Thomas Petazzoni via buildroot
2024-12-19 5:30 ` [Buildroot] [RFC v2 14/14] package: disable -ztext Brian Cain via buildroot
2025-02-05 11:33 ` Thomas Petazzoni
2025-02-05 10:49 ` Thomas Petazzoni via buildroot [this message]
2025-03-10 0:44 ` [Buildroot] [RFC v2 00/14] add hexagon architecture Brian Cain 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=20250205114909.18e5f9dd@windsurf \
--to=buildroot@buildroot.org \
--cc=brian.cain@oss.qualcomm.com \
--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