[Buildroot] Building u-boot on PowerPC64 (but u-boot only supports 32 bits)

Alvaro Gamez alvaro.gamez at hazent.com
Tue Nov 13 11:39:03 UTC 2018


On Tue, Nov 13, 2018 at 08:52:08AM -0200, Carlos Santos wrote:
> > From: "Alvaro Gamez" <alvaro.gamez at hazent.com>
> > To: "buildroot" <buildroot at buildroot.org>
> > Sent: Terça-feira, 13 de novembro de 2018 7:10:34
> > Subject: [Buildroot] Building u-boot on PowerPC64 (but u-boot only supports 32 bits)
> 
> > I can no doubt create another project that is intended only for building u-boot,
> > but then why would I use buildroot instead of simply compiling u-boot? I'd
> > really like to have everything integrated on buildroot, and I guess this can be
> > useful for any other packages.
> 
> Here at DATACOM our initial approach was building u-boot along with the
> firmware on 32-bit projects and have separate 32-bit projects to build
> it for 64-bit processors.
> 
> After some time we decided to provide u-boot as a pre-built binary for
> each board. The boot loader is a very critical part of any system and
> once it starts working as expected there is to reason to rebuild it over
> and over again. In fact it would be risky to do that.

Thanks for sharing your experience! You're right in this last part, I won't
be needing to recompile u-boot each time I upgrade they payload of my system.

Since I'm using buildroot as a submodule, I don't really need to manage a
full repository or project, but just a new defconfig that builds the
toolchain I need to compile uboot and uboot itself.

Except for this case, I don't know if there's any other use case that
involves compiling software both for 32 and 64 bits on a single project.
If there is, maybe it's still worthwhile taking a look at how can two
different toolchains be built and selected on buildroot, but I guess that's
gonna turn out to be pretty complex.

Best regards!

-- 
Alvaro G. M.



More information about the buildroot mailing list