Repository navigation
device/husky: say what slot B reads on Lef's phone, and the DEVICES Boot cell wording - #488
Conversation
…oot cell wording Two optional points from the review of derekross#472. The roadmap now says Lef's slot B is still marked from the local unit's last write (0x35 reads 06), what that means until his next flash, that a flash clears the bit, and that the bit is not cleared by hand. The DEVICES Boot cell says Lef's phone, not this phone. Signed-off-by: Lef <me@lefteros.com>
|
@Somnius thank you for picking up both optional points so quickly. The wording One thing has moved since you wrote it, though. On #252 tonight you said that A heads-up on merging: #494 changes the 9a row right above the 8 Pro row, so Thanks again for keeping the record this careful. |
|
Thanks, that's a better line. I rewrote it as a dated record: B stayed marked (0x35 I didn't read |
…oot cell wording (derekross#488) Two optional points from the review of derekross#472, and the record of slot B on Lef's phone. The roadmap dates the marked state: B stayed marked (0x35 read 06) from the local unit's last write until the first flash after the unit was masked on 2026-11-07, when it read 04. Since then a boot spends one of B's tries (retry count 3 after set_active, 2 after one boot), so the flash-before-the-last-try routine applies. slot-successful:b was not read after those flashes; Lef will add it after the next one. The bit is not cleared by hand. The DEVICES Boot cell says Lef's phone, not this phone. Signed-off-by: Lef <me@lefteros.com>
@derekross these are the two optional things from your comment on #472. The roadmap now says my slot B is still marked from the unit's last write (0x35 reads
06), what that means until my nextflash(apushcosts no try, a broken pushed image means fastboot by the buttons), that a flash clears the bit, and that I won't clear it by hand. The DEVICES Boot cell says "Lef's phone" instead of "this phone". Docs only,tools/pr-checkpasses.