michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Eliminate VxMicro branding in kernel code

Browse source 
Eliminates references to the obsolete OS name. In most cases the
name is simply removed, as it isn't necessary.

Change-Id: I32f9e7390e436aec008a9454b72657e129d65152
Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
This commit is contained in:
Allan Stephens 2015-06-05 10:19:43 -04:00 • committed by Anas Nashif
commit 5189844df5
39 changed files with 85 additions and 88 deletions
Download patch file Download diff file Expand all files Collapse all files

2
arch/arm/core/basepri.s
View file

@ -34,7 +34,7 @@
DESCRIPTION
Provide irq_lock() and irq_unlock() via the BASEPRI register. This
allows locking up to a certain interrupt priority. VxMicro locks out priorities
allows locking up to a certain interrupt priority. Kernel locks out priorities
2 and lower (higher numbered priorities), in essence leaving priorities 0 and 1
unlocked. This achieves two purposes:

2
arch/arm/core/exc_exit.s
View file

@ -66,7 +66,7 @@ GDATA(_nanokernel)
* _IntExit - kernel housekeeping when exiting interrupt handler installed
* directly in vector table
*
* VxMicro allows installing interrupt handlers (ISRs) directly into the vector
* Kernel allows installing interrupt handlers (ISRs) directly into the vector
* table to get the lowest interrupt latency possible. This allows the ISR to be
* invoked directly without going through a software interrupt table. However,
* upon exiting the ISR, some kernel work must still be performed, namely

4
arch/arm/core/gdb_stub.s
View file

@ -134,8 +134,8 @@ SECTION_FUNC(TEXT, _GdbStubExcExit)
* _irq_vector_table_entry_with_gdb_stub - stub for ISRs installed directly in
* vector table
*
* VxMicro on Cortex-M3/4 allows users to configure the kernel such that
* ISRs are installed directly in the vector table for maximum efficiency.
* The kernel on Cortex-M3/4 can be configured so that ISRs
* are installed directly in the vector table for maximum efficiency.
*
* When OS-awareness is enabled, a stub must be inserted to invoke
* _GdbStubExcEntry() before the user ISR runs, to save the current task's