**** BEGIN LOGGING AT Thu Dec 09 02:59:56 2021 Dec 09 16:56:13 Tofe; Seems the PPP uses uBoot, which we know from Tenderloin I guess? Dec 09 16:56:25 Should I get some inspiration from Tenderloin mainline in order to get it to boot? Dec 09 17:04:55 Seems pmOS use some custom uBoot: https://git.syndicate-lang.org/synit/pmaports-mirror/commit/162913a799272dcab05fa55366e833206748cbf3?style=unified&whitespace=ignore-all Dec 09 17:06:01 I guess I'll try to piggyback a bit on that to get something to build at least Dec 09 17:09:21 OK seems he has some PPP specific bits in https://git.sr.ht/~martijnbraam/u-boot/log/device/lightsaber Dec 09 17:09:44 I'm surprised he has commits there for PPP dating 11 months back ;) Dec 09 17:15:10 Ah seems we had uBoot for regular PinePhone too, should be able to adjust .bbappend and add the PPP bits based on pmOS build script I guess Dec 09 17:19:05 Will play a bit with it and see where I get Dec 09 17:19:20 Probably will be a lot of trial and error, but we'll see Dec 09 22:00:02 OK, getting somewhere already, just a bit stuck with the arm-trusted-firmware. Seems we're on 2.3 for regular PinePhone, pmOS is on 2.5 + patches, however upstream released 2.6 with most of the patches for Allwinner already included. Seems we only need the baudrate patch for rk3399. Not really sure what I'm doing wrong here? I would expect it to find gcc? Dec 09 22:00:03 https://bpa.st/F5WA Dec 09 22:00:29 And this is my updated recipe for the 2.6 version: https://bpa.st/UW4Q Dec 09 22:10:41 Seems I might something like this for the M0 firmware? https://git.yoctoproject.org/meta-rockchip/commit/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%25.bbappend?id=70c2725ae8751749cd358815fd3f033eff37c68e Dec 09 22:12:43 That would mean I'd need to add meta-arm layer right? Dec 09 22:16:18 Or just the specific recipes that we need... I.e.: https://git.yoctoproject.org/meta-arm/tree/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/gcc-arm-none-eabi_10.3-2021.10.bb and the arm-binary-toolchain.inc Dec 09 22:21:02 OK got it to build, just do_install fails now, but that's easy to fix Dec 09 22:21:12 Ehm do_deploy that is Dec 09 22:24:44 Now we'd just need to decide what's the best way to get gcc-arm-none-eabi into the build, either copy from meta-arm, or include the layer. Seeing that the layer also provides trusted-firmware-a, my gut feeling says we should take meta-arm and use it from there and drop our own recipes and maybe just suffice with .bbappends. JaMa/Tofe: thoughts on this? Dec 09 22:27:46 OK enough for today, getting close to something that builds at least... u-boot is the next step it seems, kernel seems to behave in terms of build, but still need to tweak defconfig **** ENDING LOGGING AT Fri Dec 10 02:59:56 2021