patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity

Rename Zephyr OS into Zephyr Kernel

Browse source 
We are a kernel, not an OS.

Change-Id: Ib987e3e511e1bdbed6293ab5e15e598bff00b09b
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2015-06-19 21:21:48 -04:00
parent bde0949049
commit ac47c45ca0
17 changed files with 22 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Makefile
View file

@ -5,7 +5,7 @@ VERSION_REVISION = 0
VERSION_RESERVED = 0 VERSION_RESERVED = 0
PATCHLEVEL = 0 PATCHLEVEL = 0
SUBLEVEL = 0 SUBLEVEL = 0
NAME = Zephyr OS NAME = Zephyr Kernel
export SOURCE_DIR PROJECT MDEF_FILE KLIBC_DIR export SOURCE_DIR PROJECT MDEF_FILE KLIBC_DIR

2
arch/x86/crt0.S
View file

@ -31,7 +31,7 @@
*/ */
/* /*
DESCRIPTION DESCRIPTION
This module contains the initial code executed by the Zephyr OS ELF image This module contains the initial code executed by the Zephyr Kernel ELF image
after having been loaded into RAM. after having been loaded into RAM.
INTERNAL INTERNAL

2
doc/development/naming_conventions.rst
View file

@ -7,7 +7,7 @@ The Purpose of Naming Conventions
Unlike desktop operating systems, where applications are written in user-space Unlike desktop operating systems, where applications are written in user-space
and drivers are used to cross the boundary between kernel and user space, all and drivers are used to cross the boundary between kernel and user space, all
applications in the Zephyr OS are written in kernel space. These are then applications in the Zephyr Kernel are written in kernel space. These are then
linked against the kernel creating a shared and common namespace. linked against the kernel creating a shared and common namespace.
To ensure proper execution of both kernel and applications, it makes sense to To ensure proper execution of both kernel and applications, it makes sense to

2
doc/installation/installation_custom_builds.rst
View file

@ -108,7 +108,7 @@ and list the options you’ve set.
Installing a Custom QEMU for ARM Platforms Installing a Custom QEMU for ARM Platforms
============================================ ============================================
The Yocto SDK comes with a Qemu binary suitable for running sample Zephyr OS The Yocto SDK comes with a Qemu binary suitable for running sample Zephyr Kernel
applications. The steps below are only needed if you choose not to use the applications. The steps below are only needed if you choose not to use the
provided binary and use a custom built binary instead. provided binary and use a custom built binary instead.

2
doc/object/object.rst
View file

@ -2,7 +2,7 @@ Zephyr Kernel Objects
###################### ######################
Use this information to understand how the different kernel objects of Use this information to understand how the different kernel objects of
the Zephyr OS function. The purpose of this section is to help you the Zephyr Kernel function. The purpose of this section is to help you
understand the most important object of the operating system. In order understand the most important object of the operating system. In order
to help you navigate through the content, we have divided the objects to help you navigate through the content, we have divided the objects
in :ref:`basicObjects`, :ref:`nanokernelObjects` and in :ref:`basicObjects`, :ref:`nanokernelObjects` and

2
doc/object/object_basic_fibers.rst
View file

@ -92,7 +92,7 @@ computational cannot call :c:func:`fiber_yield()`.
Scheduling Fibers Scheduling Fibers
***************** *****************
The fibers in the Zephyr OS are priority-scheduled. When several fibers The fibers in the Zephyr Kernel are priority-scheduled. When several fibers
are ready to run, they run in the order of their priority. When more are ready to run, they run in the order of their priority. When more
than one fiber of the same priority is ready to run, they are ordered than one fiber of the same priority is ready to run, they are ordered
by the time that each became runnable. Each fiber runs until it is by the time that each became runnable. Each fiber runs until it is

6
doc/object/object_basic_interrupts.rst
View file

@ -89,7 +89,7 @@ the macros detailed in following table. The table lists the macros you
can use to identify and register your static ISRs into the Interrupt can use to identify and register your static ISRs into the Interrupt
Descriptor Table. The IA-32 interrupt descriptor allows for the setting Descriptor Table. The IA-32 interrupt descriptor allows for the setting
of the privilege level, DPL, at which the interrupt can be triggered. of the privilege level, DPL, at which the interrupt can be triggered.
The Zephyr OS assumes all device drivers are kernel mode (ring 0) as The Zephyr Kernel assumes all device drivers are kernel mode (ring 0) as
opposed to user-mode (ring 3). Therefore, these macros always set the opposed to user-mode (ring 3). Therefore, these macros always set the
DPL to 0. DPL to 0.
@ -186,7 +186,7 @@ The following is an example of a dynamic interrupt stub for x86:
} }
This feature is part of the enhanced security profile in Zephyr OS. This feature is part of the enhanced security profile in Zephyr Kernel.
Working with ISRs Working with ISRs
@ -330,7 +330,7 @@ The default setting of 0 disables the following interfaces:
:c:func:`task_irq_ack()` and :c:func:`task_irq_test()`. Each device has :c:func:`task_irq_ack()` and :c:func:`task_irq_test()`. Each device has
a well-known identifier in the range from 0 to *MAX_NUM_TASK_DEVS*-1. a well-known identifier in the range from 0 to *MAX_NUM_TASK_DEVS*-1.
The Zephyr OS allows kernel tasks to bind to devices at run-time by The Zephyr Kernel allows kernel tasks to bind to devices at run-time by
calling :c:func:`task_irq_alloc()`. A task may bind itself to multiple calling :c:func:`task_irq_alloc()`. A task may bind itself to multiple
devices by calling this routine multiple times but a given device can devices by calling this routine multiple times but a given device can
be bound to only a single task at any point in time. The registering be bound to only a single task at any point in time. The registering

2
doc/object/object_nanokernel.rst
View file

@ -8,7 +8,7 @@ Section Scope
This section provides an overview of the most important nanokernel This section provides an overview of the most important nanokernel
objects. The information contained here is an aid to better understand objects. The information contained here is an aid to better understand
how the Zephyr OS operates at the nanokernel level. how the Zephyr Kernel operates at the nanokernel level.
Document Format Document Format
*************** ***************

2
doc/substitutions.rst
View file

@ -1,4 +1,4 @@
.. |codename| replace:: Zephyr OS .. |codename| replace:: Zephyr Kernel
.. |PM| replace:: Hirally Rodriguez Santiago .. |PM| replace:: Hirally Rodriguez Santiago

4
include/arch/x86/linker-common-sections.h
View file

@ -33,7 +33,7 @@
/* /*
DESCRIPTION DESCRIPTION
This script defines the memory location of the various sections that make up This script defines the memory location of the various sections that make up
a Zephyr OS image. It is usable by most supported BSPs. This file is used a Zephyr Kernel image. It is usable by most supported BSPs. This file is used
by the linker. by the linker.
This script places the various sections of the image according to what features This script places the various sections of the image according to what features
@ -54,7 +54,7 @@ end of the RODATA section. At runtime, the DATA section is copied into the RAM
region so it can be accessed with read and write permission. region so it can be accessed with read and write permission.
Most symbols defined in the sections below are subject to be referenced in the Most symbols defined in the sections below are subject to be referenced in the
Zephyr OS image. If a symbol is used but not defined the linker will emit an Zephyr Kernel image. If a symbol is used but not defined the linker will emit an
undefined symbol error. undefined symbol error.
Please do not change the order of the section as the nanokernel expects this Please do not change the order of the section as the nanokernel expects this

2
scripts/gen_idt/gen_idt.c
View file

@ -39,7 +39,7 @@ This program expects to be invoked as follows:
All parameters are required. All parameters are required.
<file name> is assumed to be a binary file containing the intList section from <file name> is assumed to be a binary file containing the intList section from
the Zephyr OS ELF image (microkernel.elf, nanokernel.elf, etc.) the Zephyr Kernel ELF image (microkernel.elf, nanokernel.elf, etc.)
<number of interrupt vectors> is the same as CONFIG_IDT_NUM_VECTORS. <number of interrupt vectors> is the same as CONFIG_IDT_NUM_VECTORS.

2
scripts/sanity_chk/bt_regression_chk
View file

@ -3,7 +3,7 @@
# Import common sanity check definitions # Import common sanity check definitions
# #
if [ -z ${ZEPHYR_BASE} ]; then if [ -z ${ZEPHYR_BASE} ]; then
echo "shell variables required to build Zephyr OS are not set" echo "shell variables required to build Zephyr Kernel are not set"
exit 1 exit 1
fi fi
if [ ! -d ${ZEPHYR_BASE} ] ; then if [ ! -d ${ZEPHYR_BASE} ] ; then

2
scripts/sanity_chk/footprint_chk
View file

@ -34,7 +34,7 @@
# Import common sanity check definitions # Import common sanity check definitions
# #
if [ -z ${ZEPHYR_BASE} ]; then if [ -z ${ZEPHYR_BASE} ]; then
echo "shell variables required to build Zephyr OS are not set" echo "shell variables required to build Zephyr Kernel are not set"
exit 1 exit 1
fi fi
if [ ! -d ${ZEPHYR_BASE} ] ; then if [ ! -d ${ZEPHYR_BASE} ] ; then

2
scripts/sanity_chk/out-of-tree_chk
View file

@ -34,7 +34,7 @@
# Import common sanity check definitions # Import common sanity check definitions
# #
if [ -z ${ZEPHYR_BASE} ]; then if [ -z ${ZEPHYR_BASE} ]; then
echo "shell variables required to build Zephyr OS are not set" echo "shell variables required to build Zephyr Kernel are not set"
exit 1 exit 1
fi fi
if [ ! -d ${ZEPHYR_BASE} ] ; then if [ ! -d ${ZEPHYR_BASE} ] ; then

2
scripts/sanity_chk/regression_chk
View file

@ -34,7 +34,7 @@
# Import common sanity check definitions # Import common sanity check definitions
# #
if [ -z ${ZEPHYR_BASE} ]; then if [ -z ${ZEPHYR_BASE} ]; then
echo "shell variables required to build Zephyr OS are not set" echo "shell variables required to build Zephyr Kernel are not set"
exit 1 exit 1
fi fi
if [ ! -d ${ZEPHYR_BASE} ] ; then if [ ! -d ${ZEPHYR_BASE} ] ; then

6
scripts/sanity_chk/sanity_chk
View file

@ -34,7 +34,7 @@
# Import common sanity check definitions # Import common sanity check definitions
# #
if [ -z ${ZEPHYR_BASE} ]; then if [ -z ${ZEPHYR_BASE} ]; then
echo "shell variables required to build Zephyr OS are not set" echo "shell variables required to build Zephyr Kernel are not set"
exit 1 exit 1
fi fi
if [ ! -d ${ZEPHYR_BASE} ] ; then if [ ! -d ${ZEPHYR_BASE} ] ; then
@ -70,7 +70,7 @@ EOF
long_help() { long_help() {
cat << EOF cat << EOF
Script to sanitize Zephyr OS. Script to sanitize Zephyr Kernel.
The full sanity check consists of the following phases: The full sanity check consists of the following phases:
@ -83,7 +83,7 @@ by using the available command options.
*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-= *-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=*-=
Before running the script, ensure Zephyr OS environment variables are set. Before running the script, ensure Zephyr Kernel environment variables are set.
The script returns 0 on success. If an error is encountered at any point The script returns 0 on success. If an error is encountered at any point
the script terminates with an error message and returns the exit value the script terminates with an error message and returns the exit value

2
zephyr-env.sh
View file

@ -1,6 +1,6 @@
if [ "X$(basename -- "$0")" == "Xzephyr-env.sh" ]; then if [ "X$(basename -- "$0")" == "Xzephyr-env.sh" ]; then
echo "Source this file (do NOT execute it!) to set the Zephyr OS environment." echo "Source this file (do NOT execute it!) to set the Zephyr Kernel environment."
exit exit
fi fi