Am 03.04.2016 um 21:59 schrieb Alexander Graf:
Am 03.04.2016 um 21:32 schrieb Andreas Färber afaerber@suse.de:
Am 03.04.2016 um 18:05 schrieb Andreas Färber: v2016.01 is the last release to boot Linux on the Firefly-RK3288 for me. On v2016.03 or master there is no output from the kernel.
Correction: Plain v2016.03 does work but not openSUSE's package.
[...]
ed980b8c62fbe17052ec6151a68b5b0be3809485 is the first bad commit commit ed980b8c62fbe17052ec6151a68b5b0be3809485 Author: Alexander Graf agraf@suse.de Date: Fri Mar 4 01:10:07 2016 +0100
efi_loader: hook up in build environment
Now that we have all the bits and pieces ready for EFI payload loading support, hook them up in Makefiles and KConfigs so that we can build.
So I take it that you successfully bisected to this commit with upstream master?
Yes. After wading through lots of v2016.01..v2016.03 commits where SPL was often too large to test, I came up with no conclusive findings. And re-testing v2016.03 suddenly worked - I assume that I forgot to initially test a self-built one without your backported patches. A git-bisect for v2016.03..563d8d93585035fa2a0b20190c1008eb625432c4 then pointed to the above mainline commit.
In that case consider me puzzled. As quick fix you should be able to just disable CONFIG_EFI in your .config file.
Confirming that master boots again when I disable CONFIG_EFI_LOADER.
On other boards such as Jetson TK1 (extlinux.conf) or Cubietruck (boot.scr) I have had no such problem with our 2016.03 based EFI-enabled package.
Regards, Andreas