[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
slackwarearm:development_component_kmodloader [2023/08/25 16:45 (UTC)] – mozesslackwarearm:development_component_kmodloader [2023/08/27 17:35 (UTC)] (current) – mozes
Line 37: Line 37:
 <note tip>Even though the baseline set of modules isn't extensive, the generic Operating System Initial RAM Disk ('OS InitRD') and Slackware Installer contain a wide array of modules which can be loaded by the Hardware Model Loader scripts.  The Liklihood is that the modules you require may already be included, just not set/loaded.  However, if you cannot find the module(s) you require, [[https://www.linuxquestions.org/questions/slackware-arm-108/|drop a note to the Slackware ARM forum]] with the module name and Kernel ''CONFIG_'' option, the Hardware Model name and we can probably add it to the generic OS InitRD and Slackware Installer.</note> <note tip>Even though the baseline set of modules isn't extensive, the generic Operating System Initial RAM Disk ('OS InitRD') and Slackware Installer contain a wide array of modules which can be loaded by the Hardware Model Loader scripts.  The Liklihood is that the modules you require may already be included, just not set/loaded.  However, if you cannot find the module(s) you require, [[https://www.linuxquestions.org/questions/slackware-arm-108/|drop a note to the Slackware ARM forum]] with the module name and Kernel ''CONFIG_'' option, the Hardware Model name and we can probably add it to the generic OS InitRD and Slackware Installer.</note>
    
-===== Hardware Model specific modules =====+===== Hardware Model-specific modules =====
  
 In addition to the base line set of rules, particular Hardware Models will require modules unique to themselves. e.g. you won't want to load the driver for the Raspberry Pi's network interface on the RockPro64, since it will never be used.  Additionally, some modules surface error messages when loaded on Hardware Models on which the expected hardware isn't present. In addition to the base line set of rules, particular Hardware Models will require modules unique to themselves. e.g. you won't want to load the driver for the Raspberry Pi's network interface on the RockPro64, since it will never be used.  Additionally, some modules surface error messages when loaded on Hardware Models on which the expected hardware isn't present.
Line 108: Line 108:
       eth0 [e2:8d:0f:6b:b1:a2]:   dwmac_rk (up)       eth0 [e2:8d:0f:6b:b1:a2]:   dwmac_rk (up)
 </code> </code>
 +
 +== Video ==
 +
 +
 +<code>
 +root@bladswede:~/ac/source/k/scripts# for card in /dev/dri/card* ; do ./find_modules_drivers $card  | grep DRIVER= ; done
 +    DRIVER=rockchip-drm
 +    DRIVER=panfrost
 +</code>
 +
  
  

Trace:

slackwarearm:development_component_kmodloader ()