From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Javad Rahimipetroudi <javad321javad@gmail.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/7] configs/pine64_defconfig: add dynamic mdev To add networking support, dynamic mdev is required to load network drivers.
Date: Sat, 4 Nov 2023 14:38:11 +0100 [thread overview]
Message-ID: <20231104143811.0d9ba0f3@windsurf> (raw)
In-Reply-To: <20231104072458.7369-4-javad321javad@gmail.com>
Hello,
The commit title is too long.
On Sat, 4 Nov 2023 10:54:55 +0330
Javad Rahimipetroudi <javad321javad@gmail.com> wrote:
> Signed-off-by: Javad Rahimipetroudi <javad321javad@gmail.com>
> ---
> configs/pine64_defconfig | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/configs/pine64_defconfig b/configs/pine64_defconfig
> index b567462f5d..5cb4b4a0b5 100644
> --- a/configs/pine64_defconfig
> +++ b/configs/pine64_defconfig
> @@ -42,9 +42,13 @@ BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
>
> # Filesystem
> BR2_TARGET_GENERIC_ISSUE="Welcome to PINE64"
> +BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
> +BR2_SYSTEM_DHCP="eth0"
> +
> BR2_TARGET_ROOTFS_EXT2=y
> BR2_TARGET_ROOTFS_EXT2_4=y
> -BR2_PACKAGE_HOST_DOSFSTOOLS=y
Why are you removing this package?
> +BR2_TARGET_ROOTFS_EXT2_SIZE="128M"
This is not explained in the commit log. Why does the size needs to be
increased? Is it because the Linux 6.1 kernel is bigger, and has more
kernel modules? If so, this change should be together with the kernel
update.
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
next prev parent reply other threads:[~2023-11-04 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 7:24 [Buildroot] [PATCH 1/7] configs/pine64_defconfig: bump Linux version to 6.1 Linux Kernel and Header version upgraded to 6.1.50 LTS Javad Rahimipetroudi
2023-11-04 7:24 ` [Buildroot] [PATCH 2/7] configs/pine64_defconfig: bump ATF version to v2.9 Javad Rahimipetroudi
2023-11-04 7:24 ` [Buildroot] [PATCH 3/7] configs/pine64_defconfig: bump Uboot version to 2023.04 Javad Rahimipetroudi
2023-11-04 13:37 ` Thomas Petazzoni via buildroot
2023-11-04 7:24 ` [Buildroot] [PATCH 4/7] configs/pine64_defconfig: add dynamic mdev To add networking support, dynamic mdev is required to load network drivers Javad Rahimipetroudi
2023-11-04 13:38 ` Thomas Petazzoni via buildroot [this message]
2023-11-04 7:24 ` [Buildroot] [PATCH 5/7] configs/pine64_defconfig: remove unnecessary configs Javad Rahimipetroudi
2023-11-04 7:24 ` [Buildroot] [PATCH 6/7] board/pine64/genimage.cfg: rename uboot bin image The generated image name modified according to uboot output Javad Rahimipetroudi
2023-11-04 13:38 ` Thomas Petazzoni via buildroot
2023-11-04 7:24 ` [Buildroot] [PATCH 7/7] board/pine64/genimage.cfg: remove unnecessary partition for itb For minimal booting, uboot.itf is no longer required, so the correspondig partition deleted Javad Rahimipetroudi
2023-11-04 13:40 ` Thomas Petazzoni via buildroot
2023-11-04 13:50 ` Javad Rahimipetroudi
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=20231104143811.0d9ba0f3@windsurf \
--to=buildroot@buildroot.org \
--cc=jagan@amarulasolutions.com \
--cc=javad321javad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox