01-19-2021, 12:01 PM
(01-18-2021, 02:08 AM)as400 Wrote: Some answers from me:Perhaps a stupid question then.
1. Suspend not working has nothing to do with uboot - rather with ATF - as Simon wrote.
In MrFixit's release there are three files, uboot.img, idbloader.img, and trust.img. I assume trust.img is what contains ATF? If that's correct, then that file hasn't changed since MrFixit's release 1.1. Danielt's script was originally using release 1.4, and with it suspend didn't work, but after upgrading to MrFixit's release 2.0 suspend works, and the only change there is uboot.img. Your build has idbloader.img and u-boot.itb, which I assume (perhaps incorrectly?) are the equivalent of idbloader.img and uboot.img in MrFixit's release and need to be written to eMMC at the same locations. That means I'd be still using the same ATF as trust.img in MrFixit's release. When I tried using your u-boot build suspend wouldn't work properly (it's been some time now, but IIRC machine would simply freeze on suspend).
Was it that one of my assumptions is incorrect, or did I miss something else? Because honestly if I can get suspend to work I'd much rather use your build than carry a recovery microSD card with me everywhere in case there are any boot problems with a new kernel.
This message was created with 100% recycled electrons