merge f7xx-hal #667
merge f7xx-hal #667
Conversation
burrbull
force-pushed
the
f7_2
branch
4 times, most recently
from
73d8edb to
8d5b9dc
Compare
burrbull
force-pushed
the
f7_2
branch
7 times, most recently
from
4418fca to
8fe8f86
Compare
burrbull
force-pushed
the
f7_2
branch
5 times, most recently
from
abd13ff to
76b2d31
Compare
burrbull
force-pushed
the
f7_2
branch
5 times, most recently
from
64ff76c to
a5eb1b3
Compare
burrbull
force-pushed
the
f7_2
branch
7 times, most recently
from
0b03ebe to
5ae7a64
Compare
burrbull
force-pushed
the
f7_2
branch
15 times, most recently
from
42946ec to
3514184
Compare
|
cc @therealprof @eldruin @no111u3 What do you think about this? |
|
After briefly look through I found it's okay but should we rename crate or release it for two names instead of one? |
|
I find it weird to have F4 and F7 mixed into one since they're completely different series but if that's what people want, who am I to stop them. 🤪 |
F2/F4/F7 are very similar series. Peripherals on higher F4 chips (F446/69) are even closer to F7 then other F4. |
Yeah, there're some newer outliers. From that PoV all of the STM32 chips are very similar (sans the clock trees) because there're only a few versions of peripherals all the chips share... |
|
I am fine with anything you would like to maintain. The F7 repository has seen very little action lately. |
burrbull
force-pushed
the
f7_2
branch
3 times, most recently
from
ef15874 to
1919a74
Compare
4 participants
No description provided.