Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2019-08-19

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:21Halamix2[m]Ah, build-crosstool-ng/configure has hardcoded version 3.X of bash, so 5 won't work
00:30:21w1d3m0d3speachy: 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:47speachyyeah, most is device-specitic code. I don't think there are any custom widgets either.
00:32:19w1d3m0d3I may volunteer in that case
00:32:31w1d3m0d3I really like rockbox so I think it'd be time well spent
00:38:47speachythat's how it always starts...
00:38:50w1d3m0d3Oh 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:27w1d3m0d3So, I guess the build server would need to be updated and that's ut?
00:41:15 Quit pystar89 (Ping timeout: 245 seconds)
00:46:07w1d3m0d3$ ldd RockboxUtility | grep Qt
00:46:08w1d3m0d3 => /lib/x86_64-linux-gnu/ (0x00007f5e64645000)
00:48:51Halamix2[m]is version 1.4.0 the newest one?
00:49:58Halamix2[m]cause it doen't seem like it uses qt at all
00:50:26w1d3m0d3sadly for some reason I can't communicate to my ipod to test it out :(
00:51:24Halamix2[m]maybe udev rules?
00:51:52w1d3m0d3I am getting an error in dmesg
00:52:25w1d3m0d3it seems that this brand new cable is defective, that's great
00:54:31w1d3m0d3I 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:15w1d3m0d3Fuck. Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
00:56:06w1d3m0d3yep, dirty bit set. god damn it
00:59:18w1d3m0d3ok, managed to fsck it
01:00:29***Saving seen data "./dancer.seen"
01:13:09w1d3m0d3right, fixed that issue thanks to the folk in ##linux
01:13:37w1d3m0d3Halamix2[m]: it's 1.4.0 but I built off of trunk
01:15:36 Join Soap [0] (~Soap@rockbox/staff/soap)
01:26:39w1d3m0d3it seems to work just the same, so the only question is why hasn't qt 4 been dropped yet
01:27:35w1d3m0d3I'm sure there are changes to be made like utilizing QStringLiterals and the new signal slot mechanisms but otherwise looks fine
01:29:59w1d3m0d3I may go over the codebase to fix up some of the warnings and legacy stuff
01:30:27w1d3m0d3The question is whether dropping qt 4 support would be acceptable in the developer's view
02:03:46 Join Galois [0] (
02:04:00 Quit Galois (Client Quit)
02:04:48 Join Galois [0] (
02:04:58 Part Galois
02:05:08 Join Galois [0] (
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:56speachyYou'd have to make a cost-benefit argument about how dropping QT4 is beneficial vs any potential downsides.
02:30:54speachyprobably not relevant on Windows, but eg do any common Linux distros not have QT5 out of the box or whatnot.
02:32:25speachyand, aisde from better fonts, does QT5 enable (or make easier) any functionality that's desired?
02:32:29speachyetc etc
02:33:15speachybecause 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] (
02:46:06w1d3m0d3speachy: 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:57bremnerfwiw, I think debian is finally getting rid of qt4 (qt5 is also there, of course)
02:47:23w1d3m0d3I 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:39w1d3m0d3and yes, distributions are dropping support for qt 5
02:47:55speachyIf RHEL6 and Debian oldstable have QT5, then there's probably no need to maintain QT4 any more.
02:48:31speachyI think my last serious mucking with a QT application was built with QT3 or 4.
02:49:30w1d3m0d3iirc qt 5.7 was present in stretch (current oldstable) back then, however I have not checked RHEL
02:49:51w1d3m0d3 version 5.7.1 and I am pretty sure that rest of Qt matches the version
02:50:04w1d3m0d3current debian stable (buster) has qt 5.11
02:53:34speachymy main concern are binary builds for the likes of Windows.
02:53:55w1d3m0d3why is that? licensing
02:54:02w1d3m0d3I have barely worked with Windows
02:54:16 Quit pystar89 (Ping timeout: 272 seconds)
02:54:54speachyno, just that we'd need to make sure it can still be built and generate a usable exectuable.
02:55:04speachywindows is always a special case
02:55:11w1d3m0d3I 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:59w1d3m0d3speachy: how does the build work currently on it? and in general, how does the build server work?
03:08:02speachy I don't know how/where rbutil is built.
03:08:13w1d3m0d3alright, thanks regardless
03:09:22speachyit's not handled by the usual build server/client combos.
03:09:40w1d3m0d3and how do those work? just out of curiosity
03:10:13speachyclients register themselves with the server, saying what their capabilities are (essentially, which toolchains they support)
03:10:49speachyserver then hands out individual builds to appropriate clients, which check the code out of git, do the build, and upload the results.
03:11:21speachyrepeat as necessary until all builds are complete (currently at 280)
03:11:49w1d3m0d3seems simple enough, can anyone become a client? if so, how do you know to trust the code
03:11:50speachythere's an additional set of builds that generate (some) voice packs and manuals, but I think that's done nightly.
03:13:19speachyyeah, 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:54speachythe acutal build script is fetched from git too, so it's not like the client is completely arbitrary.
03:14:54speachybut 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:32w1d3m0d3there were also those zip parent directory bugs found recently which were interesting
03:15:45w1d3m0d3I suppose really no damage could be done to the target devices?
03:16:03w1d3m0d3At least, that's how it was with iPods from what I could tell
03:17:15speachyI mean, short of stuxnet-level efforts I don't think there's much that can be done.
03:18:00speachyinject stuff into the zip file that could trigger a host PC 0-day or something like that. :)
03:18:18w1d3m0d3that happening is *definitely* not even close to likely
03:21:43speachyfar easier to just port scan for vulnerable IoT devices with hardcoded root passwords.
03:22:13w1d3m0d3:^) I mean, most (all?) of these players have no networking?
03:22:30speachya few of the latest crop have bluetooth but that's it.
03:23:27speachyI think calling the devices autistic is technically accurate.
04:40:45 Quit ufdm (Quit: Leaving)
05:00:10 Join pystar89 [0] (
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] (
05:41:27 Quit TheSeven (Ping timeout: 264 seconds)
05:41:51 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
05:57:28quadjfetAnybody know much about the Ingenic X1000 SoC?
05:57:48quadjfetIt is the cpu in the AGPTek Rocker. I am looking for a full programming manual
05:58:59quadjfetThere is already a preliminary rockbox port for the device
06:35:16quadjfetI am wondering how similar it is to the Ingenic JZ4725B
06:35:41quadjfetwhich has a full programming manual here:
06:36:07quadjfetor 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] (
07:10:59 Quit pystar89 (Ping timeout: 248 seconds)
07:15:07quadjfethelpful, thanks
07:15:42quadjfetfor 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] (
07:20:46quadjfetok, so that's helpful but it's the ISA
07:21:15quadjfetI still need something with all the register addresses
07:21:37quadjfetI need the 600+ page version
07:23:43quadjfetFor reference, the programming manual to JZ4760 is 917 pages
07:24:29 Quit ZincAlloy (Ping timeout: 252 seconds)
07:25:27 Quit ZincAlloy1 (Ping timeout: 268 seconds)
07:32:08 Join dys [0] (
07:42:53_Bilgusthe link one from our IRC log was dead but it gave me the magic incantation to find it :)
07:43:34quadjfetoh yeah. that's it. hits the spot
07:44:48 Join deevious [0] (~Thunderbi@
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] (
08:25:42 Quit TheSphinX^ (Ping timeout: 250 seconds)
08:25:42 Nick TheSphinX_ is now known as TheSphinX^ (
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] (
09:17:42 Quit pystar89 (Excess Flood)
09:28:00 Join petur [0] (~petur@
09:28:00 Quit petur (Changing host)
09:28:00 Join petur [0] (~petur@rockbox/developer/petur)
10:10:14 Join wodz [0] (
10:16:42 Join brasello [0] (
10:17:52 Join ZincAlloy [0] (
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] (
11:24:19 Join pystar89 [0] (
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] (
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] (
15:00:45***Saving seen data "./dancer.seen"
15:09:28 Join speachy [0] (40eebded@
15:13:46 Quit pl44c (Ping timeout: 245 seconds)
15:30:50 Join blackyus17 [0] (
15:36:40 Quit blackyus17 (Quit: AFK)
15:37:27 Join blackyus17 [0] (
15:44:15 Quit blackyus17 (Quit: AFK)
15:47:00 Join pystar89 [0] (
15:48:20 Join blackyus17 [0] (
15:52:42 Quit blackyus17 (Client Quit)
15:53:05 Join blackyus17 [0] (
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@
17:00:46***Saving seen data "./dancer.seen"
17:20:03 Quit petur (Ping timeout: 272 seconds)
17:58:11 Join tchan1 [0] (
17:59:23 Quit tchan1 (Client Quit)
17:59:43 Join tchan1 [0] (
18:00:14 Quit tchan1 (Client Quit)
18:00:39 Join tchan1 [0] (
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] (
18:03:04 Quit pystar89 (Excess Flood)
18:07:14 Join pystar89 [0] (
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] (
18:49:02 Quit pR0Ps (Quit: Quitting)
19:00:48***Saving seen data "./dancer.seen"
19:02:48 Join pR0Ps [0] (
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] (
20:20:13 Join pystar89 [0] (
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] (
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] (
22:01:06 Quit michaelni (Ping timeout: 248 seconds)
22:29:35 Join pystar89 [0] (
22:34:48 Quit pystar89 (Ping timeout: 272 seconds)
22:43:37 Join Strife89 [0] (
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)

Previous day | Next day