Jonathan 'theJPster' Pallant

cfg_attr I can live with. Different function signatures would be a problem.

> If we were smart we'd let you trade one directory handle for another Actually, no, you need a stack because you want to come back to the parent dir...

So I poked around a bit at this today, and I don't know why I thought my example worked - doing a `bkpt 0xAB` (a semihosting syscall) from unprivileged mode...

I think unit tests will be really hard given the test runner we have. Entering unpriv mode is kind of a one-time deal at the moment. If there's no place...

There's already a feature called `set-msplim` which sets `MSPLIM`. If we set PSPLIM here, we should use a function from cortex_m::asm to do it. I would leave this function as...

It appears the tests are failing - possible because the API changed?

So we already have functions for updating the FAT: `FatVolume::update_fat`. Could we just create some new `ClusterId` variants which represent clean/dirty volumes and use the `update_fat` function to write them...

> So we already have functions for updating the FAT: `FatVolume::update_fat`. Could we just create some new `ClusterId` variants which represent clean/dirty volumes and use the `update_fat` function to write...

Ok, first up, I'd like to make a point of order and ask that we name the Arm architectures correctly. * Armv6-M * Armv7-M * Armv7E-M * Armv8-M * Baseline...

A good source for what GCC supports on bare-metal Arm is: https://wiki.segger.com/GCC_floating-point_options Also interesting to see what Arm's own compiler does: https://developer.arm.com/documentation/dui0741/f/Overview-of-the-ARM-Compiler-6-Toolchain/ARM-architectures-supported-by-the-toolchain?lang=en They seem to have a single `arm-arm-none-eabi` target,...