From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Christophe Priouzeau <christophe.priouzeau@foss.st.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/stm32f4xx_defconfig: off network utils from busybox
Date: Fri, 28 Jul 2023 23:01:15 +0200 [thread overview]
Message-ID: <20230728230115.1585253c@windsurf> (raw)
In-Reply-To: <20230528153156.1685512-1-dario.binacchi@amarulasolutions.com>
On Sun, 28 May 2023 17:31:56 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> Kernel is built without network support, so network utils are useless.
> This has a positive impact on the size of busybox and xipImage, making
> them smaller.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> .../common/stm32f4xx/busybox.fragment | 21 +++++++++++++++++++
> .../common/stm32f4xx/stm32-post-build.sh | 3 +++
> configs/stm32f429_disco_xip_defconfig | 1 +
> configs/stm32f469_disco_sd_defconfig | 1 +
> configs/stm32f469_disco_xip_defconfig | 1 +
> 5 files changed, 27 insertions(+)
> create mode 100644 board/stmicroelectronics/common/stm32f4xx/busybox.fragment
We normally don't want to have defconfigs with too many tweaks, but I
agree the STM32F4 ones are special due to their low flash/RAM size, so
applied to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-28 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 15:31 [Buildroot] [PATCH 1/1] configs/stm32f4xx_defconfig: off network utils from busybox Dario Binacchi
2023-05-30 7:49 ` Giulio Benetti
2023-07-28 21:01 ` Thomas Petazzoni via buildroot [this message]
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=20230728230115.1585253c@windsurf \
--to=buildroot@buildroot.org \
--cc=christophe.priouzeau@foss.st.com \
--cc=dario.binacchi@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