**** BEGIN LOGGING AT Sat Feb 03 03:00:01 2018 Feb 03 03:22:35 jeez, cgroups v2 is really taking ages Feb 03 03:26:09 but it seems the cgroup v2 cpu controller finally got merged in 4.15, and cgroup v2 device controller in HEAD Feb 03 07:20:47 yeah cgroups currently also creates issues for flatpak and the like Feb 03 07:23:10 hmm? Feb 03 07:24:25 (note: I don't think cgroups v2 is enabled by default in any distro, given that it still has too many limitations compared to v1) Feb 03 07:25:07 I mean, "unified" (v2-only) cgroup hierarchy in systemd as opposed to legacy or hybrid modes Feb 03 07:28:32 ah yeah, I can imagine flatpak and such would also very much like to see the switch to cgroups v2 finally happening Feb 03 07:28:57 since it supports safe delegation Feb 03 09:27:14 I have bought this wifi cape Feb 03 09:27:17 http://boardzoo.com/index.php/beaglebone/beaglebone-wl1835mod-w-chip-antenna.html#.WnWATu2kVC0 Feb 03 09:27:55 unable to use it even remotely. http://processors.wiki.ti.com/index.php/Using_the_WL18xx_Cape_with_BeagleBone_Black Feb 03 09:28:06 any help available ? Feb 03 09:35:29 I know the question is very vague, however to be specific, I was earlier using a simple wifi module based on UART and I wrote code for operating it Feb 03 09:36:37 this cape is something --> need an overview what broad steps are involved in configuring and setting up the cape Feb 03 09:40:32 hi Feb 03 11:04:05 tejas: the appropriate device tree declarations might suffice Feb 03 11:05:14 the wl18xx driver is already installed in debian images for the beaglebone (since the bbbw and bbgw use the same wireless chip) Feb 03 11:06:43 also it seems there's already a device tree overlay for this cape Feb 03 11:06:51 which actually means it should have worked plug&play Feb 03 11:07:46 oh Feb 03 11:07:52 do make sure you boot from SD card Feb 03 11:08:26 since the cape uses the pins which the bbb normally uses for eMMC Feb 03 11:09:18 wait Feb 03 11:11:01 nm, you can stop waiting. I got confused for a moment because I forgot that mmc1 is labeled as mmc2 in am33xx.dtsi (extremely annoying) Feb 03 11:55:58 zmatt : it seems like a new image needs to be compiled Feb 03 11:56:20 can you please point out the source device tree file Feb 03 11:57:30 or whether the code is already present in on of the already compiled dtbo"s available Feb 03 12:59:40 what are you basing that conclusion on? Feb 03 13:00:29 the dtbo should be included in any standard beaglebone image (see bbb.io/latest ) Feb 03 13:01:14 and it *should* get automatically loaded Feb 03 13:02:12 you may want to keep an eye on the serial console during boot to see what's going on Feb 03 13:04:01 (if you're using a recent enough image to have u-boot overlays that is. for older images the kernel log may suffice for debugging) Feb 03 13:04:50 you may want to be sure eMMC is disabled in /boot/uEnv.txt. I'm not sure whether that happens automatically. (it might when using u-boot overlays) Feb 03 13:05:59 ohh wait a minute that's not going to suffice Feb 03 13:06:17 possibly Feb 03 13:07:43 hmm. I don't know if things will get confused because eMMC and the wl18xx are connected to the same mmc bus. it may be necessary to ensure the eMMC is being held in reset, for which you'd first need to enable the eMMC's reset pin in its OTP config Feb 03 13:14:29 oh lol you're not even here anymore Feb 03 13:59:23 Hello all Feb 03 14:00:12 Is there any third party repo for installing QT 5.8+ for Debian stretch in beaglebone? Feb 03 14:15:50 5.9 is in debian buster Feb 03 14:17:36 you can add buster as secondary repository by adding these two files: https://pastebin.com/raw/ZBuK5Lg2 Feb 03 14:18:10 though mixing packages from different releases can be a tricky thing to do Feb 03 14:18:42 I'm assuming you're using debian stretch right now? Feb 03 14:20:09 you can also just switch to debian buster instead of mixing packages from stretch and buster Feb 03 15:05:42 zmatt, i installed debian buster but sgx drivers and other things related to it not worked! so i downgraded to debian stretch Feb 03 15:06:27 now i test your solution Feb 03 15:06:49 uhh, I don't see how the debian distro could have any influence on that Feb 03 15:08:57 i think any single package with minor change can influence! Feb 03 15:09:15 uh no, the sgx libs have very few dependencies Feb 03 15:12:44 but i had some problems in debian buster.in debian stretch i have not any problem Feb 03 15:35:07 zmatt, how to force apt to download and install newer version? or install from secondary repo? Feb 03 15:58:21 -t buster Feb 03 15:58:33 as option to apt-get install Feb 03 16:07:42 hello all, Feb 03 16:07:59 i wanted to know how I can use a timer functionality in writing my code Feb 03 16:08:24 speed is of the utmost importance so obviously i cannot use the "time" package Feb 03 16:08:42 are there any ways to efficiently read the loop time of my program?? Feb 03 16:11:40 will watchdog timers work Feb 03 16:17:46 (obviously don't mention which programming language you're even using) Feb 03 16:27:30 zmatt, thank you.now i installed qt 5.9. Feb 03 16:27:50 when i run qt apps, i got this error : Failed to move cursor on screen LVDS1: -14 Feb 03 16:28:01 i use eglfs Feb 03 16:29:35 Could not create buffer for cursor! / Failed to move cursor on screen LVDS1: -14 Feb 03 16:30:13 and QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Feb 03 16:41:33 Hello, how can I detect SOF with PRU? I tried using WBC but it seems to detects dominant bits in addition to SOF. So, is there a way that I can detect SOF only? Feb 03 16:41:54 The SOF of CANbus is what I'm referring to Feb 03 16:47:11 mehdi: maybe it's trying to use a hardware cursor? Feb 03 16:48:34 (which lcdc doesn't support) Feb 03 16:53:25 and XDG_RUNTIME_DIR is typically set as part of setting up a login session. it's normally not set in the environment of a service Feb 03 16:53:45 of course you can just set it properly yourself Feb 03 16:56:16 oh actually it's also set for user services apparently, just not for system services Feb 03 17:57:29 zmatt, should i set XDG_RUNTIME_DIR? i didn't have this problem in qt 5.7.1! is it QT related issue? Feb 03 18:10:52 I doubt it's important, it had a fallback anyawy Feb 03 18:17:22 actually, it's not new Feb 03 18:17:30 the warning already existed in 5.7 Feb 03 18:18:03 so something is querying for it that didn't used to Feb 03 18:20:27 i.e. something is calling QStandardPaths::standardLocations(QStandardPaths::RuntimeLocation) or QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) Feb 03 18:21:14 anyway, just make some private directory in /run for your service and set XDG_RUNTIME_DIR to that path, problem solved Feb 03 18:23:38 if you're using a systemd service, you can use the RuntimeDirectory=foo variable to have systemd automatically create /run/foo for your service Feb 03 18:46:52 zmatt, XDG error was solved by set the XDG_RUNTIME_DIR. but i don't know why my mouse not working.when i move the mouse the error repeated : Failed to move cursor on screen LVDS1: -14 Feb 03 18:50:31 like I said, that means it's trying to use a hardware cursor Feb 03 18:50:37 which lcdc doesn't support Feb 03 18:53:33 so there's something going wrong with the decision logic to use a hw cursor instead of a software cursor Feb 03 18:56:28 I dug a bit in the source code, there seems to be a config variable for it somewhere Feb 03 18:57:12 maybe google a bit for eglfs kms hwcursor or something Feb 03 18:57:23 "hwcursor" is the name of the config var, it needs to be set to false Feb 03 18:57:30 but I'm not sure where you set it Feb 03 18:57:36 anyway, I'm a bit distracted atm Feb 03 19:11:51 thank you so much for useful infos Feb 03 19:17:26 The KMS/DRM backend also supports custom configurations via a JSON file. Set the environment variable QT_QPA_EGLFS_KMS_CONFIG to the name of the file to enable this Feb 03 19:17:43 "hwcursor": false Feb 03 19:17:58 hope this work! Feb 03 19:21:45 woooooooooooooooooooooooow Feb 03 19:21:56 zmatt, THANK YOU THANK YOU Feb 03 19:22:08 works Feb 03 19:22:10 :D Feb 03 19:23:25 behold the power of... grepping the qtbase5 source code for the messages you got ;) Feb 03 19:24:38 you are right sir Feb 03 19:25:35 Thank you for spending time with me. Feb 03 19:25:47 you're welcome **** ENDING LOGGING AT Sun Feb 04 03:00:01 2018