4 ms·

I vaguely recall thinking the file was just some sort of serial number or stock tracking metadata when I deleted it. It might have instead failed for quite mund

by billpg 2y ago

I vaguely recall thinking the file was just some sort of serial number or stock tracking metadata when I deleted it. It might have instead failed for quite mundane reasons such as low quality manufacture. I don't know. Exposing the firmware in this fashion would be a bad idea for all of these reasons. It is a good thing that SD card manufacturers don't do this any more, if they ever did.

vardump 2y ago
Firmware definitely would not be on the filesystem layer or even accessible on the block device.
- 01HNNWZ0MV43FF 2y ago
  You'd think yeah
  - tiberious726 2y ago
    It isn't. Before a chip has firmware loaded, it can't decode filesystems.
    - 15155 2y ago
      Even after a chip has firmware loaded, which controller can make logical sense of a filesystem?
      - goodburb 2y ago
        According to SDXC specs, the controller looks for exFAT markers to relocate the table and bitmap to smaller AU units. exfatprogs can pack bitmap with table for SDHC and lower: https://manpages.debian.org/experimental/exfatprogs/mkfs.exfat.8.en.html https://manpages.debian.org/experimental/exfatprogs/mkfs.exf...
    - samatman 2y ago
      That doesn't at all mean that the firmware can't be exposed through the filesystem. Is that a bad idea? Almost certainly. Is it possible? Absolutely yes.