Dario Nieuwenhuis

If user wants to store the peripheral somewhere such as a RTIC resource, they could do this: ```rust enum DisableableUart { Disabled(UARTE0, uarte::Pins), Enabled(Uarte), } ``` IMO this is much...

I am guilty of that too, hehe. However if you're willing to use unsafe you can already do this with `Peripherals::steal()` or with `let u: UARTE0 = mem::transmute(());`. I'm not...

> Not sure why though? And what are the consequences of doing this anyways? Higher power usage? gpios have an "input buffer" you can connect/disconnect. If you don't connect it,...

There's `.write()`, which should ignore incoming bytes indeed. If it's hanging it's a bug. Which chip are you using?

@darkwater could you confirm which chip you're using?

if it was stm32, there's been a few hang fixes: #663 #664 . Could you check again? Thank you! :)

What're you using this for exactly? you're writing your own CAN driver and need to access the value of `REGISTERS`, `NUM_FILTER_BANKS`?

If it's something widely-applicable it should Ideally be in-tree though. If it's not widely applicable (specific to a project) then lack of macrotables shouldn't be an issue because the project...

Chunking will work for UARTE and SPIM, not for TWIM. Unfortunately, the TWIM hardware does a repeated-start every time you start a new transfer. This will break communications with chips...

Could you add a new `examples/nrf-rtos-trace` example project instead? The examples lose "teaching value" really quickly if there's so much complex feature stuff going on in the `Cargo.toml`. (Yes, I...