Remove references to BSP from include/ directory
Removes references to obsolete BSP terminology. Where appropriate, replaces it with platform terminology. Change-Id: If38c859338c7cf0de58430336e1046b28f9e9944 Signed-off-by: Peter Mitsis <peter.mitsis@windriver.com>
This commit is contained in:
parent
771c5998e9
commit
7cbad4e7dd
4 changed files with 20 additions and 25 deletions
|
@ -32,7 +32,7 @@
|
|||
|
||||
/*
|
||||
DESCRIPTION
|
||||
Linker script for the Cortex-M3 BSPs.
|
||||
Linker script for the Cortex-M3 platform.
|
||||
*/
|
||||
|
||||
#define _LINKER
|
||||
|
@ -206,8 +206,8 @@ SECTIONS
|
|||
*(".bss.*")
|
||||
COMMON_SYMBOLS
|
||||
/*
|
||||
* BSP clears this memory in words only and doesn't clear any
|
||||
* potential left over bytes.
|
||||
* As memory is cleared in words only, it is simpler to ensure the BSS
|
||||
* section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
|
||||
*/
|
||||
__bss_end = ALIGN(4);
|
||||
} GROUP_LINK_IN(RAMABLE_REGION)
|
||||
|
|
|
@ -49,7 +49,7 @@
|
|||
|
||||
/**
|
||||
* Macro used internally by NANO_CPU_INT_REGISTER and NANO_CPU_INT_REGISTER_ASM.
|
||||
* Not meant to be used explicitly by BSP, driver or application code.
|
||||
* Not meant to be used explicitly by platform, driver or application code.
|
||||
*/
|
||||
#define MK_ISR_NAME(x) __isr__##x
|
||||
|
||||
|
@ -456,11 +456,11 @@ extern const NANO_ESF _default_esf;
|
|||
/*
|
||||
* @brief Configure an interrupt vector of the specified priority
|
||||
*
|
||||
* BSP provided routine which kernel invokes to configure an interrupt vector
|
||||
* of the specified priority; the BSP allocates an interrupt vector, programs
|
||||
* hardware to route interrupt requests on the specified irq to that vector,
|
||||
* and returns the vector number along with its associated BOI/EOI information
|
||||
*
|
||||
* This routine is invoked by the kernel to configure an interrupt vector of
|
||||
* the specified priority. To this end, it allocates an interrupt vector,
|
||||
* programs hardware to route interrupt requests on the specified irq to that
|
||||
* vector, and returns the vector number along with its associated BOI/EOI
|
||||
* information.
|
||||
*/
|
||||
extern int _SysIntVecAlloc(unsigned int irq,
|
||||
unsigned int priority,
|
||||
|
@ -472,7 +472,7 @@ extern int _SysIntVecAlloc(unsigned int irq,
|
|||
unsigned char *eoiParamRequired
|
||||
);
|
||||
|
||||
/* functions provided by the kernel for usage by the BSP's _SysIntVecAlloc() */
|
||||
/* functions provided by the kernel for usage by _SysIntVecAlloc() */
|
||||
|
||||
extern int _IntVecAlloc(unsigned int priority);
|
||||
|
||||
|
|
|
@ -33,8 +33,7 @@
|
|||
/*
|
||||
DESCRIPTION
|
||||
This script defines the memory location of the various sections that make up
|
||||
a Zephyr Kernel image. It is usable by most supported BSPs. This file is used
|
||||
by the linker.
|
||||
a Zephyr Kernel image. This file is used by the linker.
|
||||
|
||||
This script places the various sections of the image according to what features
|
||||
are enabled by the kernel's configuration options.
|
||||
|
@ -180,11 +179,8 @@ SECTIONS
|
|||
*(".bss.*")
|
||||
COMMON_SYMBOLS
|
||||
/*
|
||||
* Ensure the true BSS section ends on a 4 byte boundary. When the BSP
|
||||
* clears this memory it is done in words only and doesn't clear any
|
||||
* potential left over bytes. Rather than adding code to do this it is
|
||||
* simpler to pad out the end of the section. We only waste a maximum
|
||||
* of 3 bytes.
|
||||
* As memory is cleared in words only, it is simpler to ensure the BSS
|
||||
* section ends on a 4 byte boundary. This wastes a maximum of 3 bytes.
|
||||
*/
|
||||
. = ALIGN(4);
|
||||
__bss_end = .;
|
||||
|
|
|
@ -35,12 +35,11 @@ DESCRIPTION
|
|||
This header file declares prototypes for the kernel's random number generator
|
||||
APIs.
|
||||
|
||||
Typically a BSP should enable the hidden CUSTOM_RANDOM_GENERATOR configuration
|
||||
option and provide its the implementations for sys_rand32_init() and
|
||||
sys_rand32_get().
|
||||
However, if it does not do so a project requiring random numbers must implement
|
||||
these routines, or (for testing purposes only) enable the TEST_RANDOM_GENERATOR
|
||||
configuration option.
|
||||
Typically, a platform enables the hidden CUSTOM_RANDOM_GENERATOR configuration
|
||||
option and provide its own driver that implements both sys_rand32_init() and
|
||||
sys_rand32_get(). If it does not do this, then for projects that require random
|
||||
numbers, the project must either implement those routines, or (for testing
|
||||
purposes only) enable the TEST_RANDOM_GENERATOR configuration option.
|
||||
*/
|
||||
|
||||
#ifndef __INCrand32h
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue