From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Arnout Vandecappelle <arnout@mind.be>, buildroot@buildroot.org
Cc: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
Danilo Bargen <mail@dbrgn.ch>,
Suniel Mahesh <sunil@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH] configs/roc_pc_rk3399_defconfig: expand rootfs size to 120M
Date: Mon, 14 Feb 2022 01:03:09 +0100 [thread overview]
Message-ID: <cb93cb6a-c8ae-0975-6ae0-14ad369de9e2@benettiengineering.com> (raw)
In-Reply-To: <c3a9cf08-fb79-580d-f1e6-79ef28b46263@mind.be>
Hi Arnout,
On 13/02/22 12:35, Arnout Vandecappelle wrote:
>
>
> On 02/02/2022 18:10, Giulio Benetti wrote:
>> Default 60M for rootfs are not enough and generate a build failure, so
>> let's expand rootfs size to 120M.
>
> Did you find out _why_ 64M wasn't enough for just the kernel and busybox? Is
> it because of all the stupid modules in the default arm64 defconfig? But most
> other arm64 defconfigs don't seem to need this...
It is because of modules(30M) and linux "Image", it's not compressed, so
it's 25M. So only for Linux+modules => 55M, plus the few other
stuff(Busybox+libc etc.)1M
Also, nothing changed since the beginning, so I don't know how could
this happened:
# git log --oneline configs/roc_pc_rk3399_defconfig
f51cbc33d9 configs/roc_pc_rk3399: fix U-Boot dependencies
80ae1aedcb configs/roc_rk3399_pc: new defconfig
# git log --oneline roc-rk3399-pc/
80ae1aedcb configs/roc_rk3399_pc: new defconfig
U-Boot dependencies are host dependencies, so it doesn't impact.
# git log --oneline fs/ext2:
5ece6be60b fs/ext2: fir (again) namespace for variables
db7d786140 fs/ext2: fix namespace for variables
5631c38024 fs/ext2: pass a default string to filesystem label
...
here board has been added
So it doesn't seem a ext2 problem too.
I can't understand how it could be building in the beginning.
We have 2 solutions:
- expand rootfs
- use a compressed linux Image.gz(25M => 9M), but need target testing
Honestly I don't think systems with SoCs like RK3399 have problems with
56M more, so I would go with expanding rootfs to 120M and if maintainer
in Cc wants to shrink Linux and target testing it is welcome to send a
patch.
What do you think?
Best regards
--
Giulio Benetti
Benetti Engineering sas
>>
>> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
>> ---
>> configs/roc_pc_rk3399_defconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/configs/roc_pc_rk3399_defconfig b/configs/roc_pc_rk3399_defconfig
>> index dfbc5e4f47..ae7cf19a80 100644
>> --- a/configs/roc_pc_rk3399_defconfig
>> +++ b/configs/roc_pc_rk3399_defconfig
>> @@ -45,7 +45,7 @@ BR2_TARGET_GENERIC_HOSTNAME="roc-rk3399-pc"
>> BR2_TARGET_GENERIC_ISSUE="Welcome to ROC-RK3399-PC!"
>> BR2_TARGET_ROOTFS_EXT2=y
>> BR2_TARGET_ROOTFS_EXT2_4=y
>> -BR2_TARGET_ROOTFS_EXT2_SIZE="64M"
>> +BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
>> BR2_PACKAGE_HOST_DOSFSTOOLS=y
>> BR2_PACKAGE_HOST_GENIMAGE=y
>> BR2_PACKAGE_HOST_MTOOLS=y
>
> Unrelated by this patch, but the image doesn't have a FAT partition so
> dosfstols and mtools aren't needed.
>
> Regards,
> Arnout
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-14 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 17:10 [Buildroot] [PATCH] configs/pcengines_apu2_defconfig: linux needs host libelf Giulio Benetti
2022-02-02 17:10 ` [Buildroot] [PATCH] configs/roc_pc_rk3399_defconfig: expand rootfs size to 120M Giulio Benetti
2022-02-13 11:35 ` Arnout Vandecappelle
2022-02-14 0:03 ` Giulio Benetti [this message]
2022-02-14 20:13 ` Arnout Vandecappelle
2022-02-14 20:36 ` Yann E. MORIN
2022-02-15 8:15 ` Peter Korsgaard
2022-02-14 20:56 ` Arnout Vandecappelle
2022-02-14 20:01 ` [Buildroot] [PATCH] configs/pcengines_apu2_defconfig: linux needs host libelf Arnout Vandecappelle
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=cb93cb6a-c8ae-0975-6ae0-14ad369de9e2@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=mail@dbrgn.ch \
--cc=michael@amarulasolutions.com \
--cc=sunil@amarulasolutions.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.