From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] firefly_rk3288_demo_defconfig: increase ext2 filesystem size
Date: Fri, 14 Apr 2017 23:26:05 +0200 [thread overview]
Message-ID: <20170414212606.13819-2-arnout@mind.be> (raw)
In-Reply-To: <20170414212606.13819-1-arnout@mind.be>
Since commit c6bca8cef0 removed autocalculation of the ext2 filesystem
size, the default size is now set to 60MB. However, this is too small
for firefly_rk3288_demo_defconfig. Indeed, the ext2 filesystem contains
the mali blobk (90MB) and Qt5 (14MB), totalling to 125MB.
This is a bit too small to fit comfortably on a 128M flash driver, so
increase the size to 250000K (245MB).
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
configs/firefly_rk3288_demo_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/firefly_rk3288_demo_defconfig b/configs/firefly_rk3288_demo_defconfig
index 7dadc6bc9a..c2de701934 100644
--- a/configs/firefly_rk3288_demo_defconfig
+++ b/configs/firefly_rk3288_demo_defconfig
@@ -26,6 +26,7 @@ BR2_PACKAGE_QT5BASE_EGLFS=y
BR2_PACKAGE_MALI_T76X=y
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
+BR2_TARGET_ROOTFS_EXT2_BLOCKS=250000
# BR2_TARGET_ROOTFS_TAR is not set
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
--
2.11.0
next prev parent reply other threads:[~2017-04-14 21:26 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 ` Arnout Vandecappelle [this message]
2017-04-14 21:26 ` [Buildroot] [PATCH 3/3] at91sam9x5ek_mmc_dev_defconfig: " Arnout Vandecappelle
2017-04-15 8:42 ` [Buildroot] [PATCH 1/3] pc_x86_64_bios_defconfig: " Thomas Petazzoni
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=20170414212606.13819-2-arnout@mind.be \
--to=arnout@mind.be \
--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 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.