floppy-driver-rs VS xargo

Interesting and fun project! I found the MFM encoding page particularly enlightening as it explained why you have to write a full sector at a time on a floppy, even though there's nothing physically constraining you to that so far as I could see on the electromechanical/hardware side of things.

And on that page the "make sure the compiler didn't inject 10,000 lines of boundary checks" bit told me everything I needed to know about what language the project was written in :lol: - here's the link to the driver: https://github.com/SharpCoder/floppy-driver-rs

I'm glad to see the Teensy continuing to get love; I adopted it back when it was at v1 and v2 as it was just such a complete no-brainer of a better choice than the Arduino stack everyone was using back then. I think now there's even an Arduino-on-Teensy software stack, but I've moved to just using STM32 directly and have greatly enjoyed coding for that target in rust.

Head on over to the https://floppy.cafe if you want to learn everything about how these ancient disks work. I spent the last few months bit-banging a device from the 90s and documenting my process. Hopefully this information proves useful to somebody. Aliens, technoarcheologists, retro computing geeks? I'm not sure who my target audience is, but it was a lot of fun to throw this together and I hope you can enjoy my little slice of the 90s!

Head on over to the floppy cafe, if you want to learn more! https://floppy.cafe/ and here's my github repo with the full source for my project: https://github.com/SharpCoder/floppy-driver-rs

I think you can use xargo for this with:

If you need to pass arguments to rustc, try cargo rustc or RUSTFLAGS instead of invoking it manually. If you're cross-compiling, check out cross (uses Docker) or xargo.