linux-kernel - Re: OCOTP and DWMAC builtin modules are needed for imx93-11x11-evk kernel dev via TFTP and NFS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z9hkDqcKG1xOmIB5@alb3rt0-ThinkPad-P15-Gen-1>
Date: Mon, 17 Mar 2025 19:03:58 +0100
From: Alberto Merciai <alb3rt0.m3rciai@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: shawnguo@...nel.org, linux-kernel@...r.kernel.org, imx@...ts.linux.dev,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: OCOTP and DWMAC builtin modules are needed for imx93-11x11-evk
 kernel dev via TFTP and NFS

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
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:
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?

To be honest I was expecting to have a builtin driver for eth by
default, so that NFS and TFTP can be turned on without caring about the rest.
But for sure I'm missing something  there :)

Thanks,
Alberto