Uclinux-2008r1-rc8 (bf561) to VDSP5 transplantation (in): Start_kernel

After the Head.s initialization is complete, it jumps to the Start_kernel function to continue, as follows:

JUMP.L _start_kernel;

The realization of Start_kernel in INIT/MAIN.C

asmlinkage void __init start_kernel (void)

This marks the start of the first phase of the end of the second phase of the beginning. But in VDSP, when you start debugging, the default stops at the first statement of the main function, so in order to satisfy VDSP's self-righteous, we change this jump to the main function and call Start_kernel in the main function:

JUMP.L _main;

and the main function becomes:

#include <config.h>
#include <linux/types.h>
#include <linux/module.h>
#include <linux/proc_fs.h>
#include <linux/kernel.h>
#include <linux/syscalls.h>
#include <linux/string.h>
#include <linux/ctype.h>
/*****************************************************************************
* Core A
* coreA.c
*****************************************************************************/

asmlinkage void __init main( void )
{
/* The default startup code does not include any functionality to allow core
A to enable core B. A convenient way to enable core B is to use the
'adi_core_b_enable()' function. */
//adi_core_b_enable();

/* Begin adding your custom code here */
start_kernel();
}

Since Start_kernel becomes a function call here, it needs to change its declaration (include/linux/start_kernel.h) to read:

extern void __init start_kernel (void);

At the same time, change the implementation in INIT/MAIN.C to:

void __init start_kernel(void)
…