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

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

[Alberto Merciai]

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?

Regards,
Alberto

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

[Krzysztof Kozlowski]

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

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

[Alberto Merciai]

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

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

[Krzysztof Kozlowski]

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

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

[Alberto Merciai]

On Mon, Mar 17, 2025 at 07:12:55PM +0100, Krzysztof Kozlowski wrote:
> 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.
Thanks a lot, I was not aware of that.
Do you have any reference?

> > 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.
Let's proceed in that way :)

> > 
> > 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.
Cool! Now is clear.

> Best regards,
> Krzysztof

Thanks,
Alberto

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

[Krzysztof Kozlowski]

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

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

[Alberto Merciai]

On Mon, Mar 17, 2025 at 08:14:30PM +0100, Krzysztof Kozlowski wrote:
> 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
Really appreciate, Thanks a lot!