ryan

> How's this different from embedded? You can also serve other interrupt, or if you're handling it in an interrupt handler, run stuff from your main routine. Only in that...

good summary! > In my experience, buffered UART has been MUCH nicer to work with. agreed, and i think this is the right level of abstraction for the majority of...

the updated `spi` traits have me wondering if a similar approach would suit for ADCs... something like a shared `AdcDevice` that is split into separate channels implementing `AdcChannel` which drivers...

> Maybe having a trait for an "ADC device" is not really needed? We could just have this what i'm mostly wondering is whether this is a consistent problem with...

Yeah good question, depends on the implementation (Linux you could just create multiple devices `/dev/spidev0.N` and leave them to manage CS themselves), but in the more embedded case i think...

the current state is pretty well covered [here](https://github.com/rust-embedded/embedded-hal/issues/211) i think, at the moment people are experimenting with `embedded-time` and hopefully we'll move hardware traits back to e-h and maybe maintenance...

hey @ildar, @asdfhjkl, as far as i know nothing much has changed. we continue to use `mdBook` to generate the docs outputs, the open issue for epub/other outputs via `mdBook`...

Hey thanks for the issue, it's an interesting problem! At one point in time we were looking at extracting commonality using svd2rust (or similar) that we could then extend where...

not at all familiar with fedora packaging but it looks like it was dropped in fedora 30 due to a failed build / missing python dependency? https://bugzilla.redhat.com/show_bug.cgi?id=1603406

it appears arm now package `arm-none-eabi-gdb` in their binary distributions available [here](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads), if this works for you we could update the book to offer this alternative.