Thales

Results 50 comments of Thales

> It would be great to see it in HAL. Yes, let's keep this open to track that.

The idea is to implement the necessary abstraction and traits to the Adc HAL type, and pass it to the `Transfer` API instead of the pac type. It seems that...

I think the example declares its own `panic_handler` to avoid pulling in more dependencies, you don't need to define it yourself for this crate to work.

I would also want to know if we want to continue with the current behavior of `Addr`, where if you clone it you get a free spot on the queue...

The problem is that the PAC itself isn't really used in the example and the PAC is the responsible for providing the interrupt vectors to `cortex-m-rt`, the simplest solution is...

> Hm, usually that should work automatically via the prelude. If it doesn't that's probably a problem with the HAL impl. The problem is that the example in question doesn't...

The issue referenced is actually: https://github.com/rust-embedded/cortex-m-semihosting/issues/49 Problems of moving repos, I guess.

@jonas-schievink Have you had any idea on how to integrate a callback mechanism with resources policies like the one used in RTFM ? Or even reentrancy problems when using the...

I believe this is caused by the `Drop` implementation of `ContextFut`: https://github.com/actix/actix/blob/d7aab0a0f439679a570d08aaa6972ad8b60003de/actix/src/contextimpl.rs#L219-L232 The poll will call your `started` function if `ContextFut` didn't get the change to be polled before. The...

I believe this is caused by forcing the system shutdown when handling signals in `actix-server`: https://github.com/actix/actix-net/blob/14272a1762680aec65b59ac084819e4bd0d4e4a6/actix-server/src/server.rs#L316-L345 This seems unexpected, at least for the SIGTERM case.