Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FCR] Bump to Zephyr v4.0 #274

Open
rexut opened this issue Nov 18, 2024 · 0 comments
Open

[FCR] Bump to Zephyr v4.0 #274

rexut opened this issue Nov 18, 2024 · 0 comments
Assignees
Labels
question Further information is requested
Milestone

Comments

@rexut
Copy link
Member

rexut commented Nov 18, 2024

Is your feature request related to a problem? Please describe.
I'd like to work with Zephyr v4.0 as soon as it is released.

Describe the solution you'd like
Change the manifest in west.yml file. Qualify Bridle against new Zephyr version and fix all errors and warnings that happens.

Describe alternatives you've considered
Non.

Additional context
Non.

@rexut rexut added the question Further information is requested label Nov 18, 2024
@rexut rexut added this to the v4.0.0 milestone Nov 18, 2024
rexut added a commit that referenced this issue Nov 18, 2024
Add statement about:

  * the CI workflow changes
  * the standalone 'stm32f777xx' SoC support by Bridle
  * the DTS binding and Kconfig changes for the two I2C-based
    GPIO expander 'PCA9554' and 'PCA9555'
  * the copy-and-own of Sphinx extension 'warnings_filter'
  * the changes on documentation level: Sphinx v8.1, Sphinx
    copy button, inter-Sphinx links with valid official syntax
    and update output messages

Add GitHub issues #270, #271, #272 and #274.

Signed-off-by: Stephan Linz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants