On Thu, May 26, 2016 at 8:44 PM, Martin Michlmayr <t...@hpe.com> wrote: > I'm not Debian's u-boot maintainer but I have some interest in Debian > on this board.
First sorry for the delay, I had an issue with my mail filters and I only saw the bug updates this week, after Mateusz pinged me directly on IRC. > I have some questions/comments: > > First of all, please split the upstream fixed in 3 patches and submit > them upstream. I haven't seen them there yet. I definitely agree > with changing the boot order. I cannot comment about the other > changes. Mateusz fixed the env size already, and I finally got time to send the other two minor fixes upstream. http://lists.denx.de/pipermail/u-boot/2016-June/258552.html http://lists.denx.de/pipermail/u-boot/2016-July/259567.html http://lists.denx.de/pipermail/u-boot/2016-July/259568.html Didn't yet send the change that fixes the partition id used to boot when using eMMC, trying to play with the bootable mbr/gpt flag first. > The other comments are related to the packaging: I believe on armhf > and arm64, the u-boot source builds different binary packages for the > different packages. You could probably create something like a > u-boot-qcom package with the DragonBoard support. (Vagrant can > confirm) I decided not to create a new package simply because there were not a lot of targets for arm64, but fine to add a package just for qcom devices. Will send another patch. > My bigger question is around Debian support: the boot loader on this > device requires boot images to be in a specific format made with > Qcom's "skeles" tools. They are currently not packages in Debian. > Is the ELF file useful, i.e. have you found a way to boot that > directly? Or do we need to package the skeles tools and create the > dt.img and a bootable .img file? We still need the qcom tool to create a working boot image, and we should definitely package that as well (will have a look into that). I know Mateusz was first working on chainloading from lk, so once we get u-boot to replace it completely, the special tool shouldn't be needed anymore (but that might take a while). Thanks, -- Ricardo Salveti de Araujo
