Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "Simek, Michal" <michal.simek@amd.com>,
	"Erkiaga Elorza, Ibai" <ibai.erkiaga-elorza@amd.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>,
	"Frager, Neal" <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v3 1/6] package/binutils-bare-metal: new package
Date: Wed, 4 Oct 2023 23:57:56 +0200	[thread overview]
Message-ID: <20231004235756.255601f7@windsurf> (raw)
In-Reply-To: <20231003091539.5e26d558@booty>

Hello Luca,

On Tue, 3 Oct 2023 09:15:39 +0200
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:

> > > This series instead goes to the other extreme, E.G. we build the
> > > entire microblaze toolchain from scratch and then use it to build
> > > the firmware and use it in the u-boot package - This is nice
> > > because it is all in Buildroot and we have it all under control,
> > > but also brings quite some build time overhead for building the
> > > toolchain before building the    
> > (small) toolchain. You can naturally "solve" it by using two
> > defconfigs, E.G. one that builds the pmufw and another that uses
> > the prebuilt one, but it isn't very handy either.  
> 
> I think the approach taken here by Neal and Ibai is valuable,
> especially as it would allow Buildroot defconfigs to be self-standing.
> Additionally it is already proving useful as it prompted "the
> community" (mostly Neal -- thanks about that) to upstream patches
> needed to support Microblaze in binutils and gcc, that are currently
> downstream.

I agree.

> I fyou are thinking about toolchains.bootlin.com, I am not the
> maintainer of those toolchains but I think the idea is to only have
> Linux toolchains there, not bare metal ones, thus newlib is not
> supported. Also I'm pretty sure downstream feature patches are
> absolutely not welcome there.

Regarding providing a bare-metal toolchain on toolchains.bootlin.com,
we have a chicken-and-egg problem: the toolchains on
toolchains.bootlin.com are built using... Buildroot. So if we want
toolchains.bootlin.com to offer pre-built bare-metal toolchains, we
need Buildroot to be able to generate such bare-metal toolchains in the
first place :-)

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

  reply	other threads:[~2023-10-04 21:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 10:04 [Buildroot] [PATCH v3 1/6] package/binutils-bare-metal: new package Neal Frager via buildroot
2023-09-04 10:04 ` [Buildroot] [PATCH v3 2/6] package/gcc-bare-metal: " Neal Frager via buildroot
2023-09-22 12:53   ` Luca Ceresoli via buildroot
2023-09-04 10:04 ` [Buildroot] [PATCH v3 3/6] package/newlib-bare-metal: " Neal Frager via buildroot
2023-09-22 12:54   ` Luca Ceresoli via buildroot
2023-09-04 10:04 ` [Buildroot] [PATCH v3 4/6] package/toolchain-bare-metal: " Neal Frager via buildroot
2023-09-22 12:55   ` Luca Ceresoli via buildroot
2023-09-04 10:04 ` [Buildroot] [PATCH v3 5/6] boot/zynqmp-firmware: new boot firmware Neal Frager via buildroot
2023-09-22 12:57   ` Luca Ceresoli via buildroot
2023-09-04 10:04 ` [Buildroot] [PATCH v3 6/6] boot/uboot.mk: new zynqmp pmufw build option Neal Frager via buildroot
2023-09-22 12:58   ` Luca Ceresoli via buildroot
2023-09-22 12:52 ` [Buildroot] [PATCH v3 1/6] package/binutils-bare-metal: new package Luca Ceresoli via buildroot
2023-09-22 13:34   ` Frager, Neal via buildroot
2023-09-22 13:57     ` Luca Ceresoli via buildroot
2023-09-22 14:57       ` Frager, Neal via buildroot
     [not found]         ` <MN0PR12MB60045761B225083426E7B1A1A0FFA@MN0PR12MB6004.namprd12.prod.outlook.com>
2023-09-23  9:50           ` Frager, Neal via buildroot
2023-09-25  2:59             ` Luca Ceresoli via buildroot
2023-09-25  3:43               ` Frager, Neal via buildroot
2023-10-01 11:24                 ` Peter Korsgaard
2023-10-01 16:11                   ` Frager, Neal via buildroot
2023-10-03  7:15                     ` Luca Ceresoli via buildroot
2023-10-04 21:57                       ` Thomas Petazzoni via buildroot [this message]
2023-10-05  5:59                         ` Frager, Neal 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=20231004235756.255601f7@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=michal.simek@amd.com \
    --cc=neal.frager@amd.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