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 19:12:55 +0100 [thread overview]
Message-ID: <ef163f08-35f9-4d1d-8082-c826c6cd0aa0@linaro.org> (raw)
In-Reply-To: <Z9hkDqcKG1xOmIB5@alb3rt0-ThinkPad-P15-Gen-1>
On 17/03/2025 19:03, Alberto Merciai wrote:
> On Mon, Mar 17, 2025 at 05:07:26PM +0100, Krzysztof Kozlowski wrote:
>> On 17/03/2025 09:47, Alberto Merciai wrote:
>>> While playing with linux-next and imx93-11x11-evk via NFS and TFTP
>>> I found that the dwmac-imx, nvmem-imx-ocotp-ele drivers by default are
>>> not builtin then the I was not able to reach userland.
>>>
>>> The following configs were needed to reach my goal:
>>> CONFIG_DWMAC_IMX8=y
>>> CONFIG_STMMAC_ETH=y
>>> CONFIG_NVMEM_IMX_OCOTP_ELE=y
>>>
>>> is that something expected?
>>
>> You mean they are disabled or you just did not put them inside your
>> initramfs?
>>
>> Best regards,
>> Krzysztof
>
> Hello,
>
> 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.
> setenv loaddtb "tftp 0x80400000 imx93-11x11-evk.dtb"
> setenv loadkernel "tftp 0x83000000 Image"
> setenv netargs "setenv bootargs console=ttyLP0,115200 root=/dev/nfs ip=dhcp nfsroot=192.168.1.3:/tftp/root,v3,tcp"
> setenv bootcmd "run loaddtb; run loadkernel; run netargs; booti 0x83000000 - 0x80400000;"
>
> Do you think that initramfs can solve that?
Yes, that's the entire point of initramfs.
>
> To be honest I was expecting to have a builtin driver for eth by
No, why? We built as much as possible as modules in defconfig. Otherwise
it would be impossible to actually boot that image because several arm64
platforms have limitations of boot partition size.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-17 18:15 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 [this message]
2025-03-17 18:59 ` Alberto Merciai
2025-03-17 19:14 ` Krzysztof Kozlowski
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=ef163f08-35f9-4d1d-8082-c826c6cd0aa0@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