Drop mxm-mwifiex-setup recipe#998
Conversation
angolini
left a comment
There was a problem hiding this comment.
Do you know if the KERNEL_MODULE_* variables also deal with firmware?
I think I still prefer to keep this as a MACHINE_FEATURE
| KERNEL_MODULE_AUTOLOAD:imx8mm-lpddr4-evk-ebbr += "moal" | ||
| KERNEL_MODULE_PROBECONF:imx8mm-lpddr4-evk-ebbr += "moal" |
There was a problem hiding this comment.
Is there a reason to add this driver only for the ebbr variation of the board?
There was a problem hiding this comment.
Right, it shouldn't be ebbr specific.
VARIABLE:board += ""
IIRC this will also potentially cause issues with the assignment (var ?=, var:board = ""), which is why we usually just append here instead.
There was a problem hiding this comment.
Is there a reason to add this driver only for the ebbr variation of the board?
This replace the previous MACHINE_FEATURES:append:imx8mm-lpddr4-evk = " mxm-mwifiex-load" that uses the imx8mm-lpddr4-evk machine override, a few lines below there is another but now for imx8mp-lpddr4-evk.
There was a problem hiding this comment.
IIRC this will also potentially cause issues with the assignment (var ?=, var:board = ""), which is why we usually just append here instead.
Changed to use the append
There was a problem hiding this comment.
Is there a reason to add this driver only for the ebbr variation of the board?
This replace the previous
MACHINE_FEATURES:append:imx8mm-lpddr4-evk = " mxm-mwifiex-load"that uses theimx8mm-lpddr4-evkmachine override, a few lines below there is another but now forimx8mp-lpddr4-evk.
misunderstood this part and ebbr variation is my fault! now fixed
I think not, this variables is handled on
Is this configuration to auto load the kernel module still required? Why the |
|
As far as I understand, As far as I understand, moal module is a generic wifi driver, and I would say it is a common dependency for other drivers. So I understand we can configure the moal driver probe using the OE variable, but I would not remove the MACHINE_FEATURES. Are you facing some log errors due to changes in some firmware due to the latest meta-freescale bump, @quaresmajose ? |
The MACHINE_FEATURES have now all the pieces on meta-freescale and we have our adaptation in #997 so LmP is aligned. This PR is for auto load the kernel modules in this two machines, I can change it to be done with a MACHINE_FEATURES. |
|
I'm not entirely aware of the context of this PR. I thought it was only an enhancement, not a bug fix. I think the suggestion was to have the OE variables ready to load the module instead of something else. We can discuss this more offline, but I would need to understand what is happening. |
and you are right, this is a different way of doing the same thing and is not a bug. we can talk offline |
@angolini has a reason. I agree it would be better to keep a machine feature and |
| MACHINE_FEATURES:append:imx8mm-lpddr4-evk = " mxm-mwifiex-load" | ||
| KERNEL_MODULE_AUTOLOAD:append:imx8mm-lpddr4-evk = " moal" | ||
| KERNEL_MODULE_PROBECONF:append:imx8mm-lpddr4-evk = " moal" | ||
| module_conf_moal:imx8mm-lpddr4-evk = "options moal mod_para=nxp/wifi_mod_para.conf drvdbg=0x6" |
There was a problem hiding this comment.
Would be good to confirm indeed if this customization for mod_para is still needed as it seems it is not required anymore by looking at the BSP (maybe the default path it looks now is nxp/wifi_mod_para.conf?).
There was a problem hiding this comment.
And also if autoloading is still required as well, @MrCry0 should be able to confirm.
|
Convert this to WIP because the variable KERNEL_MODULE_AUTOLOAD and KERNEL_MODULE_PROBECONF in yocto needs be adapted because they use "/etc" hard-coded in kernel-module-split.bbclass and we need to have this in ${libdir} |
Use yocto variables for this propose: - KERNEL_MODULE_AUTOLOAD https://docs.yoctoproject.org/ref-manual/variables.html?highlight=kernel_module_autoload#term-KERNEL_MODULE_AUTOLOAD - KERNEL_MODULE_PROBECONF https://docs.yoctoproject.org/ref-manual/variables.html?highlight=kernel_module_autoload#term-KERNEL_MODULE_PROBECONF Signed-off-by: Jose Quaresma <[email protected]>
Signed-off-by: Jose Quaresma <[email protected]>
Signed-off-by: Jose Quaresma <[email protected]>
Use yocto variables for this propose: - KERNEL_MODULE_AUTOLOAD https://docs.yoctoproject.org/ref-manual/variables.html?highlight=kernel_module_autoload#term-KERNEL_MODULE_AUTOLOAD - KERNEL_MODULE_PROBECONF https://docs.yoctoproject.org/ref-manual/variables.html?highlight=kernel_module_autoload#term-KERNEL_MODULE_PROBECONF Signed-off-by: Jose Quaresma <[email protected]>
I have a patch prepared for oe-core so i will merge this in main-next to test |
We can use yocto variables for this propose: