Re: finding who call all __init functions

2020-07-07 Thread John Paul Adrian Glaubitz
On 7/7/20 1:55 PM, Giuseppe Sacco wrote: >> Why aren't you bisecting the kernel using git so you find the actual >> commit that broke the build? This way you will find the problem much >> quicker. > > This is a possibility, but I was unaware that the bisect works between > branches (5.4 and 5.6).

Re: finding who call all __init functions

2020-07-07 Thread Giuseppe Sacco
Hello Adrian Il giorno mar, 07/07/2020 alle 12.30 +0200, John Paul Adrian Glaubitz ha scritto: > Hi Guiseppe! > On 7/7/20 11:54 AM, Giuseppe Sacco wrote [...] > > I would like to start knowing what is called after the cpufreq. How > > do I find it? I know that drivers/cpufreq/pmac32-cpufreq.c has

Re: Debian live

2020-07-07 Thread Steffen Möller
That - and for ARM as well. Would be a good chance to attract more users, indeed. On 07.07.20 12:38, Jeroen Diederen wrote: Hi! Do you guys know if it is possible to create live installer images from a working Debian PowerpPC system? I know debian-live is only for i386 and amd64. Maybe there

Debian live

2020-07-07 Thread Jeroen Diederen
Hi! Do you guys know if it is possible to create live installer images from a working Debian PowerpPC system? I know debian-live is only for i386 and amd64. Maybe there are other unofficial ways to achieve this? Documentation somewhere? What I want to achieve is create a live iso from a

Re: finding who call all __init functions

2020-07-07 Thread John Paul Adrian Glaubitz
Hi Guiseppe! On 7/7/20 11:54 AM, Giuseppe Sacco wrote: > Now, I would like to better follow the boot process, looking for what > is done after the cpufreq driver setup. > I cannot use the netconsole since the ethernet driver is not yet loaded > when the boot process hangs. I already created a

finding who call all __init functions

2020-07-07 Thread Giuseppe Sacco
Hello, I am still investigating the problem about kernel not booting on powerbook. I compiled many kernel versions and found the problem starts with 5.6 since 5.4.50 boots correctly. Now, I would like to better follow the boot process, looking for what is done after the cpufreq driver setup. I