Dario Nieuwenhuis

`tm4c129x_hal` needs updating, it's implementing the embedded-hal 0.2 traits, while embedded-hal-bus uses embedded-hal 1.0

Embassy HALs implement both the 0.2 and 1.0 traits, should be a good reference since you can compare: https://github.com/embassy-rs/embassy/blob/ea25112f7d1ce27a7216ce6c3aab983dc3a0d7c0/embassy-nrf/src/spim.rs#L549-L601

Originally `Interface` would permanently own the `Device`. Later I changed it to taking `&mut Device` in method calls. It's true creation only needs the DeviceCapabilities, but I thought taking the...

In the end sequence numbers are integers modulo 2^32 where the only thing that matter is the position of one relative to another, not the absolute value.. The behavior is...

@elagil if you look through the diff the CI bot posted, there's many timers where the `registers` field is gone. This will make those be unusable with the HAL. The...

ah sorry I should've read the thread instead of assuming my memory is in working order :sweat_smile: There's people out there using a lot of timers, sometimes someone asks in...

There's ways to remove the panic fmt bloat without adding cfgs to every single crate. Have you tried these? - Don't use `panic-probe`, write your own panic handler that does...

> I want to stress that a major difference with this approach compared to the methods you listed is that you still get full panic info when something goes wrong,...

To clarify: it *is* a goal of Embassy to allow getting code size as small as possible. My position is not "code size is not a priority so `no-panic-msgs` isn't...

and `panic_immediate_abort`?