From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Christophe Priouzeau <christophe.priouzeau@foss.st.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/stm32f429_disco_xip_defconfig: fix runtime error due to low ram space and bump to linux version 6.1.27
Date: Sun, 7 May 2023 14:48:29 +0200 [thread overview]
Message-ID: <20230507124829.GR252090@scaer> (raw)
In-Reply-To: <CABGWkvqpAsu8NjkfW7RVQTbBrrsA_koVffPSVh8K5dUYhmHX6Q@mail.gmail.com>
Dario, All,
On 2023-05-06 16:21 +0200, Dario Binacchi spake thusly:
> On Mon, May 1, 2023 at 6:26 PM Giulio Benetti
> <giulio.benetti@benettiengineering.com> wrote:
> > After booting Linux the userspace is unusable since every command issued,
> > that is a symlink to busybox, fails because of no free ram. So let's
> > disable IIO in linux.config to give some more ram to userspace.
> I have also experienced this type of behavior when using ST boards in
> general (stm32f429-disco, stm32f469-disco,
> and stm32f769-disco), and every time I wonder whether it is better to
> update the kernel (which always occupies more
> memory with each new version) or not. The idea I have is to prefer the
> kernel to user space, and therefore disable
> starting from the user space first of all, but my opinion is debatable.
Thanks for the feedback.
The thing is: how useful is Industrial IO (IIO) on a device such as the
stm32 disco family? I suspect the interest in IIO for those devices to
be virtually nill, so Giulio's change does make sense.
Regards,
Yann E. MORIN.
> Thanks and regards,
> Dario
>
> > Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> > ---
> > board/stmicroelectronics/stm32f429-disco/linux.config | 4 ----
> > configs/stm32f429_disco_xip_defconfig | 2 +-
> > 2 files changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git a/board/stmicroelectronics/stm32f429-disco/linux.config b/board/stmicroelectronics/stm32f429-disco/linux.config
> > index 7b5c60f180..02d9c2d1e0 100644
> > --- a/board/stmicroelectronics/stm32f429-disco/linux.config
> > +++ b/board/stmicroelectronics/stm32f429-disco/linux.config
> > @@ -95,10 +95,6 @@ CONFIG_STM32_MDMA=y
> > CONFIG_SYNC_FILE=y
> > # CONFIG_VIRTIO_MENU is not set
> > # CONFIG_VHOST_MENU is not set
> > -CONFIG_IIO=y
> > -CONFIG_IIO_BUFFER=y
> > -CONFIG_IIO_TRIGGERED_BUFFER=y
> > -CONFIG_IIO_STM32_TIMER_TRIGGER=y
> > # CONFIG_FILE_LOCKING is not set
> > # CONFIG_DNOTIFY is not set
> > # CONFIG_INOTIFY_USER is not set
> > diff --git a/configs/stm32f429_disco_xip_defconfig b/configs/stm32f429_disco_xip_defconfig
> > index 872e4b6a30..1aea741f7e 100644
> > --- a/configs/stm32f429_disco_xip_defconfig
> > +++ b/configs/stm32f429_disco_xip_defconfig
> > @@ -6,7 +6,7 @@ BR2_ENABLE_LTO=y
> > BR2_ROOTFS_POST_BUILD_SCRIPT="board/stmicroelectronics/common/stm32f4xx/stm32-post-build.sh"
> > BR2_LINUX_KERNEL=y
> > BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> > -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.1.10"
> > +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.1.27"
> > BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> > BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/stmicroelectronics/stm32f429-disco/linux.config"
> > BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y
> > --
> > 2.34.1
> >
>
>
> --
>
> Dario Binacchi
>
> Senior Embedded Linux Developer
>
> dario.binacchi@amarulasolutions.com
>
> __________________________________
>
>
> Amarula Solutions SRL
>
> Via Le Canevare 30, 31100 Treviso, Veneto, IT
>
> T. +39 042 243 5310
> info@amarulasolutions.com
>
> www.amarulasolutions.com
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-05-07 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 16:26 [Buildroot] [PATCH] configs/stm32f429_disco_xip_defconfig: fix runtime error due to low ram space and bump to linux version 6.1.27 Giulio Benetti
2023-05-06 14:21 ` Dario Binacchi
2023-05-07 12:48 ` Yann E. MORIN [this message]
2023-05-07 12:52 ` Giulio Benetti
2023-05-07 12:46 ` Yann E. MORIN
2023-06-05 20:08 ` Peter Korsgaard
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=20230507124829.GR252090@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=christophe.priouzeau@foss.st.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=giulio.benetti@benettiengineering.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