From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roberto Medina <robertoxmed@gmail.com>
Cc: kilian.zinnecker@mail.de, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] configs/roc_rk3399_pc: Bring back and update the configuration for the rockchip rk3399 built by firefly.
Date: Sat, 12 Aug 2023 00:29:02 +0200 [thread overview]
Message-ID: <20230812002902.5ce271b0@windsurf> (raw)
In-Reply-To: <88906c88-9597-4f1d-a5d2-244337ac0fdf@gmail.com>
On Fri, 11 Aug 2023 18:28:43 +0200
Roberto Medina <robertoxmed@gmail.com> wrote:
> Thank you for your reviews. I submitted a v3 for review but I will
> answer the following here as well.
>
> On 8/8/23 23:06, Thomas Petazzoni wrote:
> > Why this custom size rather than leaving the default?
>
> If I leave this value as default I will get the following error:
>
> Copying files into the device: __populate_fs: Could not alocate block in
> ext2 filesystem while writing file "stm_core.ko".
This indeed means that what's on the rootfs exceeds the default
ext2/ext4 filesystem image size, so increasing it is fine.
Thanks,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-11 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 21:21 [Buildroot] [PATCH v2 0/1] configs/roc_rk3399_pc: Bring back and update the Roberto Medina
2023-07-10 21:21 ` [Buildroot] [PATCH v2 1/1] configs/roc_rk3399_pc: Bring back and update the configuration for the rockchip rk3399 built by firefly Roberto Medina
2023-07-14 18:08 ` Kilian Zinnecker via buildroot
2023-07-24 11:01 ` Roberto Medina
2023-07-25 8:21 ` Da Xue
2023-08-08 21:06 ` Thomas Petazzoni via buildroot
2023-08-11 16:28 ` Roberto Medina
2023-08-11 22:29 ` 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=20230812002902.5ce271b0@windsurf \
--to=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=robertoxmed@gmail.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 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.