Hi, after !50 (merged) vmlinuz-dtb is no longer installed. This breaks the heimdall-isorec installation method, as that method uses that file. Only samsung-{i9100,i9100g,kiran} use this method at the moment.
I am not sure whether it would be best to fix this in boot-deploy or pmbootstrap, but I guess we can cat vmlinuz and the dtb somewhere in any case.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Yes. And it is only these very old devices, that do not support a standard boot.img, that flash the vmlinuz-dtb file with the "heimdall-isorec" method.
We could also update the heimdall_flash_kernel.sh script to do the concatenation of vmlinuz and dtb there, but would be nice to be able to keep flashing with (different versions of) pmbootstrap, boot-deploy and heimdall as backward compatible as possible
vmlinuz-dtb could also be used for kernel upgrades on device (when deviceinfo_flash_kernel_on_update="true") for the heimdall-isorec devices. I don't think deviceinfo_flash_kernel_on_update has any effect for these devices at the moment though
could boot-deploy copy vmlinuz-dtb to the boot partition when flash_heimdall_partition_kernel is set? Is that a good indicator for "this device uses heimdall, and thus pmb and the flash upgrade script need vmlinuz-dtb" ?
deviceinfo_flash_method="heimdall-isorec" is a better indicator, most heimdall-using devices (the ones woth deviceinfo_flash_method="heimdall-bootimg") do not need vmlinuz-dtb, only heimdall-isorec devices do
oh ok, thank you! yeah this would be pretty trivial to patch boot-deploy to handle. just conditionally re-add the bit removed in !50 (merged) if deviceinfo_flash_method == "heimdall-isorec"
I'm thinking a bit more about why!50 (merged) was done. adding the patch I just mentioned above to boot-deploy would re-add vmlinuz-dtb to /boot. It's technically not used for booting, but it needs to live somewhere, where other scripts/tools can find it. Traditionally this has been /boot/vmlinuz-dtb, so they are all looking for it there. If we try to preserve the intention of !50 (merged) by only having files used during boot in /boot, then we would need to 1) have boot-deploy take some new option for a path outside of /boot, 2) save vmlinuz-dtb in that special path, 3) update all of those tools to look in the new path and their packages have to have an constrained dependency on a specific boot-deploy version that uses the new path for writing out vmlinuz-dtb.
tl;dr: you're right about wanting to fix it only in boot-deploy, even though it would have been nicer to keep vmlinux-dtb out of /boot... at least on most devices, that file will continue to be kept out of /boot, and I think that still makes @calebccff happy (right?)