Peter Krull

There are only 4 outputs (X, Y, Z and E0), but Z has to connectors because you can use two Z motors in series with the same driver. It is...

In my own fork I have been playing with creating an array of `Block`s in the `VolumeManager::write()` function to get multi-block writes. It works, but it is quite inefficient memory-wise,...

I like the idea of the 4K buffer, since that is essentially what I have ended up doing external to this library. If the entire buffer could be handled internally,...

> So far, I've had one buffer that the files and FAT32 code can temporarily access. This is designed for microcontrollers with like 8K of RAM total. How would that...

I am aware of that, maybe I misunderstood your previous statement. Hmm, are there any parts of the library, except from `write`, which would benefit from having a large buffer?...

For anyone who stumbles across this issue in search for async, I have an up to date (at the time of writing) branch which supports async: https://github.com/peterkrull/embedded-sdmmc-rs/tree/develop-async One difference to...

I am considering removing the peek methods for the receivers. Their use case is dubious, and not marking a message as seen can make stuff hard to reason about for...

A fix sees to be just using StaticCell ```rust static STACK: StaticCell = StaticCell::new(); ``` and then ```rust spawn_core1(p.CORE1, STACK.init(Stack::new()), move || { let executor1 = EXECUTOR.init(Executor::new()); executor1.run(|spawner| unwrap!(spawner.spawn(core1_task()))); });...

For my suggestions the VolumeManager does not need to be changed at all. For the first point, it already exposes the underlying device through `VolumeManager::device(&mut self) -> &mut D` allowing...

The multiplication seems fine to me, but normalizing a vector where all entries are zeros is what seems to return NaN. However it seems to me that the entries of...