embassy/examples/nrf/src/bin/uart_split.rs, branch main Unnamed repository; edit this file 'description' to name the repository. Rename examples/nrf to examples/nrf52840 2023-01-09T21:30:02+00:00 Dominik Boehi dominik.boehi@gmail.com 2023-01-09T21:29:58+00:00 0a27b6cedb52453123190671f294bbd34918e09a 






sync: flatten module structure.
2022-08-22T20:18:13+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-08-22T20:00:06+00:00

5677b13a86beca58aa57ecfd7cea0db7ceb189fa












split `embassy-util` into `embassy-futures`, `embassy-sync`.
2022-08-22T20:18:13+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-08-22T19:46:09+00:00

21072bee48ff6ec19b79e0d9527ad8cc34a4e9e0












Split embassy-time from embassy-executor.
2022-08-17T23:22:30+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-08-17T21:40:16+00:00

5daa173ce4b153a532b4daa9e94c7a248231f25b












Remove HAL initialization from #[embassy::main] macro.
2022-08-17T20:16:46+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-08-17T16:49:55+00:00

fc6e1e06b305d302d1b7ad17e8ef3a9be986c358












Split embassy crate into embassy-executor, embassy-util.
2022-07-29T21:40:36+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-07-29T19:58:35+00:00

a0f1b0ee01d461607660d2d56b5b1bdc57e0d3fb












Run rustfmt.
2022-06-12T20:22:31+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-06-12T20:15:44+00:00

a8703b75988e1e700af701116464025679d2feb8












Rename channel to mpmc
2022-06-12T05:16:56+00:00

huntc
huntchr@gmail.com

2022-06-12T05:16:56+00:00

99d19c7dcf077cdd06113bf013d6a458289b1ecb

I've renamed the channel module for the MPMC as mpmc. There was a previous debate about this, but I feel that the strategy here avoids importing `channel::channel`. The change leaves `signal::Signal`, but I think that's ok. It is all a bit subjective of course. The bottom line for me is that I really like the term mpmc - it means something to me and aligns with broader naming e.g. in Tokio.





I've renamed the channel module for the MPMC as mpmc. There was a previous debate about this, but I feel that the strategy here avoids importing `channel::channel`. The change leaves `signal::Signal`, but I think that's ok. It is all a bit subjective of course. The bottom line for me is that I really like the term mpmc - it means something to me and aligns with broader naming e.g. in Tokio.







Simpler Channel.
2022-04-05T23:34:08+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-04-05T22:00:29+00:00

27a1b0ea7316be4687e7173a73861d276974d502

- Allow initializing in a static, without Forever.
- Remove ability to close, since in embedded enviromnents channels usually live forever and don't get closed.
- Remove MPSC restriction, it's MPMC now. Rename "mpsc" to "channel".
- `Sender` and `Receiver` are still available if you want to enforce a piece of code only has send/receive access, but are optional: you can send/receive directly into the Channel if you want.





- Allow initializing in a static, without Forever.
- Remove ability to close, since in embedded enviromnents channels usually live forever and don't get closed.
- Remove MPSC restriction, it's MPMC now. Rename "mpsc" to "channel".
- `Sender` and `Receiver` are still available if you want to enforce a piece of code only has send/receive access, but are optional: you can send/receive directly into the Channel if you want.







Use embassy/defmt-timestamp-uptime in all examples.
2022-04-02T02:35:06+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2022-04-02T02:35:06+00:00

82803bffdab0842bf6c3e4bce21131d437b06669