From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Aleksandr Makarov <aleksandr.o.makarov@gmail.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Suniel Mahesh <sunil@amarulasolutions.com>,
Jagan Teki <jagan@amarulasolutions.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] board/pine64/rockpro64/linux.fragment: integrate stmmac driver
Date: Tue, 9 Jul 2024 22:30:35 +0200 [thread overview]
Message-ID: <20240709223035.06d08008@windsurf> (raw)
In-Reply-To: <20240426184732.1390508-1-aleksandr.o.makarov@gmail.com>
On Fri, 26 Apr 2024 21:47:32 +0300
Aleksandr Makarov <aleksandr.o.makarov@gmail.com> wrote:
> Currently, the stmmac driver is configured as a module in the defconfig, which
> means that the network functionality is not available until the driver module
> is manually inserted.
>
> Use extra config fragment to integrate it directly into the kernel, ensuring that network
> functionality is available immediately upon boot.
>
> Signed-off-by: Aleksandr Makarov <aleksandr.o.makarov@gmail.com>
> ---
> board/pine64/rockpro64/linux.fragment | 3 +++
> configs/rockpro64_defconfig | 1 +
> 2 files changed, 4 insertions(+)
> create mode 100644 board/pine64/rockpro64/linux.fragment
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-09 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 18:47 [Buildroot] [PATCH 1/1] board/pine64/rockpro64/linux.fragment: integrate stmmac driver Aleksandr Makarov
2024-07-09 20:30 ` Thomas Petazzoni via buildroot [this message]
2024-07-11 21:26 ` Peter Korsgaard
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=20240709223035.06d08008@windsurf \
--to=buildroot@buildroot.org \
--cc=aleksandr.o.makarov@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=jagan@amarulasolutions.com \
--cc=sunil@amarulasolutions.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