My point was after running make menuconfig you can compare the config
file for anything that might have changed since the configuration file
has a habit of changing as config options in the kernel change also.
Haven though about it you could drop the original somewhere then copy
it into the new ke
basti wrote:
> i have done make menuconfig and / or make dist-clean and so on.
> build the kernel does not seem the problem. it looks like rpi4 cant boot
> this. but i have no rpi3 at the moment to test if it runs on it.
>
> some days ago i read on a place i cant remember that the boot process on
On 20.12.19 20:41, mick crane wrote:
> On 2019-12-20 19:28, deloptes wrote:
>> Nigel Sollars wrote:
>>
>>> You might want to run make menuconfig after copying the config ..
>>> perhaps do the same with the 4.19 kernel also and do a compare of
>>> 'what is' and 'what is not' there in the 5.5 perhaps
On 2019-12-20 19:28, deloptes wrote:
Nigel Sollars wrote:
You might want to run make menuconfig after copying the config ..
perhaps do the same with the 4.19 kernel also and do a compare of
'what is' and 'what is not' there in the 5.5 perhaps things have been
moved around a bit in the kconfig s
Nigel Sollars wrote:
> You might want to run make menuconfig after copying the config ..
> perhaps do the same with the 4.19 kernel also and do a compare of
> 'what is' and 'what is not' there in the 5.5 perhaps things have been
> moved around a bit in the kconfig stuff.
>
Not sure if this is st
You might want to run make menuconfig after copying the config ..
perhaps do the same with the 4.19 kernel also and do a compare of
'what is' and 'what is not' there in the 5.5 perhaps things have been
moved around a bit in the kconfig stuff.
5.5 iirc actually adds new stuff for rpi4 so it does se
6 matches
Mail list logo
