On Freitag, 21. Juni 2019 02:01:22 CEST you wrote:
> I think that it makes sense to put this snippet in qcom-msm8974.dtsi
> with a status of disabled, and then enable it in
> qcom-msm8974-fairphone-fp2.dts like so:
>
> imem@fe805000 {
> status = "ok";
> };
Do you want me to put the whole node in the the dtsi file? Even though these
values are the same, there are also custom vendor-specified values for specific
phones.
This opens another question, which values we should put into the dts files. For
example in the fairphone 2 bootloader source there's also the unused
#define ALARM_BOOT 0x77665503
and behind a #if VERIFIED_BOOT :
#define DM_VERITY_LOGGING 0x77665508
#define DM_VERITY_ENFORCING 0x77665509
#define DM_VERITY_KEYSCLEAR 0x7766550A
and 0x77665501 ("mode-normal") isn't used in the bootloader at all.
On the Linux kernel side, it has bootloader (0x77665500), recovery
(0x77665502), rtc (0x77665503), oem-* (0x6f656d00 | somevalue), edl (some
other addresses), and the else statements writes the 0x77665501 value in my
patch.
> What's the pmOS utility that utilizes this? I'll test it on the Nexus 5.
"reboot-mode" at https://gitlab.com/postmarketOS/pmaports/merge_requests/442
> Thanks,
>
> Brian
Attachment:
signature.asc
Description: This is a digitally signed message part.
