Go to file
Alperen Sener 4e83af0dd9 Bluetooth: Mesh: Fix OOB info and URI hash in scan report message
OOB information should be in little endian in scan report messages.
URI hash should be retrieved as it is from unprovisioned device beacon
and encoded likewise into scan report messages like we do for UUID.

Signed-off-by: Alperen Sener <alperen.sener@nordicsemi.no>
2023-07-11 18:18:48 +00:00
.github ci: github: workflows: west_cmds: install natsort package 2023-07-07 09:19:02 +02:00
arch arch/x86: add more arch dcache functions 2023-07-11 11:33:16 -04:00
boards boards: arm: mimxrt595_evk: remove RK055HDMIPI4M display definition 2023-07-11 09:53:38 -05:00
cmake cmake: Fix code relocation functions with absolute paths 2023-07-10 12:05:00 +02:00
doc docs: flash_debug: host_tools: Fix reference to jlink host tools 2023-07-11 13:15:06 -04:00
drivers drivers: added support for clock PCF8563 2023-07-11 16:14:49 +02:00
dts drivers: added support for clock PCF8563 2023-07-11 16:14:49 +02:00
include/zephyr drivers/i2c: Add callback functions to support buffer mode in header file 2023-07-11 15:50:13 +02:00
kernel kernel: spinlock: LOCKED -> K_SPINLOCK 2023-07-10 09:27:21 +02:00
lib libc/picolibc: Use mutexes instead of semaphores for non-recursive locks 2023-07-10 15:11:15 +02:00
misc
modules tfm: Fix board selection for Musca B1 board 2023-07-11 09:44:14 +02:00
samples samples: drivers: kscan: enable logging, and add RK055HDMIPI4M shield 2023-07-11 09:53:38 -05:00
scripts twister: Initialise unbound 'hardware' variable 2023-07-10 13:57:21 +02:00
share cmake: boards: Fix issue with relative paths 2023-06-15 05:10:42 -04:00
snippets snippets: support for EXTRA_DTC_OVERLAY_FILE and EXTRA_CONF_FILE 2023-05-25 13:31:53 +00:00
soc ITE: drivers/i2c: Add I2C target driver used buffer mode 2023-07-11 15:50:13 +02:00
submanifests
subsys Bluetooth: Mesh: Fix OOB info and URI hash in scan report message 2023-07-11 18:18:48 +00:00
tests tests: drivers: kscan: add RK055HDMIPI4M shield 2023-07-11 09:53:38 -05:00
.checkpatch.conf
.clang-format clang-format: flag *_SECTION_FOREACH as for loop 2023-05-26 11:04:54 -05:00
.codecov.yml yamllint: fix all yamllint comments errors 2023-01-04 01:16:45 +09:00
.editorconfig
.gitattributes
.gitignore scripts: ci: check_compliance: add a no-modules Kconfig check 2023-07-05 09:11:02 +02:00
.gitlint
.mailmap mailmap: sort alphabetically 2023-05-15 13:23:32 -04:00
.yamllint scripts: compliance: add support for YAMLLint 2023-01-04 17:29:23 +01:00
CMakeLists.txt cmake/compiler: Add linker_script compiler property 2023-07-06 11:43:09 +02:00
CODE_OF_CONDUCT.md
CODEOWNERS soc: ti: cc13/26xx: clean up include hierarchy 2023-07-07 18:46:24 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr Kconfig: Tidy up dependants of NATIVE_APPLICATION 2023-07-05 07:01:19 -04:00
LICENSE
MAINTAINERS.yml MAINTAINERS: Renesas R-Car ARM64: add entry 2023-07-11 11:17:41 +02:00
README.rst
VERSION release: bump main to v3.4.99 2023-06-16 13:29:34 -04:00
version.h.in cmake: generalize VERSION infrastructure for better reuse 2023-05-17 13:56:58 +02:00
west.yml west.yml: update west.yml to use stm32wba hal 2023-07-11 15:05:05 +02:00
zephyr-env.cmd
zephyr-env.sh

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <picture>
         <source media="(prefers-color-scheme: dark)" srcset="doc/_static/images/logo-readme-dark.svg">
         <source media="(prefers-color-scheme: light)" srcset="doc/_static/images/logo-readme-light.svg">
         <img src="doc/_static/images/logo-readme-light.svg">
       </picture>
     </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