**** BEGIN LOGGING AT Tue Feb 22 02:59:56 2022 Feb 22 07:23:08 hideki0[m]: flashing the image on a sdcard is the easiest way Feb 22 08:18:28 hideki0[m]: What OS are you using for flashing? I often flash sdcards on Windows using BalenaEtcher which seems very reliable. On Linux you can use other tools as well Feb 22 09:27:52 Morning BTW Feb 22 09:29:09 Tofe; Building Chromium 91 here Feb 22 10:28:06 Tofe: Well this should mainly do it I guess for now to do the switch. I left out the Python3 patches for now, but should be easy enough to add when needed. https://github.com/webOS-ports/meta-webos-ports/commit/63358db1398271972146290af217b2a79eb2f85a Feb 22 10:30:26 morning Feb 22 11:01:03 Herrie: thanks, looks good ! Feb 22 11:01:58 Herrie: for the patches we'll had them with the switch to 94, or on 91 if they apply as-is, but no need to spend time on it now Feb 22 11:03:34 Tofe: Well JaMa prepared them, I just didn't add them yet Feb 22 11:04:30 I just took the one necessary to build with Python2 for now Feb 22 11:05:20 So basically left these out for now: https://github.com/shr-project/meta-webosose/blob/honister/meta-webos/recipes-webos/chromium/webruntime-repo_91.inc#L20-L51 Feb 22 15:50:11 Morning Feb 22 16:05:06 codepoet: Morning! Feb 22 16:06:49 So we're now in the middle of changing the compositor from luna-next to luna-surface-manager and luna-webappmgr+qtwebengine to wam+chromium 91. As you can imagine this is quite a change but should make things easier to maintain for future Feb 22 16:07:37 So bear with us for a bit while we get that all sorted, afterwards we can tackle the funny Enyo things with cookies Feb 22 16:09:21 yup, i figure i'll give you some time to get moved over. now i'm learning Enyo2. Feb 22 16:09:59 Chromium 94 is also in the pipeline from LGE side, these upgrades should be less painfull hopefully vs our custom QtWebEngine stuff Feb 22 16:10:32 And more sanity tested in millions of production devices Feb 22 16:10:42 So stability should be good really Feb 22 16:16:32 cool! i wonder if we'll hit CORS problems on the app side when moving to Chromium? Feb 22 16:17:06 codepoet: that shouldn't change a lot, it's also chromium that's used inside qtwebengine Feb 22 16:17:42 ok cool. that seems to be the biggest problem with Enyo2 cross platform Feb 22 16:19:14 https://github.com/webosose/luna-surfacemanager/commit/b03a663c7bf4c82a0f2e3646bf9b829a010d561d it's never very far away, yes :) Feb 22 16:39:53 HerrieTP: far in the pipeline :) Feb 22 17:08:33 JaMa: Ooh I guessed so, but switching Chromium with OSE is easier vs continuous patching of Qt Feb 22 17:09:05 And having WAM+Chromium opens back up the pmOS LuneOS port too ;) Feb 22 17:16:43 JaMa: Is python2 only used for Chromium or also somewhere else still in Honister? Feb 22 17:28:30 only qtwebengine should be using it in current LuneOS honister builds Feb 22 17:29:25 I'll compare py2 and py3 builds of webruntime soon and then we shouldn't wait for lge to publish 94 version Feb 22 17:38:16 JaMa: OK Feb 22 18:37:12 last major change was merged to kirkstone today and all our layers (and layers we use) were adapted to new variable names, if you were planing to start testing it, then now would be good time (from unstable branch) Feb 22 18:38:24 I've already built qemux86-64, tissot, hammerhead, raspberrypi4-64 and kernels for some other MACHINEs (like sargo) Feb 22 18:52:10 JaMa: OK I guess I'll play with that when I'm back in the weekend Feb 22 19:18:22 Tofe: any reason to use recipes-graphics/lvgl/lvgl_6.1.2.bb from meta-pine64 instead of meta-oe/recipes-graphics/lvgl/lvgl_8.1.0.bb ? other than historic that the later might not be available in hardknott or even earlier when you were working on it? Feb 22 19:20:45 there are couple more overlayed recipes which probably don't make much sense anymore https://pastebin.com/SyAuuZdm Feb 22 19:28:08 JaMa: completely historical reason Feb 22 19:28:40 however, bumping to 8.1 might require some rework Feb 22 19:31:43 will drop python3-dtschema-wrapper which is identical in meta-pine64 and create PR to drop apitrace and lvgl (after some testing) Feb 22 19:41:30 done https://github.com/webOS-ports/meta-pine64-luneos/pull/30 Feb 22 20:02:25 JaMa: I added the dtschema-wrapper because it wasn't in hardknott (or honister) before, if there now not needed anymore Feb 22 20:07:08 I've already removed it as well as dtc Feb 22 20:07:58 and exiv2, properties-cpp from meta-webos-ports as well Feb 22 20:08:16 good :) Feb 22 20:08:26 only apitrace and lvgl are waiting in PR (and I'm running pinephone build with kirkstone now to build test newer version of them) Feb 22 20:08:55 JaMa: so, luneos-recoveryui is building fine with newer lvgl ? Feb 22 20:09:14 build in progress, don't know yet Feb 22 20:12:21 I'd be surprised if it does build, when I looked a couple of months ago the gap was quite high Feb 22 20:27:47 in kirkstone there is also 2.6 trusted-firmware-a now available from meta-arm, but in honister they have only 2.5 while meta-pine64 has 2.6 Feb 22 20:28:22 but there is no rush, I've just run bitbake-layers show-overlayed and was surprised how many recipes are overlayed now Feb 22 20:28:32 but most of them are toolchain from meta-arm anyway Feb 22 20:38:08 2.6 should be fine Feb 22 20:38:21 So you can take from upstream if builds Feb 22 20:38:59 But I recall I had some issues somewhere so I decided to use a simplified recipe in meta-pine64 Feb 22 20:39:16 I think it was TFA Feb 22 20:59:24 out of curiosity, what's kirkstone? Feb 22 21:01:16 it's the next yocto release Feb 22 21:16:51 ah Feb 22 21:18:11 and that's the "mainline" linux you're using for non-Android devices? Feb 22 21:21:25 it's set of tools to create custom Linux distribution Feb 22 21:21:42 LuneOS is our custom Linux distribution built with Yocto/OpenEmbedded Feb 22 21:21:59 used by both mainline as well as android MACHINEs Feb 22 21:25:31 so what makes one platform "mainline" and another not? the kernel? Feb 22 21:28:10 yes, in the sense as we're using "mainline" here than the biggest differenence is kernel and low-level stuff around it Feb 22 21:29:02 if the LuneOS image contains Android rootfs in LXC, then it's not "mainline" MACHINE for us Feb 22 23:07:33 Tofe: luneos-recovery-ui/1.0-r0/recipe-sysroot/usr/include/lvgl/src/lv_conf_internal.h:41:14: fatal error: ../../lv_conf.h: No such file or directory Feb 22 23:08:04 will check tomorrow, u-boot is also failing to build now for pp Feb 23 01:03:18 Herrie: hey sorry still confused on the install instructions for pinephone. I have this image: luneos-dev-image-pinephone-20220125.wic.gz Feb 23 01:03:47 can i just `dd` this over to the sdcard after unzipping? Feb 23 01:03:55 also is this the right image? **** ENDING LOGGING AT Wed Feb 23 02:59:57 2022