From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] pc_x86_64_bios_defconfig: increase ext2 filesystem size
Date: Sat, 15 Apr 2017 10:42:05 +0200 [thread overview]
Message-ID: <20170415104205.6aef1b2e@free-electrons.com> (raw)
In-Reply-To: <20170414212606.13819-1-arnout@mind.be>
Hello,
On Fri, 14 Apr 2017 23:26:04 +0200, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Since commit c6bca8cef0 removed autocalculation of the ext2 filesystem
> size, the default size is now set to 60MB. However, this is too small
> for pc_x86_64_bios_defconfig. Indeed, the ext2 filesystem contains the
> kernel (4MB), the wireless modules (4MB), all firmware for wireless
> modules (40MB), and the wifi userspace (9MB) and the udev hwdb (5MB)
> which brings the total to 70MB.
>
> Increase the filesystem size to 120000K, which is a nice and round
> number and leaves enough space for overhead on a 128MB flash drive.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> configs/pc_x86_64_bios_defconfig | 1 +
> 1 file changed, 1 insertion(+)
I've applied all three to master, thanks! For PATCH 2/3, it is somewhat
surprising that the Mali blob takes as much as 90 MB, but that's a
separate issue.
If you could resync the Gitlab mirror so that tomorrow morning build of
all defconfigs uses the latest updates, it would be nice.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-15 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 21:26 [Buildroot] [PATCH 1/3] pc_x86_64_bios_defconfig: increase ext2 filesystem size Arnout Vandecappelle
2017-04-14 21:26 ` [Buildroot] [PATCH 2/3] firefly_rk3288_demo_defconfig: " Arnout Vandecappelle
2017-04-14 21:26 ` [Buildroot] [PATCH 3/3] at91sam9x5ek_mmc_dev_defconfig: " Arnout Vandecappelle
2017-04-15 8:42 ` Thomas Petazzoni [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=20170415104205.6aef1b2e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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