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

[H. Nikolaus Schaller]

> Am 28.06.2019 um 19:15 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> On Thu, 27 Jun 2019 19:42:32 +0200
> Andreas Kemnade <andreas at kemnade.info> wrote:
> 
>> On Thu, 27 Jun 2019 18:34:29 +0200
>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>> 
>>>> Am 27.06.2019 um 18:20 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
>>>> 
>>>> Hi Andreas,
>>>> 
>>>>> Am 27.06.2019 um 18:09 schrieb Andreas Kemnade <andreas at kemnade.info>:
>>>>> 
>>>>> Hi Nikolaus,
>>>>> 
>>>>> On Thu, 27 Jun 2019 15:59:11 +0200
>>>>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>>>>> 
>>>>>> Hi,
>>>>>> maybe some reader here remembers better than me how to build
>>>>>> the android compatible kernels for LetuxOS Replicant.
>>>>>> 
>>>>>> Our LetuxOS Replicant 4.2 image
>>>>>> 
>>>>>> 	http://download.goldelico.com/letux-replicant/4.2/  (File: latest-replicant.tbz)
>>>>>> 
>>>>> 
>>>>> hmm, there is:
>>>>> http://download.goldelico.com/letux-replicant/4.2/20170423-kernel-4.10-replicant.tbz    
>>>> 
>>>> Yes... I just found it. I'm getting old :)
>>>> 
>>>> Unfortunately that one boots, shows the red Android but then ended in a kernel panic
>>>> for some iio locking.
>>>> 
>>>> I also tried the same with 
>>>> 
>>>> 20170423-kernel-4.10+smshack-replicant.tbz
>>>> 
>>>> and it also panics (attached).    
>>> 
>>> 20160626-kernel-4.6.tbz seems to boot and without NAND ECC reports!
>>> 
>> but probably without correct sound and support for newer modem fw. I
>> think I started on 4.9 or 4.10 with the gta04a5.
>> 
> and wifi is fixed in
> http://projects.goldelico.com/p/gta04-replicant-device/source/commit/b08e242fbd86838e3480316225d26da5c43da66b/

Good to know!

I don't know from which manifest the latest binary .tbz was built...
So it may or may not include this patch.

But: this affects the binary bootargs.scr, doesn't it?

IMHO there is no bootargs.scr in the .tbz but I have to scan my µSD.

It adds firmware_class.path=/system/vendor/firmware/

So a better strategy would be to add this to the CONFIG_CMDLINE?

BR,
Nikolaus