Michel Machado

Are you trying to port only `f3write` and `f3read`? Or are you planning to port the other tools (e.g. `f3probe`)? I'm asking because `f3write` and `f3read` do not use libusb....

If you want, we can try a pull request to patch only `f3write` and `f3read`. Thus, we leave the other tools for when you have a chance to get them...

Hi @cmurf, There have been three F3 releases already after version 7.0. Could you try the current version 8.0? I don't think this bug still exists in the new version....

Good morning, @jtojnar, F3 is GPL-3-or-later. Thank you for your inquiry.

It is quite a project. I've added the tag "Help wanted" to this thread in the hope someone will pick the idea up.

HI @alainroger, Check out section ["The extra applications for Linux"](https://fight-flash-fraud.readthedocs.io/en/stable/introduction.html#the-extra-applications-for-linux) of our page on Read the Docs.

Your observations are correct. Notice that while the code uses masks, low-level hardware just ignores the high bits of the address bus. The code is simulating real fake drives and...

`real_size_bytes` is the size from the beginning of the drive (i.e. from block 0) that is expected to be usable. This information has to be detected. `f3probe` even accounts for...

Bad blocks are inferred from the description of the simulated drives. For example, the parameters of the first limbo drive in the unit test are as follows: ```c /* Geometry...

In order to avoid duplicate patches in this pull request, you need to `git rebase master` at your branch. You should `git push --force` afterward. On the question of what...