Build kernel modules and run it on L4linux
doebel at os.inf.tu-dresden.de
Tue Feb 18 16:01:33 CET 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 18.02.2014 15:43, Irvanda Kurniadi wrote:
> On Tue, Feb 18, 2014 at 11:10 PM, Björn Döbel
> <doebel at os.inf.tu-dresden.de>wrote:
>>> Yes I did. I just checked the .config file # Stub drivers
>> Are you getting any messages about a missing file during Linux
>> bootup? For the file to be available through l4bdds it needs to
>> be passed as a module in the respective menu.lst entry.
> There was no message about missing file. But I didn't put any
> addition line inside the modules.list entry. I don't know whether
> this is the cause of the problem.
Yes it was, but in this case there should be a warning from L4BDDS
that it could not find the file rom/hello.ko somewhere on the serial line.
> But, wait...
>>> 2. I mounted my L4linux Ramdisk and copied my hello.ko into
>>> the Ramdisk
>> if you already copied hello.ko to the ramdisk, there is no need
>> to add it through l4bdds. The file is already there and all you
>> need to do is "insmod hello.ko"?
> When I tried to insmod hello.ko, I got error message: Invalid
> module format So btw, if my kernel module has been placed inside
> the Ramdisk, I don't need to use the l4bdds? Because I just
> followed the instruction before and don't know what to do with that
> kernel module file.
The exercise slides say you have two options: Either you mount the
ramdisk as root and put your file there. If this is impossible because
you cannot be root on your machine, you will need to circumvent this.
This is where the l4bdds solution comes into play.
In your case, the module seems to be available, there's just something
wrong with it. When you compiled the module, did you configure the
correct L4Linux build directory in the Makefile?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the l4-hackers