| *** ChanServ sets mode: +v T4 | 02:32 | |
| *** ChanServ sets mode: +v T4 | 08:29 | |
| T4 | <adampigg> Is there a difference between sending 0/1 to /sys/class/rfkill.... And sending magic strings to /dev/rfkill?? | 10:35 |
|---|---|---|
| r0kk3rz | probably | 10:43 |
| *** ChanServ sets mode: +v T4 | 14:28 | |
| *** ChanServ sets mode: +v T4 | 20:19 | |
| piggz | Does sailfish-browser need something specific to render ... with the mesa based xiaomi mitab2, it just shows a white screen ... webcat works ok, in as much as webcat works | 21:12 |
| piggz | mal, r0kk3rz, ^ | 21:12 |
| r0kk3rz | not sure tbh | 21:18 |
| piggz | what does tbj use? is it a 'natice' port , or uses hybris? | 21:18 |
| r0kk3rz | pretty sure it uses hybris | 21:18 |
| TheKit | piggz, hybris | 21:20 |
| piggz | k | 21:20 |
| mal | piggz: sailfish-browser is somehow special, not sure how the rendering is done | 21:22 |
| piggz | another query is non-hybris GPS......weird thing with latte is, all the specs say there is no GPS, but it has a GPS chip according to the kernel, and rkfill has a gps device it an control. so, there is no android side to the gps, but can we use gpsd os similar? | 21:22 |
| mal | piggz: depends on how the gps is implemented, or if it even has gps, some devices have useless drivers in kernel | 21:23 |
| piggz | its a bcm47521 | 21:23 |
| piggz | it may not have antennas, just wondering what the device is | 21:23 |
| TheKit | eugenio, oh, just noticed you're the one who is g7 on GitHub | 21:35 |
| eugenio | yup! | 21:35 |
| TheKit | how does rpm-divert work for compatibility layer? I want to use it for tbj-like device | 21:35 |
| eugenio | it tries to work in a similar manner to dpkg-divert, but obviously in Debian dpkg is aware of diversions. With rpm I leverage triggers, which is not as elegant but it works rather well. It all boils down to: the compatibility layer registers triggers for the real HW adaptation packages as provided by Jolla, which are fired whenever they're upgraded. | 21:42 |
| eugenio | the standard usage flow is: when the Jolla-provided package fires the installation trigger, the trigger registered by the compatibility layer removes the diversions via rpm-divert. When the old package is removed (thus firing up the uninstallation trigger) the triggers calls rpm-divert to put the diversions back | 21:44 |
| eugenio | rpm is pretty twisted during upgrades - it installs first the new files for the up-to-date package (so the installation trigger gets called first), and then removes the old package (removing files that do exist anymore + upgrading the rest) | 21:47 |
| TheKit | thanks for explanation, good that it works then | 22:04 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!