I have recently received a Dragonboard 820c with Debian installed with the following kernel:
Linux version 4.11.0-qcomlt (abuild@r2-a19) (gcc version 7.2.1 20171025 (Debian 7.2.0-12) ) #1 SMP PREEMPT Mon Nov 6 23:24:36 UTC 2017
Before flashing the latest snapshots onto this board I thought I would review the current state and I have found several confusing inconsistancies which I hope someone can resolve.
As delivered, the kernel reports that write protect is off on all UFS devices, but ufs-provision_toshiba.xml in dragonboard-820c-bootloader-ufs-linux-31 sets bLUWriteProtect=“1” for LUs 1 to 4. Does this tag have any effect or was it not set when my board was configured?
As I understand it, bit 60 of the attribute flags of a GPT partition entry denotes read-only. lsblk does not seem to recognise this bit as meaning read only while reporting it set in the PARTFLAGS column in each partition of LUs 1 to 4 except partition 32 of LU 4, sti.
In addition, sti (partition 30 of LU 4 now as system and recovery have been removed), in gpt_both4.bin of dragonboard-820c-bootloader-ufs-linux-31 does not have bit 60 of the attribute flags set, whereas all the other partitions of LUs 1 to 4 do. Is sti special?
In patch.xml of dragonboard-820c-bootloader-ufs-linux-31, there is one instance of start_sector=“NUM_DISK_SECTORS-1.” for each LU which reads start_sector=“NUM_DISK_SECTORS-1”. Does the full stop (period) have any significance? If so, then the missing one may produce unexpected results, if not, then why include them at all?