Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Andy Ross 9f068737d5 arch/x86_64: Suppress spurious linker-generated code in the 32 bit stub
Within the past few days, an update to the Ubuntu 18.04 toolchain has
begun emitting code sections during link that are messing with our
stub generation.  They are appearing in the 32 bit stub link despite
not being defined in the single object file, and (worse) being
included in the output segment (i.e. at the start of the bootloader
entry point!) despite not being specifically included by the linker
script.  I don't understand this behavior at all, and it appears to be
directly contrary to the way the linker is documented.

Marc Herbert discovered this was down to gcc being called with
--enable-default-pie, so -no-pie works to suppress this behavior and
restore the default.  And it's correct: we aren't actually generating
a position independent executable, even if we don't understand why the
linker script is being disregarded (to include sections we don't
include).  See discussion in the linked github issue.

Fixes #15877

Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2019-05-06 19:48:32 -04:00
.github/ISSUE_TEMPLATE templates: Update issue templates 2018-12-07 08:27:20 -05:00
.known-issues doc: introduce final structure 2019-02-05 07:04:40 -05:00
arch arch/x86_64: Suppress spurious linker-generated code in the 32 bit stub 2019-05-06 19:48:32 -04:00
boards soc: riscv32: Move rv32m1 flash memory definitions to dts 2019-05-06 19:09:59 -04:00
cmake cmake: Toolchain abstraction: Introduce toolchain_ld_relocation macro 2019-05-04 08:59:53 -04:00
doc doc: fix west boards tip 2019-05-06 16:30:05 -04:00
drivers drivers: ieee802154_nrf5: Implement configure API 2019-05-06 10:58:04 -04:00
dts soc: riscv32: Move rv32m1 flash memory definitions to dts 2019-05-06 19:09:59 -04:00
ext drivers: ieee802154_nrf5: Implement configure API 2019-05-06 10:58:04 -04:00
include crc: remove deprecated crc headers 2019-05-06 09:33:51 -04:00
kernel kernel: fix k_stack_alloc_init() 2019-05-06 19:47:01 -04:00
lib lib: cmsis_v1: set stack size larger if coverage 2019-05-02 15:42:33 -04:00
misc license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
samples usb: webusb: Add more log output 2019-05-06 11:18:34 +02:00
scripts scripts: make west build -h fit on a screen 2019-05-06 16:30:05 -04:00
soc soc: riscv32: Move rv32m1 flash memory definitions to dts 2019-05-06 19:09:59 -04:00
subsys usb: Add log for endpoint assignment 2019-05-06 19:00:02 -04:00
tests tests: usb: desc_sections: Cleanup test 2019-05-06 19:00:02 -04:00
.checkpatch.conf
.clang-format
.codecov.yml
.editorconfig editorconfig: Set insert_final_newline true 2019-04-10 14:15:38 +02:00
.gitattributes
.gitignore
.gitlint gitlint: do not start with subsys: 2018-11-28 09:22:01 -08:00
.mailmap
.shippable.yml ci: send email to builds@ mailing list if master fails 2019-05-06 13:39:30 -04:00
.uncrustify.cfg
CMakeLists.txt cmake: Toolchain abstraction: Introduce toolchain_ld_relocation macro 2019-05-04 08:59:53 -04:00
CODEOWNERS CODEOWNERS: Add code owner for rv32m1_vega related files 2019-05-06 14:52:17 -05:00
CODE_OF_CONDUCT.md coc: move to markdown format 2019-01-24 15:37:15 -05:00
CONTRIBUTING.rst doc: Fixed a link in CONTRIBUTING.rst 2019-02-28 12:46:04 -08:00
Kconfig
Kconfig.zephyr cmake: LD: Allow input sections to remain unsorted 2019-04-24 13:58:00 -07:00
LICENSE
Makefile doc: add clean target to Makefile 2019-02-05 16:58:14 -05:00
README.rst README.rst: shorten it 2019-04-18 16:46:37 -04:00
VERSION release: Post-release patch level update 2019-04-16 15:50:31 -05:00
version.h.in
west.yml west: move to version v0.5.7 2019-03-29 11:24:32 +01:00
zephyr-env.cmd scripts: remove west from scripts/ 2019-01-29 10:15:01 +01:00
zephyr-env.sh shell: Piped output of cd to /dev/null when setting ZEPHYR_BASE. 2018-12-06 19:14:50 -05:00

README.rst

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <img
   src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


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-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

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

.. start_include_here

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.

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

.. TODO: add link to Asking for Help doc here when the latest page has it

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

Resources
*********

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

* **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://zephyrproject.org/developers/#downloads.
* **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.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack Invite`_ to register. There is also an IRC channel,
  ``#zephyrproject``, on `freenode`_.
* **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

.. _Slack Invite: https://tinyurl.com/yarkuemx
.. _supported boards: http://docs.zephyrproject.org/latest/boards
.. _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/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
.. _freenode: https://freenode.net/