[Letux-kernel] depmod for replicant modules

[H. Nikolaus Schaller]

> Am 29.06.2019 um 17:29 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> Hi,
> 
> I found some dirty way to create a modules.dep file in finished
> replicant images.
> On a system with depmod available.
> - create a directory /some_tmp_dir/lib/modules/
> ln -s /path/to/replicant/system/lib/modules /some_tmp_dir/lib_modules/4.17
> depmod -b /some_tmp_dir 4.17

yes, that is the principle described by

https://android.googlesource.com/device/asus/fugu/+/b01b7fd/AndroidKernel.mk#102

I had tried it but maybe got the symlink wrong.

What I don't get with these paths is what is constant file names and what is system-dependent.
For example why do you use /some_tmp_dir/lib_modules/4.17 and not /some_tmp_dir/lib/modules/4.17

Could you please rewrite as something like

KERNEL_MODULES_FROM_BUILD=...
TEMP_DIR=/tmp/build-$$
ln -s $KERNEL_MODULES_FROM_BUILD ... 
depmod -b ...

etc.

> 
> modprobe then works. But now we a using a lot of insmod in load_modules.sh,
> so it is not so important

Indeed. As long as the load_modules.sh is complete and loads all what is needed.

BR and thanks,
Nikolaus