[Letux-kernel] How to build LetuxOS Android Kernel for LetuxOS Replicant 4.2?

[H. Nikolaus Schaller]

> Am 28.06.2019 um 19:39 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> On Fri, 28 Jun 2019 19:19:13 +0200
> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
> 
>> Hi,
>> 
>>> Am 28.06.2019 um 19:01 schrieb Andreas Kemnade <andreas at kemnade.info>:
>>> 
>>> On Fri, 28 Jun 2019 18:41:45 +0200
>>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>>> 
>>> [...]  
>>>> What does this mean?
>>>> 
>>>> * kernel can be built outside of Replicant build system
>>>> * uImage can simply be patched over to /boot/uImage  
>>> 
>>> well, that is obvious, because it can be loaded by 
>>> ordinary uboot.  
>> 
>> Well, not completely. It could have been that it needs some other tweaks.
>> 
>>> 
>>>> * kernel modules are built differently by the Replicant build system or post-processed
>>>> * and I have not found where this is done...
>>>> 
>>>> So if we can find the post-processing script that prepares the kernel modules to /system/lib/modules
>>>> we can do the same outside of the Replicant build system.
>>>> 
>>> after make modules_install to somewhere
>>> a oneliner like:
>>> 
>>> find -name "*.ko" -exec mv \{\} /path/to/system/lib/modules \;  
>> 
>> That is what I had tried first but it did not load any module...
>> Maybe it needs a special depmod to be run.
>> 
> and simple insmod calls do result in what?

I loads the module given. But kernel starts with empty module
list. Therefore we have neither omapdrm not panel driver etc.

> simply use adb shell
> or call a shell via the init kernel commandline?
> and try to insmod from there. We manually load modules there in
> the init scripts and the android kernels have their own config.

Ah, ok. Maybe the init script should simply load the modules a modern
kernel needs instead of loading them from device tree?

On the other hand I have seen some patches by Lukas to make modprobe
work.

> 
> I have to bring back my memories for these things.

Same for me :)

> I remember
> I was the last one working on 4.2.

Unfortunately there seem to be no other working binaries around
and we have no maintainer...

BR,
Nikolaus