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).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

#rockbox log for 2021-04-23

00:18:01***Saving seen data "./dancer.seen"
01:02:59 Join advcomp2019__ [0] (~advcomp20@unaffiliated/advcomp2019)
01:06:11 Quit advcomp2019_ (Ping timeout: 260 seconds)
01:22:25 Join ZincAlloy [0] (
01:26:41 Quit ZincAlloy (Ping timeout: 240 seconds)
01:32:50 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:909:ccbb:53e3:9ccf)
01:37:23 Quit ZincAlloy (Ping timeout: 248 seconds)
01:52:45 Join ZincAlloy [0] (
01:56:46 Quit ZincAlloy (Ping timeout: 240 seconds)
02:18:04***Saving seen data "./dancer.seen"
03:46:22 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
03:55:56 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan)
04:18:06***No seen item changed, no save performed.
06:18:10***No seen item changed, no save performed.
06:41:52 Quit bzed (Read error: Connection reset by peer)
06:44:11 Join bzed [0] (
07:28:00 Join Saijin-Naib [0] (
07:33:22 Join amachronic [0] (~amachroni@
07:35:27amachronicspeachy: I'm happy with moving the m3k to unstable.
08:02:22fs-bluebotBuild Server message: New build round started. Revision 39939a164b, 298 builds, 9 clients.
08:02:54speachyamachronic: okeydokey, it is done! congratulations btw
08:15:05fs-bluebotBuild Server message: Build round completed after 762 seconds.
08:15:08fs-bluebotBuild Server message: Revision 39939a164b result: 60 errors 120 warnings
08:18:13***Saving seen data "./dancer.seen"
08:24:26*speachy raises an eyebrow.
08:26:34speachylooks like the gcc 11 toolchain is generating some problems with simulator builds. Errors are all false positives from the log parser, but the warnings are legit.
08:43:29 Join chris_s [0] (
08:47:29fs-bluebotBuild Server message: New build round started. Revision 03695429cf, 298 builds, 9 clients.
08:47:57speachylet's see if this takes care of everything.
08:49:33chris_s@speachy Re pwr management changes: iPod color/photo (stock) looking good so far, too (except for what I mentioned earlier which seems to be a separate issue). I'm *fairly* confident but not certain yet that UDMA2 causes the same trouble as it does on the 4G though. "Unfortunately", *that* problem occurs rarely enough that I've found it difficult
08:49:34chris_sto systematically/quickly provoke or test for it on a player that I don't regularly use.
08:50:07speachyawesome. I didn't expect a regression on stick player (since I kept hte same sleep command)
08:50:45speachybut I wonder what the impact would be if we unconditionally used STANDBY_IMMEDIATE instead of SLEEP across the board
08:50:52speachythe 6g+ stuff already does that
08:53:23speachyI wonder if the UDMA2 stuff is related to dynamic cpu clocking −− if we have a path that downclocks the CPU while a transfer is in progress that could cause badness.
08:55:31speachyonce the build is green again (hopefully no other GCC11 issues remain) I'll merge that power management change
08:55:36speachychris_s: thanks for the sanity checking
08:56:26chris_ssure, would it help at all if I tested a build with dynamic cpu clocking disabled and UDMA 2 enabled to see if the problem remains?
08:56:44speachyI think so!
08:59:46fs-bluebotBuild Server message: Build round completed after 736 seconds.
08:59:48amachronicspeachy, I forgot to mention −− are the unstable ports supposed to have a bootloader build available?
08:59:49fs-bluebotBuild Server message: Revision 03695429cf result: 0 errors 90 warnings
09:01:28fs-bluebotBuild Server message: New build round started. Revision 0271c0ed36, 298 builds, 9 clients.
09:01:41speachydamnit, managed to not submit all three together
09:02:36speachyamachronic: Yeah.. I think it would be a good idead to generate a binary bootloader build.
09:03:23speachyit's not strictly necessary (some of the targets are only "unstable" because of very convoluted installation requirements) but we do want to allow folks to install without having to compile anything.
09:03:33speachybootloader and spl, I guess
09:04:31speachyhmm.. is it feasible to add in a queryable version number for the spl and bootloader? (ie somethign that can be read via rockbox's debug menu?)
09:04:49amachronicIt is, I just haven't gone through the trouble.
09:05:01amachronicAs of now, the bootloader will show the version if you boot without the SD card in.
09:05:21speachythat's good enough IMO
09:05:24amachronicand spl + bootloader should be built from same revision
09:05:56speachyif they're technically independent though, we could end up in a situation where someone mis-matches them.
09:06:27amachronicyes, but assuming we only provide sync'd up builds, then that's somebody else's fault for doing things wrong
09:06:52speachyI'm thinking purely of the support burden
09:06:58amachronicI might try to eliminate the separate SPL anyway, but I'm not sure how feasible it is.
09:07:15amachronicie. use linker tricks to make the SPL part of the normal bootloader build
09:08:19*speachy nods. Ideally!
09:08:36amachronicmainly the extra complications of slicing up the resulting binary are why I've not bothered
09:10:25amachronicalso some code is #ifdef'd due to SPL constraints and sorting it out is a PITA...
09:12:17amachronicafter adding USB the bootloader size is also pushing dangerously close to the limit, probably that needs to be fixed too or it will cause annoyances later
09:13:20fs-bluebotBuild Server message: Build round completed after 712 seconds.
09:13:23fs-bluebotBuild Server message: Revision 0271c0ed36 result: 0 errors 162 warnings
09:13:24fs-bluebotBuild Server message: New build round started. Revision aab72f969f, 298 builds, 9 clients.
09:24:43fs-bluebotBuild Server message: Build round completed after 679 seconds.
09:24:45fs-bluebotBuild Server message: Revision aab72f969f result: 0 errors 180 warnings
09:26:14fs-bluebotBuild Server message: New build round started. Revision 75d9393796, 298 builds, 9 clients.
09:28:42 Quit chris_s (Quit: Ping timeout (120 seconds))
09:30:32amachronichmm, maybe I should rework the bootloader & installation process a bit given that USB works now.
09:35:36 Quit amachronic (Quit: amachronic)
09:38:45fs-bluebotBuild Server message: Build round completed after 751 seconds.
09:38:47fs-bluebotBuild Server message: Revision 75d9393796 result: 0 errors 8 warnings
09:39:24_bilgusspeachy re - g#2057 I left a comment −− I still have the sample files reffd in the FS #13133 bug report if you wanna push to wards upstream opus
09:39:27fs-bluebot Opus files with embedded artwork 45.8KiB or larger skip near beginning (bugs, closed)
09:39:27fs-bluebotGerrit review #2057 at : Sync opus codec to upstream git by William Wilgus
09:39:35speachyok, final warning is in the opus code
09:40:47speachylet's see if upstream opus still has the same warning..
09:42:21_bilgusentirely possible its a warning from my AA fix
09:43:01_bilgusor even g#2231
09:43:03fs-bluebotGerrit review #2231 at : opus reset decoder on seek completion to prevent stack overflow by William Wilgus
09:48:13speachyno.. it's a possibly unintialized use of a variable
09:49:26speachya fixed array is initialized up to the index specified in a function argument, then passd into another function. presumably that other function might access it beyond the initialized boundary.
09:50:01speachy(newer compiler has better code flow analysis basically)
09:50:14_bilguslooking at the rebase commit it appears that the sync won't wipe out those fixes
09:51:04_bilgusand the targets I was initially worried about are pretty much gone too
09:51:13speachyI rebased that commit so I could see if this warning was already fixed upstream
09:51:55_bilgusmight as well push then sounds like a good reason
09:52:17_bilgustesting reqd' ofc
09:52:27speachygone how? I mean, we didn't drop anything other than hwcodec
09:54:43_bilgusthe clip v1 and fuze v1
09:54:52_bilguslike gone from the face of the earth
09:55:50_bilgusno sd card and 2mb of ram the flash is surely toasted
09:56:32_bilgusits the next on the chopping block when it doesn't fit anymore
09:56:52speachyfuzev1 has an sd card
09:57:14speachy(I have a busted one amongst my pile of v2s)
09:57:18_bilgusoh did it thought the v1s all had no sd
09:57:41speachyI think it was one the m200 or c200 series that lacked an sd card
09:57:44_bilguspresumeably its also has more ram then?
09:57:56speachyyeah, fuzev1 has same overall specs as v2
09:58:19speachyjust a better-integrated SoC (AMSv2 plus memory-on-package)
09:58:20_bilgusit probably was the bootdata patch shows which did and didn't have a sd
10:00:50speachywell, those sample file still play
10:00:55_bilgusThe clipv1, c200,e200,m200 all were removed due to space constraints in the firmware image
10:01:42_bilgusand later the e200 v1 was later re-added
10:01:50speachyIIRC those are our only 2MB targets too?
10:01:52_bilguslater later
10:02:05_bilgus2 for emphasis
10:03:47speachy2mb targets: logix_dax, c100, clip, m200v4, c200v2
10:04:25_bilguslogix_dax huh
10:04:52speachylogik_dax, rather
10:04:57speachyI wonder if that even compiles..
10:06:44_bilgusa 1 gb device and no sd card
10:07:09speachysame platform as the sansa c100
10:07:23_bilgusand runs off 1 AA
10:07:53_bilgusyeah rather than fix it I'd say bye bye
10:08:06_bilguslast mention of it was 2009
10:08:07 Quit pamaury (Ping timeout: 260 seconds)
10:09:05 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
10:09:37_bilguslooks like it never was finished
10:16:04speachynone of the tcc77x series targets even compile.
10:18:17***Saving seen data "./dancer.seen"
10:22:10speachyc100 was never finished, logidax doesn't link after the build errors are fixed, m200's keymap goes boom, and iaudio7 is even more broken
10:23:06fs-bluebotBuild Server message: New build round started. Revision 14c6bb798d, 298 builds, 7 clients.
10:23:20speachyok, landing opus. let's see what goes kaboom.
10:24:10speachyany objections to just nuking the entire tcc77x series? It's completely b0rked and I can't see anyone caring enough to recussitate them.
10:27:32_bilguslets ask on the forum to be sure but I see no reason to keep em
10:27:44speachythese never saw any release, ever
10:28:24_bilgusoh then just nuke em
10:34:46 Join ubervison [0] (~ubervison@2a02:aa12:b106:1b80:4978:337a:24bd:4bbc)
10:37:56speachyamachronic: with respect to M3K USB DMA, are the buffers used for the initial setup aligned correctly?
10:38:14speachyeg see usb_storage_init_connection()
10:38:32fs-bluebotBuild Server message: Build round completed after 926 seconds.
10:38:35fs-bluebotBuild Server message: Revision 14c6bb798d result: All green
10:47:48 Quit ubervison (Quit: Leaving)
10:55:32speachyshould probably nuke ifp7xx too since that was never finished.
11:12:04speachy_bilgus: g#3357
11:12:06fs-bluebotGerrit review #3357 at : Nuke all TCC77x targets: iAudio 7, Sansa C100, M200(v1-3), Logik DAX by Solomon Peachy
11:12:57speachyabout 7K lines removed total.
11:33:34speachyand g#3358, whick nukes about 4K lines.
11:33:37fs-bluebotGerrit review #3358 at : Nuke the nonfunctional iriver ifp-7xx port by Solomon Peachy
11:35:31 Quit pamaury (Ping timeout: 252 seconds)
11:39:06speachythe ifp790 had 256MB of storage...
11:39:14speachyand used an AA battery
12:06:01 Join amachronic [0] (~amachroni@
12:12:46amachronicspeachy re USB: I haven't checked alignment, but the code looks ok.
12:13:06amachronicIIRC, it's the GET_MAX_LUN control request which typically hangs
12:18:20***Saving seen data "./dancer.seen"
12:28:42bertriki remember there being something weird about scsi get_max_lun, some kind of off-by-one thing in the spec
12:35:58speachyso after those nukes go through, there are only three <=2MB targets in the tree: sansa clip, m200v4, and c200v2
12:41:27 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:2199:9df5:aae6:f93a)
12:49:07 Join MrZeus_ [0] (~MrZeus@2a02:c7f:a0aa:4400:e0b6:2d44:2a99:b71a)
13:00:01 Join lebellium [0] (
13:00:03 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.")
13:14:57 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan)
13:40:24_bilgustheir days are numbered
13:42:56speachyat least they compile!
13:46:23speachyThe "Elio TPJ-1022" doesn't even make it past 'make dep'
13:48:26_bilgusno point in dead weight
13:48:46speachywait, my ifp7xx nuking broke something
13:48:59speachytpj1022 doesn't build but it's mostly plugins.
13:51:38speachysomething in 3358 is busted... grr.
13:53:42speachyok, fixed.
13:55:59speachylast commit for this target was back in 2009.
13:57:56speachydisable plugins and it... still doesn't compile. vorbis codec doesn't fit in IRAM
14:03:39speachyNone of the Meizu targets (M3, M6SL, M6SP) build either
14:07:30speachyditto on the Lyre targets ("proto 1" and mini2440)
14:13:57 Join lemon_jesus [0] (~lemon_jes@
14:18:23***Saving seen data "./dancer.seen"
14:22:46lemon_jesushey gang, I don't know if this is the right place to put this, but I figured some of you might be interested. I've been working on a flash upgrade mod for the iPod Nano 3G for the past year. so far, I'm unsuccessful, but I've developed some neato firmware modding techniques. currently (thanks to the Rockbox bootloader), I'm able to put the NAND
14:22:46lemon_jesuschip's ID where the NAND_LBA number goes in the diagnostic menu, but I'm stumped as to why I'm unable to actually read and write to the chip. my guess is the chip is being addressed weird, so the next step for me is signal level debugging. I made a video about my progress: - if you have knowledge about NAND and NAND
14:22:46lemon_jesusabstraction layers, please shoot me a message <3
14:23:27speachyI don't think any one active here can help, but best of luck all the same!
14:24:06 Quit lebellium (Ping timeout: 240 seconds)
14:51:06 Join calebccff [0] (
14:51:07calebccfflemon_jesus: that's pretty cool
14:55:41TheLemonManlemon_jesus, I like your nick
15:29:17 Quit Acou_Bass (Remote host closed the connection)
15:31:58 Join Acou_Bass [0] (
15:58:11 Quit amachronic (Quit: amachronic)
16:03:28 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
16:15:14 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.")
16:18:26***Saving seen data "./dancer.seen"
16:21:05 Quit mendel_munkis (Remote host closed the connection)
16:21:19 Join mendel_munkis [0] (
16:22:26 Join amiconn_ [0] (jens@rockbox/developer/amiconn)
16:22:26 Quit amiconn (Killed ( (Nickname regained by services)))
16:22:26 Nick amiconn_ is now known as amiconn (jens@rockbox/developer/amiconn)
16:22:38 Join pixelma_ [0] (marianne@rockbox/staff/pixelma)
16:22:38 Nick pixelma is now known as Guest96352 (marianne@rockbox/staff/pixelma)
16:22:38 Quit Guest96352 (Killed ( (Nickname regained by services)))
16:22:38 Nick pixelma_ is now known as pixelma (marianne@rockbox/staff/pixelma)
16:23:07 Quit rogeliodh (Quit: The Lounge -
16:27:18 Join rogeliodh [0] (
16:38:34 Quit rogeliodh (Quit: The Lounge -
17:04:49 Join amachronic [0] (~amachroni@
17:11:13amachronicspeachy: just so you know, I'm going to rework the M3K bootloader (yet again...) so it's probably best to hold off releasing a binary.
17:16:34 Join ac_laptop [0] (~ac_laptop@
17:22:08 Quit amachronic (Quit: amachronic)
17:51:00 Quit calebccff (Quit: Idle timeout reached: 10800s)
18:05:03 Quit APLU (Ping timeout: 260 seconds)
18:08:27 Join APLU [0] (
18:14:56 Quit kugel (Ping timeout: 245 seconds)
18:15:58 Join kugel [0] (~kugel@rockbox/developer/kugel)
18:18:29***Saving seen data "./dancer.seen"
18:29:42 Join cockroach [0] (~blattodea@pdpc/supporter/active/cockroach)
18:31:20 Quit Acou_Bass (Quit: ZNC 1.8.2 -
18:42:20 Join Acou_Bass [0] (
18:48:27 Quit pamaury (Ping timeout: 260 seconds)
19:15:52 Quit ac_laptop (Ping timeout: 252 seconds)
19:32:46 Quit daswf852 (Ping timeout: 240 seconds)
19:51:51 Join ac_laptop [0] (~ac_laptop@
20:16:04 Quit ac_laptop (Ping timeout: 268 seconds)
20:16:39 Quit MrZeus_ (Ping timeout: 260 seconds)
20:18:33***Saving seen data "./dancer.seen"
20:26:45 Quit ZincAlloy (Quit: Leaving.)
20:29:15 Join massiveH [0] (
21:55:05 Quit Soap_ (Read error: Connection reset by peer)
22:07:52 Quit cockroach (Quit: leaving)
22:18:36***Saving seen data "./dancer.seen"
22:49:07 Join shuteye1 [0] (
22:54:54shuteye1Freshly rockboxed Xduoo X3 (original) running a daily build from last week. My line-out jack works for a while, then significantly lowers in volume at a random interval to the point where the audio is barely heard via an amplified source. Pressing one of the volume buttons on the player brings the volume back to normal level, is there any way to
22:54:55shuteye1make this behaviour stop such that the volume level does not decrease at all?
23:05:29 Quit Saijin-Naib (Ping timeout: 250 seconds)
23:32:29_bilgusshuteye1, there was recently a patch that messed with the LO level
23:32:31 Join rogeliodh [0] (

Previous day | Next day