Daniel Egger
Daniel Egger
@jamesmunns Is this something you'd still like to pursue?
> Yet, there are no implementation guidelines, so it’s not easy to know which way among the others is the more “correct”. Well, there's no right or wrong. Even if...
> I think we can homogenize at least the hal un stm32 by having a common interface, begining by the clock management I very much doubt that. Clocking is vastly...
Meanwhile there are a variety of different toolchains available out-of-the-box: https://doc.rust-lang.org/nightly/rustc/platform-support.html So I think this issue can be considered done.
@andre-richter Is this still something you think we should do?
As briefly discussed in our triage meeting, I think time has shown that there's pretty much no overlap between WG interests and commercial interests which would invoce a conflict of...
I think we have added support for all interfaces which can be easily supported via `embedded-hal`. In addition there's projects like https://github.com/rust-embedded-community/embedded-nal and https://github.com/smoltcp-rs/smoltcp to take care of the more...
@adamgreen any idea why it started failing again? cf. https://travis-ci.org/rust-embedded/bookshelf/builds
> Could you include a printed copy (or QR code link) of the MIT License in the product you are shipping? Would this suffice? (Note: I am not a contributor...
No idea, sorry. I've been using OpenOCD only for flashing but even that is obsolete now. @arkap Any idea?