Difference between revisions of "Talk:PineTime external flash partitioning"

Line 25:

===Application===

The application firmwares, on the other side, can be more flexible, and a common partitioning scheme can have some sense '''if multiple firmware developers agree to implement it'''. They would have to agree on a partition table scheme, file system, file formats,... That won't be easy, but that's possible. In this case, the partition table can be stored in the FS section at offset 0xb4000, and the bootloader won't have any knowledge of it. As the external spi memory flash is mostly unused (to my knowledge, only wasp-os uses it), everything is still possible on that part of the memory.

The application firmwares, on the other side, can be more flexible, and a common partitioning scheme can have some sense '''if multiple firmware developers agree to implement it'''. They would have to agree on a partition table scheme, file system, file formats,... That won't be easy, but that's possible. In this case, the partition table can be stored in the FS section at offset 0xb4000, '''and the bootloader won't have any knowledge of it'''. As the external spi memory flash is mostly unused (to my knowledge, only wasp-os uses it), everything is still possible on that part of the memory.

But... do we really need to share data between multiple firmwares installation? Let's compare with the PinePhone : when you install a new OS image on the EMMC or on the SD card, the user settings (wifi password, timezone, applications,...) won't be kept. If the user wants to keep files in the process, they have to backup them manually (on the SD card or on a computer) before flashing the new firmware and then restore them manually.

@@ Line 25: / Line 25: @@
 ===Application===
-The application firmwares, on the other side, can be more flexible, and a common partitioning scheme can have some sense '''if multiple firmware developers agree to implement it'''. They would have to agree on a partition table scheme, file system, file formats,... That won't be easy, but that's possible. In this case, the partition table can be stored in the FS section at offset 0xb4000, and the bootloader won't have any knowledge of it. As the external spi memory flash is mostly unused (to my knowledge, only wasp-os uses it), everything is still possible on that part of the memory.
+The application firmwares, on the other side, can be more flexible, and a common partitioning scheme can have some sense '''if multiple firmware developers agree to implement it'''. They would have to agree on a partition table scheme, file system, file formats,... That won't be easy, but that's possible. In this case, the partition table can be stored in the FS section at offset 0xb4000, '''and the bootloader won't have any knowledge of it'''. As the external spi memory flash is mostly unused (to my knowledge, only wasp-os uses it), everything is still possible on that part of the memory.
 But... do we really need to share data between multiple firmwares installation? Let's compare with the PinePhone : when you install a new OS image on the EMMC or on the SD card, the user settings (wifi password, timezone, applications,...) won't be kept. If the user wants to keep files in the process, they have to backup them manually (on the SD card or on a computer) before flashing the new firmware and then restore them manually.

Difference between revisions of "Talk:PineTime external flash partitioning"

Navigation menu

Search