From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Niklas Cassel via buildroot <buildroot@buildroot.org>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
Damien Le Moal <dlemoal@kernel.org>,
Kilian Zinnecker <kilian.zinnecker@mail.de>,
Niklas Cassel <cassel@kernel.org>
Subject: Re: [Buildroot] [PATCH 3/5] configs/rock5b: enable eudev to enable automatic module loading
Date: Tue, 3 Sep 2024 21:26:11 +0200 [thread overview]
Message-ID: <20240903212611.613c6d42@windsurf> (raw)
In-Reply-To: <20240902104433.2561797-4-niklas.cassel@wdc.com>
On Mon, 2 Sep 2024 12:44:31 +0200
Niklas Cassel via buildroot <buildroot@buildroot.org> wrote:
> From: Niklas Cassel <cassel@kernel.org>
>
> The arm64 defconfig enables both the R8169 Ethernet driver and the
> PHY_ROCKCHIP_NANENG_COMBO_PHY PHY driver as modules.
>
> Enable udev so that these modules will get automatically loaded by udev
> after the rootfs is mounted from the SD card.
>
> This way, we do not need to build these modules as built-in, and we also
> get the benefit that any device plugged in to the PCIe slot will get
> automatically loaded.
>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
I'm not sure what we want to do here, especially when this ends up
needing net.ifnames=0 that you add in PATCH 4/5.
We do have already a small number of defconfigs that enable eudev. So
far we only use net.ifnames=0 in 4 configurations.
Basically, I'm trying to make sure we remain consistent and have a
policy that applies to all defconfigs rather than ad-hoc solutions that
are different for each and every defconfig. That's why I'm a bit
reluctant with applying your patches as-is because they only solve the
specific case of this defconfig, in a specific way, without creating a
clear rule that all defconfigs meeting a specific situation should
follow.
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:[~2024-09-03 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 10:44 [Buildroot] [PATCH 0/5] rock5b additional improvements Niklas Cassel via buildroot
2024-09-02 10:44 ` [Buildroot] [PATCH 1/5] board/radxa/rock5b: use gpt partition table instead of hybrid Niklas Cassel via buildroot
2024-09-02 10:44 ` [Buildroot] [PATCH 2/5] board/radxa/rock5b: use PARTLABEL to specify rootfs Niklas Cassel via buildroot
2024-09-02 10:44 ` [Buildroot] [PATCH 3/5] configs/rock5b: enable eudev to enable automatic module loading Niklas Cassel via buildroot
2024-09-03 19:26 ` Thomas Petazzoni via buildroot [this message]
2024-09-03 19:50 ` Arnout Vandecappelle via buildroot
2024-09-03 20:06 ` Niklas Cassel via buildroot
2024-09-03 21:10 ` Arnout Vandecappelle via buildroot
2024-09-09 11:11 ` Niklas Cassel via buildroot
2024-09-03 19:56 ` Niklas Cassel via buildroot
2024-09-03 21:06 ` Arnout Vandecappelle via buildroot
2024-09-09 11:01 ` Niklas Cassel via buildroot
2024-09-02 10:44 ` [Buildroot] [PATCH 4/5] board/radxa/rock5b: do not use udev predictable NIC names Niklas Cassel via buildroot
2024-09-02 10:44 ` [Buildroot] [PATCH 5/5] configs/rock5b: enable DHCP for eth0 Niklas Cassel via buildroot
2024-09-03 19:24 ` [Buildroot] [PATCH 0/5] rock5b additional improvements Thomas Petazzoni via buildroot
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=20240903212611.613c6d42@windsurf \
--to=buildroot@buildroot.org \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=kilian.zinnecker@mail.de \
--cc=niklas.cassel@wdc.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.