Go to file
Jarno Lämsä 419fa3ca6a net: lib: coap: CoAP client, multiple request handling
Use only single thread for handling polling of the sockets.
Each client will have only 1 active socket which to poll.
Each client can have multiple simultaneous requests ongoing.
The client only has one buffer for receiving and one buffer for sending.
Therefore the messages are reformed when resending.

Signed-off-by: Jarno Lämsä <jarno.lamsa@nordicsemi.no>
2023-06-28 15:19:34 +02:00
.github ci: doc-build: use customer runner 2023-06-20 16:49:07 +02:00
arch soc inf (native): Refactor into a top and bottom 2023-06-23 12:16:26 +02:00
boards include/zephyr: Fix linker scripts to define _end after all static RAM data 2023-06-28 08:41:02 +00:00
cmake cmake/linker_script: Fix cmake linker scripts to define _end 2023-06-28 08:41:02 +00:00
doc mgmt: ec_host_cmd: add logging system 2023-06-26 16:13:42 +02:00
drivers drivers: pinctrl: add pin group for NuMaker pinctrl 2023-06-28 06:49:38 +00:00
dts drivers: pinctrl: add pin group for NuMaker pinctrl 2023-06-28 06:49:38 +00:00
include/zephyr net: lib: coap: CoAP client, multiple request handling 2023-06-28 15:19:34 +02:00
kernel SMP: fix build failure if SMP=y and SYS_CLOCK_EXISTS=n 2023-06-22 06:17:27 -04:00
lib posix: fs: Fixes stat command to return file information 2023-06-23 17:04:34 -04:00
misc
modules segger: rtt: disable unsupported shell/log features 2023-06-23 14:42:41 +02:00
samples mgmt: hawkbit: remove NET_SOCKETS_POSIX_NAMES dependency 2023-06-28 06:32:45 +00:00
scripts twister: pytest: Parse report file to get testcases 2023-06-25 02:44:49 -04: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 include/zephyr: Fix linker scripts to define _end after all static RAM data 2023-06-28 08:41:02 +00:00
submanifests
subsys net: lib: coap: CoAP client, multiple request handling 2023-06-28 15:19:34 +02:00
tests tests: net: iface: verify multicast address not removed if used 2023-06-28 06:51:21 +00:00
.checkpatch.conf
.clang-format clang-format: flag *_SECTION_FOREACH as for loop 2023-05-26 11:04:54 -05:00
.codecov.yml
.editorconfig
.gitattributes
.gitignore tests bsim/net: Separate bsim networking and bluetooth tests. 2023-04-12 22:42:03 +09: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 device: make device dependencies optional 2023-06-21 09:32:05 +02:00
CODE_OF_CONDUCT.md
CODEOWNERS CODEOWNERS: Add code owners for Sensing Subsystem 2023-06-17 07:43:25 -04:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr kernel: syscalls: no need to include all syscalls in binary 2023-06-17 07:57:45 -04:00
LICENSE
MAINTAINERS.yml MAINTAINERS: cleanup the ITE Platform maintainer entry 2023-06-27 12:18:07 +00: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 manifest: openthread: Regular openthread upmerge to 6d55738 2023-06-23 09:20:23 +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