Kernel Module Definition .mdef
This topic provides details about Legato AF's Kernel Module Definition file.
The .mdef files support 2 methods of building drivers within the Legato AF.
- Using
pre-built
to bundle kernel module binary files. - Using
sources
to make and bundle .c files into a kernel object.
Each method will bundle the kernel module into the system definition (when called in the .sdef) and will be installed on the target when the system is updated.
- Note
- The
.mdef must contain either a
source
or apreBuilt
section, not both.
.mdef files contain the following sections:
sources
The sources:
section specifies the path of the source code that is required to build the kernel module binary file. This will build a .ko file from the source
Building a driver using sources:
sources:{mangoh_iot.cgreen.ceeprom.c}
preBuilt
The preBuilt:
section specifies the path to the pre-built kernel module binary file. The module binary file specified must have an extension .ko.
Building a kernel module binary file from /path/to/module/hello
.ko:
{preBuilt: /path/to/kernel/module/hello.ko}
params
The optional params:
section lists all module parameters that must be provided to the insmod
command.
The following code sample will execute this command insmod <module> param1=value1 param2=value2 …
:
params:{param1 = "value1"param2 = "value2"…}
The mandatory quotes (" ") around each parameter value indicate a string type.
flags
The optional cflags:
and ldflags:
can be added to list all options that need to be passed to the compiler and linker during the driver build.
cflags:{"-I/path/to/custom/includes"}ldflags:{"-L/path/to/custom/libs"}
Copyright (C) Sierra Wireless Inc.