**** BEGIN LOGGING AT Wed Jun 19 02:59:57 2019 Jun 19 03:49:46 JaMa: I'm new to these signature things. What would need to be adjusted for this to be gone? Jun 19 04:04:20 Morning BTW Jun 19 06:01:09 Herrie: pdm inherits webos_machine_impl_dep which makes it machine specific, pdm-plugin depends on pdm, but itself isn't machine specific Jun 19 06:01:39 Herrie: so either you need to modify pdm to stop using WEBOS_MACHINE_IMPL variable and drop the inherit or make pdm-plugin machine arch as well Jun 19 06:10:16 in OSE it wasn't an issue, because both recipes were restricted to build only on rpi3 Jun 19 06:13:03 JaMa: But when I drop webos_machine_impl_dep, will it still build a different binary for each arch? Jun 19 06:24:38 yes, but the binary might be wrong if the CMakeLists.txt use WEBOS_MACHINE_IMPL variable (which is usually the only reason for inheritting webos_machine_impl_dep Jun 19 06:26:34 or in this case they just blindly copy pasted the inherit from some other recipe.. Jun 19 06:26:54 Seems it doesn't in this case Jun 19 06:26:56 Let me fix that then Jun 19 06:28:40 Morning! Jun 19 06:29:38 JaMa: Done Jun 19 06:33:40 Tofe: Morning! Jun 19 06:34:54 Tofe: Pushed some core-app changes. Had those pending locally for a while it seems :P Never completed & pushed it ;) Jun 19 06:35:00 So did that yesterday evening Jun 19 06:38:02 so I guess it's already tested Jun 19 06:40:42 Yup :P Jun 19 06:40:47 Tested it on Desktop Chrome ;) Jun 19 06:41:50 I mainly changed non-existing links to something that DOES exist and created 2 mock files for it Jun 19 06:42:37 ok good Jun 19 06:43:14 Merely cosmetics but well ;) Jun 19 07:30:08 this random failing QA for qtquickcontrol* recipes is annoying Jun 19 07:37:52 Tofe: Yeah ;) Jun 19 07:38:00 But JaMa is on top of it ;) Jun 19 08:22:01 i am beginning to think it maybe my quassel core .. Jun 19 08:22:06 as opposed to freenode Jun 19 08:22:28 could be Jun 19 08:31:00 Tofe: btw. your patch for regdb didn't work Jun 19 08:31:28 I added: MACHINE_EXTRA_RDEPENDS = " \ Jun 19 08:31:28 linux-firmware Jun 19 08:31:28 wireless-regdb Jun 19 08:31:28 " Jun 19 08:32:20 and will have to look for a way to have a decent bnc ...i have a little pi running in my home 24x7 but the main problem is i don't have a public IP Jun 19 08:34:21 the linux-firmware also missed some firmware needed by the wifi Jun 19 08:38:18 saidinesh5: My mIRC on Windows is pretty stable :P Jun 19 08:39:07 lol.. i think my konversation would also be very stable but i need a BNC or somethig so when someone replies to my questions when i am away/sleeping, i can check them when i am back Jun 19 08:39:38 * saidinesh5 wonders if Sho_ is still maintaining konversation Jun 19 08:40:50 Afaik know he is, I'm soon packaging it for Alpine btw Jun 19 08:41:01 wait, wrong channel Jun 19 08:41:18 PureTryOut[m]: good morning, here, take a coffee Jun 19 08:41:21 Thought I was in #alpine-linux 🤔 Jun 19 08:41:39 lol Jun 19 08:41:57 That's disgusting lol, I'll go with a water instead Jun 19 08:43:13 saidinesh5: for me I included regdb in the image via a RDEPENDS on the recipe providing wifi firmware, and the latter was in RDEPENDS of the MACHINE; anyway, you just need to include it somewhere in the RDEPENDS chain Jun 19 08:43:58 Tofe: for me the wifi firmware was supposed to come via. linux-firmware which is part of openembedded-core i think? Jun 19 08:44:12 so what is the difference between MACHINE_RDEPENDS and RDEPENDS? Jun 19 08:45:57 saidinesh5: the former is directly a RDEPENDS on the MACHINE itself, so it'll be included in your target image whatever happens; the latter will be included in your image only if the recipe is included (directly or indirectly) Jun 19 08:46:09 Ahh Jun 19 08:46:32 so either way it should get included right? Jun 19 08:46:52 yes Jun 19 08:47:06 hmm.. odd.. then Jun 19 08:47:19 ohh also Jun 19 08:47:23 how did you try it at first ? with linux-firmware.bbappend ? Jun 19 08:47:26 i did run a couple of libdrmtest Jun 19 08:47:38 oh nah.. i added it to my machine.conf i think Jun 19 08:47:51 and good idea.. will try it via. linux-firmware.bbappend then Jun 19 08:48:26 wanted to actually add a patch to linux-firmware.bbappend Jun 19 08:49:31 like no point tossing in the nvidia and radeon firmwares for this tablet Jun 19 08:49:31 which linux-firmware recipe is it ? do you have an url? Jun 19 08:57:06 1 sec Jun 19 08:58:07 it was from openembedded-core .. (gimme a little while .. will have to power up the other machine) Jun 19 08:59:42 Should be this one: https://github.com/openembedded/openembedded-core/blob/warrior/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb#L264 Jun 19 09:09:39 Tofe: I'll create a table on the Wiki similar to what you did for Device Status for the OSE migration status, so we can keep track there as well. Based on my previous Google Sheets, new repos added and current status of migration of components Jun 19 09:18:35 saidinesh5: I see, yes the linux-firmware recipe is quite extensive. But it splits things up in several packages, and in RDEPENDS you specify packages Jun 19 09:18:48 this means that a bbappend wouldn't be the best solution here Jun 19 09:19:45 you'd better go for MACHINE_EXTRA_RDEPENDS = " [existing stuff] linux-firmware-bcm43430a0 " Jun 19 09:20:26 I forgot regdb MACHINE_EXTRA_RDEPENDS = " [existing stuff] linux-firmware-bcm43430a0 wireless-regdb" Jun 19 09:20:26 Tofe: ohh interesting Jun 19 09:21:38 Herrie: good idea Jun 19 14:43:16 Tofe: Not sure you saw this one, a bit old, but still has some interesting info: https://schd.ws/hosted_files/aglmmeu2018/35/AGL%20AMM%202018%20Dresden%20LG%20WebAppManager.pdf Jun 19 15:22:12 Tofe: Initial draft for colors: https://webos-ports.org/wiki/LuneOS-webOS-OSE_Migration_Status Jun 19 15:22:29 Working through my Excel now and can post the full table later ;) Jun 19 15:32:08 Herrie: for a moment there i thought you meant the LuneOS default theme when you said colors Jun 19 15:37:05 saidinesh: No, let's not use those colors for a theme LOL :P Jun 19 15:37:50 hopefully not Jun 19 15:42:23 Herrie: you don't use tab to autocommplete nicks in your IRC client? Jun 19 15:42:39 Ah wait I didn't know that feature exists LOL Jun 19 15:42:57 ohh .. it exists and is mandatory to make sure people always get your notifications Jun 19 15:43:08 Learned something new after almost 20 years of mIRC :P Jun 19 15:43:31 Or maybe 20+ years, don't remember when I started LOL Jun 19 15:44:46 you use windows as a daily PC? Jun 19 15:44:58 and wow.. i feel old now. it has been 10 years since i started using IRC Jun 19 15:46:40 Wait, you've typed out names for 20 years long on IRC? Jun 19 15:46:56 How did you not find this feature earlier? Basically every IRC client ever has had it lol Jun 19 15:47:38 LOL ;) Jun 19 15:47:50 and wow. .that's a horrifying realization. 20 years of typing names on IRC! Jun 19 15:48:04 Well I haven't been very active for all 20 years ;) Jun 19 15:48:13 Maybe last 7 and a bit in the beginning ;) Jun 19 15:49:44 Ahh Jun 19 15:53:19 Herrie: yes interesting Jun 19 15:54:05 starting my luneos work for the day... Jun 19 15:58:05 Tofe: how do i use bitbake -e to find IMAGE_FSTYPES where all it is being set? Jun 19 16:00:44 saidinesh5: What command are you using to create your image Jun 19 16:01:02 In general IMAGE_FSTYPES comes from openembedded-core layer in our builds Jun 19 16:01:03 MACHINE=intel64-tablet bitbake luneos-dev-image Jun 19 16:01:13 I see Jun 19 16:10:52 Herrie: so what could cause wireless-regdb to not install after i added it to MACHINE_EXTRA_RDEPENDS ? Jun 19 16:11:01 MACHINE_EXTRA_RDEPENDS = " \ Jun 19 16:11:01 linux-firmware-bcm43340a0 \ Jun 19 16:11:01 wireless-regdb \ Jun 19 16:11:01 " Jun 19 16:16:48 Do you have something like: https://github.com/webOS-ports/meta-pine64-luneos/blob/master/conf/machine/pinephone.conf#L16 Jun 19 16:18:15 i added that Jun 19 16:18:35 ohh Jun 19 16:18:44 wrong line Jun 19 16:20:16 NOt sure that's required, but I suspect it might be Jun 19 16:20:44 solving the brcm firmware one first Jun 19 16:20:50 that's my wifi chip anyway Jun 19 16:21:25 In general if you can post your whole layers that would help as well Jun 19 16:21:36 Understand it's WIP and hacky probably, but still ;) Jun 19 16:21:39 oh will do Jun 19 16:21:49 i just added meta-intel Jun 19 16:21:59 and then added meta-intel-luneos by myself to customize the machine Jun 19 16:22:02 and one sec Jun 19 16:22:20 Direct firmware load for brcm/brcmfmac-43430a0-sdio.txt failed with error -22 Jun 19 16:23:22 Also i don't need telephony stuff right? how do i disable that? Jun 19 16:23:26 that should also clean up some space too Jun 19 16:25:57 telephony = minimal Jun 19 16:26:03 Few mb's Jun 19 16:26:06 Ahh Jun 19 16:26:11 Wouldn't worry Jun 19 16:26:23 but adds rild and other stuff that may mess with the startup right? Jun 19 16:26:28 ofono and a few other bits Jun 19 16:26:32 yeah Jun 19 16:26:36 It's ok on qemu Jun 19 16:26:40 i see Jun 19 16:26:44 So should be for you too Jun 19 16:27:01 There were more issues without it Jun 19 16:27:08 i see Jun 19 16:27:15 okay how do i upload my changes btw. ? Jun 19 16:29:22 like which repos should i create in my github and add? Jun 19 16:30:56 Herrie: this line maybe important: MACHINE_FEATURES = "alsa apm keyboard rtc serial screen touchscreen usbgadget usbhost vfat ext2 ext3 wifi" Jun 19 16:31:00 where is this used? Jun 19 16:31:28 meta-intel-luneos should be enough Jun 19 16:31:45 Ah hold on then Jun 19 16:31:46 I don't think these are used really not sure Jun 19 16:35:17 Do you have SIM on your tablet? Or WiFi only? Jun 19 16:36:06 wifi only Jun 19 16:36:28 it's a 50$ tablet really lol. they jacked up the prices recently but this was once sold for 43 bucks too Jun 19 16:36:40 And they seemed to be coming from yocto directly Jun 19 16:36:51 https://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#ref-features-machine Jun 19 16:37:06 that explains why some sys/class stuff is missing Jun 19 16:40:37 building another image enabling them Jun 19 16:41:17 At our end we don't really rely on them AFAIK Jun 19 16:41:24 But could be you need them, not sure really ;) Jun 19 16:41:37 It never caused issues for me previously ;) Jun 19 16:42:42 i added acpi and efi Jun 19 16:42:50 like you dont use acpi in virtualbox anyway do you? Jun 19 16:43:00 and efi is probably already enabled for me via. meta-intel Jun 19 16:43:07 but enabling it again Jun 19 16:43:22 added hwcodecs and it is pulling in vaapi and gstreamer stuff Jun 19 16:44:43 Hehe :) Jun 19 16:45:36 its building Jun 19 16:45:39 brb Jun 19 16:53:01 fingers crossed Jun 19 17:10:30 meh Jun 19 17:12:48 meh ? Jun 19 17:13:09 Nothing changed.. still no regulatoru.db Jun 19 17:13:16 and no graphucs Jun 19 17:13:19 however..... Jun 19 17:13:29 found something interesting Jun 19 17:13:49 when running /usr/palm/applications/fingerterm/fingerterm Jun 19 17:13:55 with QT_QPA_PLATFORM=eglfs Jun 19 17:14:04 and EGL_PLATFORM=fbdev Jun 19 17:14:13 it goes Error could not initialize egl display Jun 19 17:14:28 and when i change EGL_PLATFORM=drm Jun 19 17:14:41 it goes: EGL library doesn't support Emulator extensions Jun 19 17:15:08 "Emulator extensions" ? what's that Jun 19 17:15:21 trying to figure that out Jun 19 17:15:56 "QT_QPA_EGLFS_INTEGRATION=none" ? Jun 19 17:16:06 (https://forum.qt.io/topic/79887/eglfs-problems-with-qt-5-9/2 ) Jun 19 17:17:00 or, maybe, another value Jun 19 17:17:58 "ls tmp-glibc/work/pinephone-webos-linux/luneos-dev-image/1.0-r0/rootfs/usr/lib/plugins/egldeviceintegrations/" will give you your current choices Jun 19 17:18:10 oops, not pinephone, obviously :D Jun 19 17:19:04 QT_QPA_EGLFS_INTEGRATION=eglfs_kms maybe? Jun 19 17:20:46 didn't work Jun 19 17:20:48 and new issue: Jun 19 17:21:00 after a little inactivity, the keyboard stops working Jun 19 17:21:28 unplugging and replugging shows teh dmesg stuff on the screen but not working Jun 19 17:22:16 Tofe: but why would it not drag in regulatory.db after adding it to my machine rdepends? Jun 19 17:22:26 that's a good question Jun 19 17:22:58 when i added wifi to the machine_features it added crda binary to the build iirc Jun 19 17:23:02 but still no regulatory.db Jun 19 17:23:40 ls tmp-glibc/deploy/ipk/all/wireless-regdb* give something? Jun 19 17:24:18 $ ls tmp-glibc/deploy/ipk/all/wireless-regdb* Jun 19 17:24:18 tmp-glibc/deploy/ipk/all/wireless-regdb_2019.03.01-r0_all.ipk tmp-glibc/deploy/ipk/all/wireless-regdb-dbg_2019.03.01-r0_all.ipk tmp-glibc/deploy/ipk/all/wireless-regdb-dev_2019.03.01-r0_all.ipk tmp-glibc/deploy/ipk/all/wireless-regdb-lic_2019.03.01-r0_all.ipk tmp-glibc/deploy/ipk/all/wireless-regdb-static_2019.03.01-r0_all.ipk Jun 19 17:25:36 in your rootfs, you're looking in /usr/lib/crda, right? Jun 19 17:25:50 oh not sure it was in dmesg actually Jun 19 17:26:01 the error message Jun 19 17:26:12 and i looked in lib/firmware then Jun 19 17:26:43 ah ok, yes, regulatory.bin isn't in there Jun 19 17:27:53 also i think my wireless card is not brcm but some realtek one Jun 19 17:27:57 https://github.com/hadess/rtl8723bs Jun 19 17:28:28 the same as on pinephone? Jun 19 17:28:49 could be.. dunno what pinephone has Jun 19 17:28:55 this one :) Jun 19 17:29:09 ohh Jun 19 17:29:44 getting you some dmesg Jun 19 17:30:16 kmstest says All ok! Jun 19 17:30:29 ah, that's a start Jun 19 17:30:47 yeah Jun 19 17:31:00 hold on Jun 19 17:31:04 will recompile Qt Jun 19 17:31:25 it's always an efficient way to spend some time :) Jun 19 17:31:35 I added this: EXTRA_OECONF_remove_intel = "-qpa wayland-egl" Jun 19 17:31:35 EXTRA_OECONF_append_intel = " --qpa=wayland" Jun 19 17:31:39 lol Jun 19 17:31:46 but i think this may no longer be needed Jun 19 17:32:09 also how do i force it to use linux 5.1 like pinephone? Jun 19 17:32:17 i suspect that will bring me some goodies Jun 19 17:33:02 looking at meta-intel for hints Jun 19 17:33:12 beware the double dashes you've put Jun 19 17:33:33 or is it intended Jun 19 17:34:02 oh i just copied that file from raspberry pi iirc Jun 19 17:34:23 ah, linux 5.1, that's easy, just say that your kernel provider is yocto-linux Jun 19 17:34:44 (or was it linux-yocto) Jun 19 17:34:54 meta-intel Jun 19 17:35:22 PREFERRED_VERSION_linux-intel_linuxstdbase ?= "4.19%" Jun 19 17:35:22 PREFERRED_VERSION_linux-intel ?= "4.19%" Jun 19 17:35:22 PREFERRED_VERSION_linux-intel-rt ?= "4.19%" Jun 19 17:35:22 linux-yocto it is Jun 19 17:35:24 interesting Jun 19 17:35:25 oh Jun 19 17:35:34 where/how do i say that? Jun 19 17:35:43 in your machine .conf Jun 19 17:36:06 but i think i am supposed to use intels' optimized config for this Jun 19 17:36:15 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto" Jun 19 17:36:20 ah, well Jun 19 17:36:26 then use that one :p Jun 19 17:37:02 but I don't know what versions are provided for linux-intel Jun 19 17:37:17 but it provides: linux-intel Jun 19 17:37:17 linux-intel_4.14.bb Jun 19 17:37:17 linux-intel_4.19.bb Jun 19 17:37:17 linux-intel-dev.bb Jun 19 17:37:17 linux-intel.inc Jun 19 17:37:18 linux-intel-rt_4.14.bb Jun 19 17:37:21 linux-intel-rt_4.19.bb Jun 19 17:37:23 linux-yocto_4.19.bbappend Jun 19 17:37:25 linux-yocto_5.0.bbappend Jun 19 17:37:27 linux-yocto_%.bbappend Jun 19 17:37:29 linux-yocto-dev.bbappend Jun 19 17:37:34 linux-yocto-rt_4.19.bbappend Jun 19 17:37:36 linux-yocto-rt_5.0.bbappend Jun 19 17:37:38 meta-intel-compat-kernel.inc Jun 19 17:37:40 ouch Jun 19 17:38:13 and it is selecting 4.19 Jun 19 17:38:22 yes, they provide some custo for linux-yocto 5.0 Jun 19 17:39:18 so if you say PREFERRED_PROVIDER_virtual/kernel = "linux-yocto" and PREFERRED_VERSION_linux-yocto ?= "5.0%" you should be on that one Jun 19 17:39:57 Ahhh Jun 19 17:45:16 recompiling Jun 19 17:47:11 might as well get some noodles meanwhile **** ENDING LOGGING AT Thu Jun 20 03:00:00 2019