Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: <Jamie.Gibbons@microchip.com>
Cc: Valentina.FernandezAlanis@microchip.com,
	Conor.Dooley@microchip.com, Ludovic.Desroches@microchip.com,
	Nicolas.Ferre@microchip.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/beaglev_fire: add support for BeagleV Fire
Date: Thu, 23 May 2024 12:33:43 +0200	[thread overview]
Message-ID: <20240523123343.28a90afa@windsurf> (raw)
In-Reply-To: <c6b4014930339dbdddcad705965e58e61576bdc7.camel@microchip.com>

Hello Jamie,

On Wed, 22 May 2024 16:06:54 +0000
<Jamie.Gibbons@microchip.com> wrote:

> > Nowadays, we try to use distro bootcmd instead of custom uBoot
> > environment scripts. See
> > https://source.denx.de/u-boot/u-boot/-/blob/v2024.04/doc/develop/distro.rst
> > for some details.  
> 
> Could you clarify the change you are looking for here? We do use distro
> bootcmd (#include <config_distro_bootcmd.h> in our U-Boot config). This
> scans for our boot.scr, which as far as I can see is supported under
> that link you sent. Are you asking for us to replace the boot.scr with
> extlinux.conf? I can see other boards use "extlinux.conf" or
> "boot.cmd". Our preference is to use "boot.cmd" as this allows us to
> use FITImage and FDT set. Could you clarify your request?

Yes, we ideally like new defconfigs to use extlinux.conf when possible.
One motivation is precisely that boot script tend to do random hacks
that are not very nice. That's not a strong requirement though, more of
a "nice to have".

> > > +BR2_PACKAGE_BASH=y  
> > 
> > Why?  
> The above four packages were used to support the gateware scripts.
> These will likely be removed for v2 due to the changes in those
> scripts.

I suppose such scripts don't really require bash, the Busybox shell
should be more than enough.

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

  reply	other threads:[~2024-05-23 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 14:34 [Buildroot] [PATCH 1/1] configs/beaglev_fire: add support for BeagleV Fire Jamie Gibbons via buildroot
2024-05-09 20:03 ` Thomas Petazzoni via buildroot
2024-05-22 16:06   ` Jamie.Gibbons--- via buildroot
2024-05-23 10:33     ` Thomas Petazzoni via buildroot [this message]
2024-05-22 17:27   ` Robert Nelson
     [not found]     ` <20240522-geometric-everglade-a978e7098495@spud>
2024-05-22 19:02       ` Robert Nelson

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=20240523123343.28a90afa@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Conor.Dooley@microchip.com \
    --cc=Jamie.Gibbons@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Valentina.FernandezAlanis@microchip.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