Go to file
Andy Ross 358355a23d tests/kernel/smp: Fix cases for !SCHED_IPI_SUPPORTED
Obviously the test of the feature won't work if we don't have an IPI.
And there were two threads that spawned threads that enter busy loops,
expecting to be able to abort them from another CPU.  That doesn't
work[1] without an IPI.  Just skip these cases rather than trying to
kludge up some kind of abort signal.

[1] Rather, it does work, it just takes infinite time for these
    particular test cases.  Eventually the CPU would be expected to
    receive some other interrupt like a timeout, which would work to
    abort the running thread.  But no such timer was registered.

Signed-off-by: Andy Ross <andyross@google.com>
2022-09-19 09:19:02 +02:00
.github ci: twister: Check out west modules for test plan 2022-09-16 21:04:25 +09:00
arch arch: arm: userspace: fix the incorrect ssf under bad syscall 2022-09-19 09:17:26 +02:00
boards dts: rt1010: Fix RT1010 IP base addresses 2022-09-16 14:50:06 -05:00
cmake cmake: test format options together 2022-09-14 09:37:59 +00:00
doc doc: hardware: peripherals: canbus: controller: add start/stop calls 2022-09-13 16:06:50 +00:00
drivers clock: mcux: Use FSL_FEATURE_MCG_FFCLK_DIV to conditionalize 2022-09-16 13:21:04 -05:00
dts dts: rt10xx: Fix SAI dts entries 2022-09-16 14:50:06 -05:00
include net: net_pkt: Simplify net_pkt_compact() API 2022-09-15 16:35:11 +00:00
kernel kernel/idle: Fix !SCHED_IPI_SUPPORTED 2022-09-19 09:19:02 +02:00
lib includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h> 2022-09-05 16:31:47 +02:00
misc misc: generated: update configs.c template with <zephyr/...> prefix 2022-05-09 12:45:29 -04:00
modules drivers: can: add start and stop CAN controller API functions 2022-09-13 16:06:50 +00:00
samples samples: drivers: can: babbling: start can node 2022-09-16 08:26:47 +00:00
scripts dts: add primitive support for multi-bus in bindings 2022-09-09 17:42:33 -04:00
share cmake: extend zephyr_get() to handle build configurations from sysbuild 2022-09-02 15:16:50 +02:00
soc dts: rt1010: Fix RT1010 IP base addresses 2022-09-16 14:50:06 -05:00
submanifests
subsys Bluetooth: Host: Make adv error reporting more consistent 2022-09-16 10:53:31 +01:00
tests tests/kernel/smp: Fix cases for !SCHED_IPI_SUPPORTED 2022-09-19 09:19:02 +02:00
.checkpatch.conf
.clang-format clang-format: do not merge blocks/functions into single line 2022-07-15 19:18:28 -04:00
.codecov.yml
.editorconfig editorconfig: Improve verbosity 2022-04-28 08:55:39 -04:00
.gitattributes
.gitignore .gitignore: exempt scripts/build from ignore 2022-07-30 08:29:29 -05:00
.gitlint
.mailmap
CMakeLists.txt cmake: move testing of compile flag in environment to top CMakeLists.txt 2022-09-01 15:59:43 +02:00
CODE_OF_CONDUCT.md
CODEOWNERS CODEOWNERS: Add/change onership of mcumgr components 2022-09-12 14:16:04 +00:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr testsuite: ztress: Use XOSHIRO generator when ztress is used 2022-09-08 05:43:17 -04:00
LICENSE
MAINTAINERS.yml MAINTAINERS: Add Andrewpini as BTM collaborator 2022-09-12 10:54:02 +00:00
README.rst readme: Update stale documentation links 2022-06-06 12:07:12 +02:00
VERSION release: Zephyr 3.2.0-rc2 2022-09-16 16:03:52 -05:00
version.h.in
west.yml clock: mcux: Use FSL_FEATURE_MCG_FFCLK_DIV to conditionalize 2022-09-16 13:21:04 -05:00
zephyr-env.cmd
zephyr-env.sh everywhere: fix typos 2022-03-18 13:24:08 -04:00

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/_static/images/logo-readme.svg">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <a
   href="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml?query=branch%3Amain">
   <img
   src="https://github.com/zephyrproject-rtos/zephyr/actions/workflows/twister.yaml/badge.svg?event=push"></a>


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM (Cortex-A,
Cortex-R, Cortex-M), Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V,
SPARC, MIPS, and a large number of `supported boards`_.

.. below included in doc/introduction/introduction.rst


Getting Started
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

.. start_include_here

Community Support
*****************

Community support is provided via mailing lists and Discord; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://github.com/zephyrproject-rtos/zephyr/releases
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI nightly build results.
* **Chat**: Real-time chat happens in Zephyr's Discord Server. Use
  this `Discord Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Discord Invite: https://chat.zephyrproject.org
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/develop/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/develop/getting_started/index.html#asking-for-help