Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→History
|2.0.1
|Sep 2017
|[[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_2.0.1.2F2.0.2.2F2.0.3|XUELK 2.0.1]]
|Update for new XUELK release
|-
|2.0.2
|Feb 2018
|[[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_2.0.1.2F2.0.2.2F2.0.3|XUELK 2.0.2]]
|Add kernel modules documentation
|-
|2.0.3
|Jan 2019
|[[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_2.0.1.2F2.0.2.2F2.0.3|XUELK 2.0.3]]
|Add support for NOR ISSY
|}
|-
! stable tag
| xuelk-2.0.13
|}
</pre>
Usually , kernel modules are installed with <code>make modules_install</code> command, but this install method installs the modules into the <code>/lib/modules</code> directory of you MVM, which is not what you want. A better way to deploy kernel modules while cross-compiling is
* generate a <code>.tar.gz</code> archive
* install this archive into the target root file system
User can create such an archive , for example , using the following commands:
<pre class="workstation-terminal">
Now copy <code>modules.tar.gz</code> into the target root file system and install them as root with the following command
<pre class="boardworkstation-terminal">
tar xvzf modules.tar.gz -C /
</pre>
