--- Log for 19.08.119 Server: hitchcock.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 5 days and 5 hours ago 00.09.14 Quit krabador (Remote host closed the connection) 00.10.06 Join krabador [0] (~krabador@unaffiliated/krabador) 00.10.40 Quit krabador (Remote host closed the connection) 00.13.28 Join krabador [0] (~krabador@unaffiliated/krabador) 00.27.21 # Ah, build-crosstool-ng/configure has hardcoded version 3.X of bash, so 5 won't work 00.30.21 # speachy: the UI seems small enough to do that (I assume the 30k LOC is more related to handling various devices than actual UI code), but it's still a major change 00.30.47 # yeah, most is device-specitic code. I don't think there are any custom widgets either. 00.32.19 # I may volunteer in that case 00.32.31 # I really like rockbox so I think it'd be time well spent 00.38.47 # that's how it always starts... 00.38.50 # Oh wait, `You have to have Qt Version 4.5.0 or higher installed. Using Qt5 is supported as well. Since r22624 out-of-tree building is possible. You can still build in-tree.` 00.39.13 # * speachy chuckles. 00.39.27 # So, I guess the build server would need to be updated and that's ut? 00.39.31 # it* 00.41.15 Quit pystar89 (Ping timeout: 245 seconds) 00.46.07 # $ ldd RockboxUtility | grep Qt 00.46.08 # libQt5Widgets.so.5 => /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x00007f5e64645000) 00.48.51 # is version 1.4.0 the newest one? 00.49.58 # cause it doen't seem like it uses qt at all 00.50.26 # sadly for some reason I can't communicate to my ipod to test it out :( 00.51.24 # maybe udev rules? 00.51.52 # I am getting an error in dmesg 00.52.25 # it seems that this brand new cable is defective, that's great 00.54.31 # I seem to have gotten it in juust the right spot for it to work but I'm nervous about mounting it because I don't want the dirty bit to be set 00.55.15 # Fuck. Volume was not properly unmounted. Some data may be corrupt. Please run fsck. 00.56.06 # yep, dirty bit set. god damn it 00.59.18 # ok, managed to fsck it 01.00.29 *** Saving seen data "./dancer.seen" 01.13.09 # right, fixed that issue thanks to the folk in ##linux 01.13.37 # Halamix2[m]: it's 1.4.0 but I built off of trunk 01.14.15 # https://i.imgur.com/pUwASK3.png 01.15.36 Join Soap [0] (~Soap@rockbox/staff/soap) 01.26.39 # it seems to work just the same, so the only question is why hasn't qt 4 been dropped yet 01.27.35 # I'm sure there are changes to be made like utilizing QStringLiterals and the new signal slot mechanisms but otherwise looks fine 01.29.59 # I may go over the codebase to fix up some of the warnings and legacy stuff 01.30.27 # The question is whether dropping qt 4 support would be acceptable in the developer's view 02.03.46 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 02.04.00 Quit Galois (Client Quit) 02.04.48 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 02.04.58 Part Galois 02.05.08 Join Galois [0] (djao@efnet.math.uwaterloo.ca) 02.22.55 Quit krabador (Remote host closed the connection) 02.23.40 Join krabador [0] (~krabador@unaffiliated/krabador) 02.28.04 Quit krabador (Remote host closed the connection) 02.29.56 # You'd have to make a cost-benefit argument about how dropping QT4 is beneficial vs any potential downsides. 02.30.54 # probably not relevant on Windows, but eg do any common Linux distros not have QT5 out of the box or whatnot. 02.32.25 # and, aisde from better fonts, does QT5 enable (or make easier) any functionality that's desired? 02.32.29 # etc etc 02.33.15 # because basically, what we have today "works well enough" so one has to justify a potentially destabilizing change. 02.34.07 Join Soap_ [0] (~Soap@rockbox/staff/soap) 02.36.53 Quit Soap (Ping timeout: 258 seconds) 02.38.40 Join krabador [0] (~krabador@unaffiliated/krabador) 02.40.52 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 02.46.06 # speachy: to my awareness all up-to-date distributions come with qt 5.7 or higher (that was the state some years ago when I was distributing Qt-based software) 02.46.57 # fwiw, I think debian is finally getting rid of qt4 (qt5 is also there, of course) 02.47.23 # I personally can't think of any downsides to it, when it comes to Qt 5 improvements they come in the form of a better slot-signal system (no longer based on string comparisons, statically checked etc), QString got improved (IIRC the aforementioned QStringLiteral macro was added in 5) 02.47.39 # and yes, distributions are dropping support for qt 5 02.47.41 # 4* 02.47.55 # If RHEL6 and Debian oldstable have QT5, then there's probably no need to maintain QT4 any more. 02.48.31 # I think my last serious mucking with a QT application was built with QT3 or 4. 02.49.30 # iirc qt 5.7 was present in stretch (current oldstable) back then, however I have not checked RHEL 02.49.51 # https://packages.debian.org/stretch/qt5-qmake version 5.7.1 and I am pretty sure that rest of Qt matches the version 02.50.04 # current debian stable (buster) has qt 5.11 02.53.34 # my main concern are binary builds for the likes of Windows. 02.53.55 # why is that? licensing 02.54.02 # I have barely worked with Windows 02.54.16 Quit pystar89 (Ping timeout: 272 seconds) 02.54.54 # no, just that we'd need to make sure it can still be built and generate a usable exectuable. 02.55.04 # windows is always a special case 02.55.11 # I know right.. 02.56.07 Join terminalator [0] (~terminala@unaffiliated/terminalator) 03.00.32 *** Saving seen data "./dancer.seen" 03.02.26 Quit krabador (Remote host closed the connection) 03.02.59 # speachy: how does the build work currently on it? and in general, how does the build server work? 03.08.02 # I don't know how/where rbutil is built. 03.08.13 # alright, thanks regardless 03.09.22 # it's not handled by the usual build server/client combos. 03.09.40 # and how do those work? just out of curiosity 03.10.13 # clients register themselves with the server, saying what their capabilities are (essentially, which toolchains they support) 03.10.49 # server then hands out individual builds to appropriate clients, which check the code out of git, do the build, and upload the results. 03.11.21 # repeat as necessary until all builds are complete (currently at 280) 03.11.49 # seems simple enough, can anyone become a client? if so, how do you know to trust the code 03.11.50 # there's an additional set of builds that generate (some) voice packs and manuals, but I think that's done nightly. 03.13.19 # yeah, anyone can set up a build client. the server boots clients that error out or take too long. I don't think there's any real validation in place, beyond basic sanity checks (eg does the uploaded zip file contain whtt it's supposed to) 03.13.54 # the acutal build script is fetched from git too, so it's not like the client is completely arbitrary. 03.14.54 # but it is conceivable that a malicious client could DoS the server by sending it a bad zip file. But the actual binaries are only executed on a target device, so there's limited scope for shenanigans. 03.15.32 # there were also those zip parent directory bugs found recently which were interesting 03.15.45 # I suppose really no damage could be done to the target devices? 03.16.03 # At least, that's how it was with iPods from what I could tell 03.17.15 # I mean, short of stuxnet-level efforts I don't think there's much that can be done. 03.18.00 # inject stuff into the zip file that could trigger a host PC 0-day or something like that. :) 03.18.18 # that happening is *definitely* not even close to likely 03.21.43 # far easier to just port scan for vulnerable IoT devices with hardcoded root passwords. 03.22.13 # :^) I mean, most (all?) of these players have no networking? 03.22.30 # a few of the latest crop have bluetooth but that's it. 03.22.38 # fancy 03.23.27 # I think calling the devices autistic is technically accurate. 03.34.00 # lol 04.40.45 Quit ufdm (Quit: Leaving) 05.00.10 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 05.00.33 *** Saving seen data "./dancer.seen" 05.05.26 Quit pystar89 (Ping timeout: 245 seconds) 05.17.20 Join _Bilgus [0] (~Bilgus@unaffiliated/bilgus) 05.17.48 Quit Bilgus (Ping timeout: 268 seconds) 05.33.10 Join ufdm [0] (~ufdm@c-75-72-5-49.hsd1.mn.comcast.net) 05.41.27 Quit TheSeven (Ping timeout: 264 seconds) 05.41.51 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 05.57.28 # Anybody know much about the Ingenic X1000 SoC? 05.57.48 # It is the cpu in the AGPTek Rocker. I am looking for a full programming manual 05.58.59 # There is already a preliminary rockbox port for the device 05.59.43 # https://www.rockbox.org/wiki/AgptekRocker 06.35.16 # I am wondering how similar it is to the Ingenic JZ4725B 06.35.41 # which has a full programming manual here: http://startcev.spb.ru/jz4725/JZ4725B_pm.pdf 06.36.07 # or you can just search for "JZ4725B PM" if you don't want to click my link 06.42.31 Quit terminalator (Ping timeout: 245 seconds) 07.00.37 *** Saving seen data "./dancer.seen" 07.05.48 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 07.10.59 Quit pystar89 (Ping timeout: 248 seconds) 07.14.31 # <_Bilgus> quadjfet? https://www.setphaserstostun.org/ci20/X1000_M200_XBurst_ISA_MXU_PM.pdf 07.15.07 # helpful, thanks 07.15.42 # for reference, the "XDuooX3" has an Ingenic JZ4760 07.20.18 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:847a:54a6:a632:449b) 07.20.38 Join ZincAlloy1 [0] (~Adium@ip5f5acea4.dynamic.kabel-deutschland.de) 07.20.46 # ok, so that's helpful but it's the ISA 07.21.15 # I still need something with all the register addresses 07.21.37 # I need the 600+ page version 07.23.43 # For reference, the programming manual to JZ4760 is 917 pages 07.23.45 # https://www.rockbox.org/wiki/pub/Main/IngenicJz47xx/JZ4760_pm.pdf 07.24.29 Quit ZincAlloy (Ping timeout: 252 seconds) 07.25.27 Quit ZincAlloy1 (Ping timeout: 268 seconds) 07.32.08 Join dys [0] (~dys@tmo-108-232.customers.d1-online.com) 07.42.01 # <_Bilgus> quadjfet https://github.com/JaminCheung/x-loader/blob/master/documents/cpu/X1000_PM_20160113.pdf 07.42.53 # <_Bilgus> the link one from our IRC log was dead but it gave me the magic incantation to find it :) 07.43.34 # oh yeah. that's it. hits the spot 07.43.52 # T.Hanks 07.44.06 # <_Bilgus> np 07.44.48 Join deevious [0] (~Thunderbi@193.226.142.214) 07.55.21 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:398d:7281:bfe8:12f3) 07.59.40 Quit ZincAlloy (Ping timeout: 252 seconds) 08.19.51 Quit TheSeven (Ping timeout: 264 seconds) 08.23.25 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 08.24.04 Join TheSphinX_ [0] (~briehl@srv001.nosupamu.de) 08.25.42 Quit TheSphinX^ (Ping timeout: 250 seconds) 08.25.42 Nick TheSphinX_ is now known as TheSphinX^ (~briehl@srv001.nosupamu.de) 08.52.18 Quit dys (Ping timeout: 248 seconds) 09.00.39 *** Saving seen data "./dancer.seen" 09.03.31 Join dys [0] (~dys@2003:5b:203b:100:a64c:c8ff:fef4:13a6) 09.17.42 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 09.17.42 Quit pystar89 (Excess Flood) 09.28.00 Join petur [0] (~petur@80.169.83.226) 09.28.00 Quit petur (Changing host) 09.28.00 Join petur [0] (~petur@rockbox/developer/petur) 10.10.14 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 10.16.42 Join brasello [0] (~brasello@anon-35-101.vpn.ipredator.se) 10.17.52 Join ZincAlloy [0] (~Adium@ip5f5acea4.dynamic.kabel-deutschland.de) 10.22.41 Quit ZincAlloy (Ping timeout: 272 seconds) 10.29.11 Quit foolsh (Ping timeout: 245 seconds) 11.00.40 *** Saving seen data "./dancer.seen" 11.18.52 Join vmx [0] (~vmx@ip5f5ac62a.dynamic.kabel-deutschland.de) 11.24.19 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 11.30.42 Quit pystar89 (Ping timeout: 248 seconds) 11.56.16 Quit quadjfet (Quit: Leaving) 12.18.58 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:180e:c592:5697:c097) 12.23.18 Quit ZincAlloy (Ping timeout: 252 seconds) 13.00.42 *** Saving seen data "./dancer.seen" 13.38.24 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 13.44.11 Quit pystar89 (Ping timeout: 245 seconds) 13.57.02 Quit GeekShadow (Ping timeout: 268 seconds) 14.06.46 Quit speachy (Remote host closed the connection) 14.16.06 Join foolsh [0] (~quassel@c-73-44-71-112.hsd1.mi.comcast.net) 15.00.45 *** Saving seen data "./dancer.seen" 15.09.28 Join speachy [0] (40eebded@64.238.189.237) 15.13.46 Quit pl44c (Ping timeout: 245 seconds) 15.30.50 Join blackyus17 [0] (~blackyus1@a24.f.t4vps.eu) 15.36.40 Quit blackyus17 (Quit: AFK) 15.37.27 Join blackyus17 [0] (~blackyus1@a24.f.t4vps.eu) 15.44.15 Quit blackyus17 (Quit: AFK) 15.47.00 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 15.48.20 Join blackyus17 [0] (~blackyus1@a24.f.t4vps.eu) 15.52.42 Quit blackyus17 (Client Quit) 15.53.05 Join blackyus17 [0] (~blackyus1@a24.f.t4vps.eu) 15.58.46 Quit wodz (Ping timeout: 245 seconds) 16.03.14 Quit pystar89 (Ping timeout: 248 seconds) 16.31.02 Quit asaba (Ping timeout: 246 seconds) 16.37.14 Join asaba [0] (~asaba@103.113.159.184) 17.00.46 *** Saving seen data "./dancer.seen" 17.20.03 Quit petur (Ping timeout: 272 seconds) 17.58.11 Join tchan1 [0] (~tchan@c-98-206-136-82.hsd1.il.comcast.net) 17.59.23 Quit tchan1 (Client Quit) 17.59.43 Join tchan1 [0] (~tchan@c-98-206-136-82.hsd1.il.comcast.net) 18.00.14 Quit tchan1 (Client Quit) 18.00.39 Join tchan1 [0] (~tchan@c-98-206-136-82.hsd1.il.comcast.net) 18.01.20 Quit tchan (Disconnected by services) 18.01.43 Quit tchan1 (Client Quit) 18.02.01 Join tchan [0] (~tchan@lunar-linux/developer/tchan) 18.02.22 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 18.03.04 Quit pystar89 (Excess Flood) 18.07.14 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 18.12.56 Quit pystar89 (Ping timeout: 245 seconds) 18.16.49 Join GeekShadow [0] (~antoine@reactos/tester/GeekShadow) 18.17.56 Join ZincAlloy [0] (~Adium@2a02:8108:9440:dfc:1e6:3210:ef9c:d12b) 18.18.02 Quit dys (Ping timeout: 264 seconds) 18.32.34 Join dys [0] (~dys@tmo-087-39.customers.d1-online.com) 18.49.02 Quit pR0Ps (Quit: Quitting) 19.00.48 *** Saving seen data "./dancer.seen" 19.02.48 Join pR0Ps [0] (~pR0Ps@orlnon0608w-lp130-01-70-53-101-203.dsl.bell.ca) 19.05.41 Join quadjfet [0] (quadjfet@gateway/vpn/privateinternetaccess/quadjfet) 19.11.57 Quit vmx (Remote host closed the connection) 19.35.44 Join krabador [0] (~krabador@unaffiliated/krabador) 19.50.43 Join lebellium [0] (~lebellium@89-92-69-110.hfc.dyn.abo.bbox.fr) 20.20.13 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 20.25.50 Quit pystar89 (Ping timeout: 245 seconds) 20.44.01 Join petur [0] (~petur@rockbox/developer/petur) 20.54.06 Quit brasello (Ping timeout: 272 seconds) 20.55.42 Join brasello [0] (~brasello@anon-35-207.vpn.ipredator.se) 21.00.52 *** Saving seen data "./dancer.seen" 21.31.41 Quit krabador (Remote host closed the connection) 21.41.09 Quit speachy (Ping timeout: 260 seconds) 21.59.04 Join michaelni_ [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 22.01.06 Quit michaelni (Ping timeout: 248 seconds) 22.29.35 Join pystar89 [0] (~pystar89@ip5f58d956.dynamic.kabel-deutschland.de) 22.34.48 Quit pystar89 (Ping timeout: 272 seconds) 22.43.37 Join Strife89 [0] (~quassel@adsl-74-250-150-177.ags.bellsouth.net) 23.00.53 *** Saving seen data "./dancer.seen" 23.18.15 Quit petur (Remote host closed the connection) 23.32.03 Quit ZincAlloy (Quit: Leaving.) 23.33.50 Quit dys (Ping timeout: 246 seconds) 23.49.04 Quit lebellium (Quit: Leaving)