From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
Cc: shawnguo@kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: OCOTP and DWMAC builtin modules are needed for imx93-11x11-evk kernel dev via TFTP and NFS
Date: Mon, 17 Mar 2025 20:14:30 +0100 [thread overview]
Message-ID: <88c66c98-7ea3-4172-9c99-405fe449cc5b@linaro.org> (raw)
In-Reply-To: <Z9hxKlrrqW4QyzdJ@alb3rt0-ThinkPad-P15-Gen-1>
On 17/03/2025 19:59, Alberto Merciai wrote:
>>>
>>> By default they are enabled as external modules, then until we don't
>>
>> So everything is as expected...
>>
>>> reach userland they are not loaded thus eth and all the mechanism behind
>>> that are out.
>>>
>>> I'm not using initramfs just tftp and NFS as follows:
>>
>> All arm64 platforms are supposed to use initramfs on defconfig with
>> necessary modules.
> Thanks a lot, I was not aware of that.
> Do you have any reference?
Reference for what? initramfs?
I am using meta-qcom initramfs:
https://github.com/krzk/yocto-qcom
with copy_modules argument:
https://github.com/krzk/tools/blob/7c0d1cacad06aa0cae8c2983ae26889471a9aaa6/linux/build.sh#L543
And here is how I append stuff, but simple `cat` one cpio archive to
another cpio archive would work as well, just be sure some paths are not
symlinks (/bin /usr/bin) because then `cat` has issues:
https://github.com/krzk/tools/blob/7c0d1cacad06aa0cae8c2983ae26889471a9aaa6/linux/build.sh#L504
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-17 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 8:47 OCOTP and DWMAC builtin modules are needed for imx93-11x11-evk kernel dev via TFTP and NFS Alberto Merciai
2025-03-17 16:07 ` Krzysztof Kozlowski
2025-03-17 18:03 ` Alberto Merciai
2025-03-17 18:12 ` Krzysztof Kozlowski
2025-03-17 18:59 ` Alberto Merciai
2025-03-17 19:14 ` Krzysztof Kozlowski [this message]
2025-03-18 6:56 ` Alberto Merciai
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=88c66c98-7ea3-4172-9c99-405fe449cc5b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alb3rt0.m3rciai@gmail.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
/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