-
Notifications
You must be signed in to change notification settings - Fork 1
Dont depend on hal #6
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
Conversation
@@ -26,6 +22,7 @@ cortex-m = { version = "0.7.7", features = ["critical-section-single-core"] } | |||
defmt-rtt = "0.4.0" | |||
cortex-m-rt = "0.7.2" | |||
panic-probe = { version = "0.3.0", features = ["print-defmt"] } | |||
stm32g4xx-hal = { git = "https://github.com/usbalbin/stm32g4xx-hal", branch = "hrtim", features = ["defmt", "hrtim"] } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@burrbull As far as I know we can not have optional dev dependendecies and thus need to select one hal to use for the examples. Would it then be better to let the examples live in the corresponding hals? See stm32-rs/stm32g4xx-hal#192
it should not be hard to rebase. So I'm fine. |
* Dont depend on hal * Remove connect pins * Move out device specific things to hals * update pac * Update CI * fixes * Fix errors for f334 and h7 * Update examples * clippy
Avoid depending on hals. Most of the removed code will have to be moved out to the corresponding hals.
See stm32-rs/stm32g4xx-hal#192 for corresponding hal changes