Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	linux-amarula@amarulasolutions.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/3] tinit and stm32f746_disco_sd_defconfig
Date: Tue, 20 Aug 2024 23:02:59 +0200	[thread overview]
Message-ID: <20240820230259.1449837e@windsurf> (raw)
In-Reply-To: <CABGWkvr-7ms+bSE5R+h7ocUDmFS-XFXaZs453mkfNbBo3D7StQ@mail.gmail.com>

Hello Dario,

On Tue, 20 Aug 2024 20:47:09 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:

> > - I believe you should drop entirely the logo thing in tinit, we don't
> >   have such "logos" in any other Buildroot defconfig, so I don't see
> >   why we would have one for those super small noMMU defconfigs. This
> >   would allow to get rid of tiny-setup.sh stuff.  
> 
> I implemented the logo management only to ensure that the patch
> "board/canaan/k210-soc: use tinit as Linux init process" was backward
> compatible.
> The previous script included the Linux logo. But if this is not an
> issue, I agree with you
>  that it's better to adopt a simpler approach.

I think it could be dropped (perhaps as a preparation commit). No other
Buildroot defconfig has this, it doesn't bring anything really useful,
and is just extra complexity for no benefit.

> > Why do we need a busybox-tiny.config? We already have
> > package/busybox/busybox-minimal.config. How different are they?  
> 
> I think this is a configuration I used for upstreaming the Linux
> display driver.
> I will remove it and use the busybox-minimal.config.

Perfect, thanks a lot!

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-08-20 21:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03 15:55 [Buildroot] [PATCH 0/3] tinit and stm32f746_disco_sd_defconfig Dario Binacchi
2024-08-03 15:55 ` [Buildroot] [PATCH 1/3] package/tinit: new package Dario Binacchi
2024-08-03 15:55 ` [Buildroot] [PATCH 2/3] configs/stm32f746_disco_sd_defconfig: new defconfig Dario Binacchi
2024-08-03 15:55 ` [Buildroot] [PATCH 3/3] board/canaan/k210-soc: use tinit as Linux init process Dario Binacchi
2024-08-03 20:45 ` [Buildroot] [PATCH 0/3] tinit and stm32f746_disco_sd_defconfig Thomas Petazzoni via buildroot
2024-08-05 17:40   ` Damien Le Moal
2024-08-20 18:47   ` Dario Binacchi
2024-08-20 21:02     ` Thomas Petazzoni via buildroot [this message]
2024-08-04  0:47 ` Waldemar Brodkorb
2024-08-20 19:03   ` Dario Binacchi
2024-08-24  4:10     ` Waldemar Brodkorb

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=20240820230259.1449837e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=dlemoal@kernel.org \
    --cc=linux-amarula@amarulasolutions.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