Changes between Version 25 and Version 26 of venice/bsp

Timestamp:

02/23/2024 12:40:04 AM (9 months ago)

Author:

Samuel Lee

Comment:

--

venice/bsp

@@ -255 +255 @@
 }}}
   - Note that some out-of-tree kernel modules do not follow the suggested Makefile standards and may need to be modified to use the CROSS_COMPILE prefix and/or specify the kernel directory (as opposed to the above example where you do a make in the linux dir and set M to the path of your module)
+
+[=#modules]
+== Building External or Out-of-Tree Kernel Modules
+
+Gateworks Venice BSP now creates images that have built in support for building external or out-of-tree kernel modules on a target board, allowing users to extend the functionality of the kernel with custom or third-party modules. Below are some examples demonstrating how to build and install external modules on a one of our Venice boards:
+
+Before building any external kernel modules, it's essential to ensure your system has necessary dependencies installed. We recommend starting with an update of package lists followed by the installation of essential tools. Run the following commands:
+{{{#!bash
+apt update
+apt install -y build-essential git bc file
+}}}
+
+{{{#!bash
+cryptodev-linux:
+                        git clone http://github.com/cryptodev-linux/cryptodev-linux
+                        cd cryptodev-linux
+                        make && make modules_install
+                        modprobe cryptodev
+
+nrc7292 (mac80211):
+                        git clone http://github.com/Gateworks/nrc7292
+                        cd nrc7292/package/src/nrc/
+                        make && make modules_install
+                        modprobe nrc
+}}}
+
+These examples illustrate the process of building and installing external kernel modules. Users can adapt these instructions for other modules as needed, ensuring that dependencies are met and the module is properly installed and loaded into the kernel.
+
+It's important to note that while many out-of-tree kernel modules follow standard Makefile conventions and can be built and installed using a simple 'make && make modules_install' command sequence, some modules may not adhere to these conventions.
+
+These non-standard modules may require modifications to their Makefiles or build processes to ensure compatibility with the standard build procedure. In such cases, it's advisable to consult the module's documentation or source repository for specific instructions on building and installing the module.
+
+Always verify the requirements and instructions provided by the module's developers to ensure successful integration with your kernel environment.