split ext/hal/st into two modules:
- hal_stm32: For the code meant to run on STM32
- hal_st: For the code meant to drive ST components
Fixes#16316
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
We need to be able to force certain versions based on the branch and
code base being used. For example for 1.14 we will need to apply some
fixes or revert some commits that may only apply to master.
Next step is also adding this to 1.14 branch and use a working commit.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
To avoid and minimize conflicts when items are always added to the
bottom of the list, order things alphabetically.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This fixes some high priority issues, including syntax errors in
docstrings which prevent us from including API docs in our Sphinx
tree.
Signed-off-by: Marti Bolivar <marti@foundries.io>
Set the revision to the v0.5.6 tag in west.yml and update the minimum
version. Barring any (more) major undiscovered issues, this will be the
version used with Zephyr v1.14.
Signed-off-by: Marti Bolivar <marti@foundries.io>
Use tinycbor from the tinycbor repo directly and drop the library from
ext/.
Add entry to west.yml and update SHA.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This is the west manifest file for mainline zephyr.
For a burn-in period, we are going to keep west pointing at master to
avoid deps rolls as we iron out any kinks. We can then set its
revision to a SHA after things settle down.
The projects key is mandatory (if there's only one repository, there
wouldn't be much need for west!) so we'll start things off with the
net-tools repository at its current master SHA.
Signed-off-by: Marti Bolivar <marti@foundries.io>