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 2020-10-23

00:00:26_bilgus__hey look I have an abandoned patch from last time
00:08:58_bilgus__wow that was 500 bytes
00:09:12_bilgus__wonder if I can squeeze it a bit further
00:14:53_bilgus__speach no boot loaders use %z or %p think they are important enough to leave?
00:15:49_bilgus__I feel like size_t can be cast to lomg and %p can be worked around with %x
00:15:55_bilgus__oops speachy
00:26:07 Quit pixelma (Quit: .)
00:26:07 Quit amiconn (Quit: - Chat comfortably. Anywhere.)
00:28:42 Join amiconn [0] (jens@rockbox/developer/amiconn)
00:28:43 Join pixelma [0] (marianne@rockbox/staff/pixelma)
00:38:17efqw20:12:45, 72765, 000%, 00:-1, 3411
00:38:30efqwoh wow this thing really did manage 20hrs
00:42:23***Saving seen data "./dancer.seen"
00:44:43_bilgus__ g#2884
00:44:45fs-bluebot_Gerrit review #2884 at : ClipPlus BOOTLOADER DONT FIT! by William Wilgus
01:28:24 Quit Oksana (Ping timeout: 272 seconds)
01:42:28 Join Oksana [0] (~Wikiwide@Maemo/community/ex-council/Wikiwide)
02:13:58_bilgus__Beat it by 400 bytes
02:14:16_bilgus__assuming removing diacritics don't mess up the bootloaders...
02:42:24***Saving seen data "./dancer.seen"
02:46:12 Join Stanley00 [0] (~Stanley00@unaffiliated/stanley00)
02:50:12Stanley00efqw: hmm, isn't 3.4V consider dangerous for lipo battery?
02:53:18 Quit toruvinn (Ping timeout: 260 seconds)
02:54:21 Quit Stanley00 ()
02:54:42 Join Stanley00 [0] (~Stanley00@unaffiliated/stanley00)
02:57:32Stanley00That's why last time I stop the benchmark when my m5 report at 5% and voltage goes slightly below 3.5V
03:01:44efqwI think 3v4 is fine.
03:05:35efqwPeople run batteries to 3v0 all the time
03:06:09efqwYou'll only get cell damage at 2.xV afaik
03:09:30efqw3v4 is actually quite conservative imo and it's a good thing
03:15:39Stanley00 I was just paranoid a little, 'cause most digram show a drop down significant when come to below 3.5v
03:15:53Stanley00But yeah, readinh the wiki state it fine though
03:17:15efqwthese batteries are not linear devices, so you get diminishing returns after you go below 3v5
03:18:32efqwbut getting lower energy per 0.1v isn't indicative of potential cell damage :P
03:33:32 Quit ender| (Ping timeout: 260 seconds)
03:36:26 Join ender| [0] (~ender1@2a01:260:4094:1:6045:6fff:fedd:cbf3)
03:36:50 Join prof_wolfff [0] (
03:37:39 Join toruvinn [0] (
03:39:11 Join edhelas [0] (9d94237298@2a01:7c8:aab8:6b9:5054:ff:fec9:fd84)
03:40:25edhelashi everyone o/
03:47:48edhelasas I know a bit more how to handle C by now I would like to dive back in
03:59:54 Quit fauweh (Quit: )
04:00:21 Join fauweh [0] (
04:06:44 Quit prof_wolfff (Ping timeout: 272 seconds)
04:18:29 Join prof_wolfff [0] (
04:20:54 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
04:35:39 Part efqw
04:35:41 Join efqw [0] (uid412670@gateway/web/
04:42:26***Saving seen data "./dancer.seen"
04:44:12wodzspeachy: Good news. 1) I figured out why my battery looked like flat dead. Usb cable generated HUGE voltage drop (3.8V at the player end). This was enough to fool player to think it is charging but way too low for charging circuit to operate. 2) bluetoothd dying was probably related to the low battery level. 3) parametrized config in asound.conf is working fine. At least aplay started to understand bluetooth device string
04:47:37 Quit pamaury (Ping timeout: 264 seconds)
04:51:32wodzspeachy: The bad news is that current version of agptek firmware does not ship libbluetooth shared objects
04:56:47efqwoh wow, that's some *horrible* usb cables you've got there
05:00:11edhelasI have some issues to setup my toolchain, if someone could assist me
05:00:19edhelasI'm on Debian testing
05:00:27edhelas$ ./
05:00:27edhelasROCKBOXDEV: "makeinfo" is required for this script to work.
05:00:27edhelasROCKBOXDEV: "libtool" is required for this script to work.
05:00:27DBUGEnqueued KICK edhelas
05:00:27edhelasROCKBOXDEV: "flex" is required for this script to work.
05:00:27edhelasROCKBOXDEV: Please install the missing tools and re-run the script.
05:01:15edhelasi've installed all the packages listed on that page
05:03:40 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
05:07:48edhelas(ok my bad, missed a few more packages)
05:29:03 Quit pamaury (Ping timeout: 260 seconds)
05:30:18 Join vmx [0] (
06:11:16edhelasgot that
06:11:17edhelasROCKBOXDEV: applying patch rockbox-multilibs-noexceptions-arm-elf-eabi-gcc-4.9.4.diff
06:11:17edhelaspatching file gcc/config/arm/t-arm-elf
06:11:17edhelasHunk #1 succeeded at 64 with fuzz 2 (offset 20 lines).
06:11:17edhelasHunk #2 FAILED at 61.
06:11:17***Alert Mode level 1
06:11:17edhelas1 out of 2 hunks FAILED −− saving rejects to file gcc/config/arm/t-arm-elf.rej
06:11:18***Alert Mode level 2
06:11:18edhelaspatching file libgcc/config/arm/t-bpabi
06:11:18***Alert Mode level 3
06:11:18edhelaspatching file libgcc/
06:14:47edhelasspeachy it seems that this patch was introduced by you recently ? ^
06:17:50 Join Rower [0] (
06:21:19***Alert Mode OFF
06:24:27 Quit danielp3344 (Quit: killed)
06:24:28 Quit kadoban (Quit: killed)
06:24:44 Quit blbro[m] (Quit: killed)
06:33:06wodzspeachy: magic sits in bt-connect utility. Running it makes bt audio work
06:33:55 Join blbro[m] [0] (blbrostrat@gateway/shell/
06:42:27***Saving seen data "./dancer.seen"
06:45:38wodzOk. Missing link is calling org.bluez.AudioSink.Connect method on connected device.
06:52:02 Join danielp3344 [0] (danielp334@gateway/shell/
06:52:03 Join kadoban [0] (kadobanmat@gateway/shell/
07:04:18 Join pamaury [0] (
07:04:19 Quit pamaury (Changing host)
07:04:19 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
07:13:35speachyedhelas: I'm not sure why that patch failed; quite a few of us have built those toolchains fine with what's committed.
07:13:40edhelasok i found the issue, i'll propose a patch soon
07:14:04edhelas-@@ -56,8 +61,8 @@
07:14:04edhelas+@@ -61,8 +61,8 @@
07:27:17speachywodz: glad the magic pieces are falling into place. do you know if BT audio is fixed @44KHz?
07:30:01speachy_bilgus__: IIRC none of the strings in the bootloaders go through the translation layer, and even if they did, there's no way to load non-english languages anyway.
07:32:42speachyso yeah, no text scrolling, no non-engrish, and the only text output should be errors anyway.
07:32:56speachygranted the "bootloaders" in the hosted ports are fancier
07:45:10 Join massiveH [0] (
07:49:54fs-bluebot_Build Server message: New build round started. Revision 7c06a9e, 293 builds, 9 clients.
08:00:49speachy_bilgus__: We should add some sort of mkamsboot/fw patching pass somewhere.
08:01:16speachyand if we don't already have some sort of mirror of all (eg) sandisk firmware updates, it's only a matter of time before they're taken offline due to sheer obsolescence.
08:05:09fs-bluebot_Build Server message: Build round completed after 916 seconds.
08:05:14fs-bluebot_Build Server message: Revision 7c06a9e result: All green
08:18:10wodzspeachy: I don't know.
08:38:21 Quit massiveH (Quit: Leaving)
08:42:28***Saving seen data "./dancer.seen"
08:43:00speachywodz: basiclly we'd have to disable or override playback rate selection to match what the BT device can consume
09:27:46braewoodsspeachy: arguably also true for iriver H100 and H300
09:28:03braewoodsthey're still available from their website, but for how long?
09:28:34braewoodsi'm also looking into ways to update the H10 offline but no luck so far.
09:28:57braewoodsthe only way i found involved using their tool that downloads it from the network
09:29:22braewoodsmirroring firmware updaters that can be used offline isn't a bad idea
09:42:20fs-bluebot_Build Server message: New build round started. Revision 186dbb4, 293 builds, 9 clients.
09:47:50_bilgus__speachy so add the mkamsboot part?, I think its fine to create them but I feel we should send it to devnull
09:48:19speachy_bilgus__: yeah, though we need an OF image to go with it?
09:55:17fs-bluebot_Build Server message: Build round completed after 778 seconds.
09:55:19fs-bluebot_Build Server message: Revision 186dbb4 result: All green
09:59:02_bilgus__wodz wb, I plan to start making the UI side on the rocker sometime this week I'll probably mock it up using lua first
09:59:45_bilgus__oh yeah I need to see why lua actions don't work on the rocker
10:07:50speachyok, the SDUC adds/extends CMD22 to include the extra 6 bits of addressing, and CMD41 is tweaked to add explicit flags for >2TB reporting.
10:08:53speachyso other than teh disklabel/filesystem issues, the changes needed to enable >2TB cards are pretty minor.
10:09:53_bilgus__are there any yet or just looking forward?
10:11:26speachylargest uSDs I'm seeing are 1TB.
10:13:36speachyhmm, I wonder what the upper limit of those iFlash duo/quad adapters is?
10:14:27_bilgus__oh yaeh so thje quad could potentially give you 4TN then nice, but wozer
10:14:50speachycan't imagine they can handle SDUC cards, but they could easily export a 4TB drive today, in theory.
10:14:53edhelasit will also take days to fill it using the USB2.0
10:15:31_bilgus__at $75-100 a card that'd be an $$$ investment atm
10:16:17_bilgus__not that I haven't spent several hundred for less :P
10:16:24speachy75-100? cheapest I see is $250 for 1TB. :)
10:17:21_bilgus__oh I figured they had gone down a tier already $100 next year then :p
10:25:44 Join johnb7 [0] (
10:32:22johnb7speachy I got me a used Walker. I turned out it had no usb socket :-( Assuming the back is similar to the F20 that lebellium pointed to, how would you attempt to open the case? Heat the glass and metal frame and then try to pry the glass?
10:34:55speachyheat the glass to soften the adhesive, and pull/pry it off, expsing the screws underneat
10:36:06johnb7yep, that's what I thought I should do
10:36:56speachyshouldn't take much heat, and use plastic tools, etc etc..
10:37:41_bilgus__re the rocker, lua action failure because it can't get a timer
10:38:16_bilgus__what got added to the hosted targets that used up the timers?
10:38:40speachynothing that I can recall.. did this ever work?
10:42:26_bilgus__I upped the priority on it and it still didn't succeed so I'll check taht the MACROS are intact that calculates cycles
10:42:32***No seen item changed, no save performed.
10:44:15_bilgus__HAHA thats it
10:44:19speachylast change to the timer code was something you did in 2019.
10:46:10 Quit pamaury (Quit: Konversation terminated!)
10:46:33_bilgus__TIMER_FREQ macro
10:50:00speachyso it gets fixed at 1MHZ on hosted platforms
10:55:45 Quit Moarc (Ping timeout: 240 seconds)
10:57:31 Quit johnb7 (Ping timeout: 265 seconds)
10:59:05_bilgus__yeah they are intact weird it shows 50000 for period and TIMER FREQ = 100000
10:59:48_bilgus__yet when its supplied to timer register it fails but if I set it to 10000 it works
11:02:57 Join Moarc [0] (
11:11:00_bilgus__hmm are ints 32 bits on your hosted platforms?
11:11:57speachystandard 32-bit linux
11:12:06_bilgus__looks like overflow in the cycles calculation
11:12:09speachyso int = long = int32_t
11:12:34speachycpufreq is 1GHz
11:12:48speachyso it wouldn't take much to overflow
11:13:25_bilgus__#define cycles_to_microseconds(cycles) \ ((int)((1000000*cycles)/TIMER_FREQ))
11:15:27_bilgus__knock off 2 zereos and divide by 100
11:20:58_bilgus__yay that did it
11:21:16_bilgus__weird that I just up and stopped maybe clocking changes?
11:26:15 Join J_Darnley [0] (
11:28:23 Quit jdarnley (Ping timeout: 260 seconds)
11:29:04speachyprobably something I did
11:33:16_bilgus__being that we don't check for timers failing much through the code I wonder what else wasn't ticking
11:33:46speachywell, this might fix a bunch of issues.
11:33:54speachymight do nothing. :D
11:35:12fs-bluebot_Build Server message: New build round started. Revision 3a7a46d, 293 builds, 9 clients.
11:35:22_bilgus__gonna find out :p
11:36:19_bilgus__I have to go find a micro usb cable or drive home to get one before I can test the Clip+ bootloader
11:37:27_bilgus__once I've done that I'll rework the lcd_fb patch to account for the new parent
11:38:00_bilgus__oh and i'll fix those comments you mentioned thanks btw helps to have someone else look
11:38:37 Quit bzed (Ping timeout: 264 seconds)
11:45:37_bilgus__mini usb cable*
11:46:35speachywas about to say.. :D
11:46:55speachyI have an entire assortment of cables permanently hanging off my desk hub
11:49:05 Join bzed [0] (
11:50:10_bilgus__yeah I forgot to grab it the last time when I grabbed the Clip+
11:50:21fs-bluebot_Build Server message: Build round completed after 909 seconds.
11:50:23fs-bluebot_Build Server message: Revision 3a7a46d result: All green
11:52:05_bilgus__so I was looking at my pared version of putsofs from the bootloader and I started thinking oh no I wonder if font_lock actually unlocks thje bits of the font for reading so I went and found it in the source
11:52:26speachywhat triggered this was probably my fixing a bunch of incorrect CPU_FREQ definitions
11:52:27_bilgus__void font_lock(int font_id, bool lock)
11:52:27_bilgus__ (void)font_id;
11:52:27DBUGEnqueued KICK _bilgus__
11:52:27_bilgus__ (void)lock;
11:52:36_bilgus__nope no issue there!
11:54:04_bilgus__speachy no worries there I'm actually surprised it wasn't caught by that lint run you did
11:55:56speachyso the math "worked" but the delays were all jacked
11:55:59_bilgus__the linting −− sounds like a stephen king novel
11:56:26speachy"the linting of rockbox place"
11:56:39_bilgus__I'd read it
11:57:14speachy(coming soon to hulu plus)
11:57:29speachy(because not even netflix would touch it...)
12:00:59_bilgus__what were the plugins crashing on hosted? I bet those all have timers :)
12:01:42speachyI know a couple of 'em were probably the viewport issues you've been fixing
12:02:59_bilgus__huh fire doesn't exit on the rocker
12:03:16_bilgus__was always the case or did I break it?
12:03:22speachymight be a display resolution thing
12:03:31speachyrocker's only 160x128 IIRC.
12:03:59speachyit's there on the eros..
12:04:04_bilgus__and oscope segfaults
12:04:22speachyit's definitley being built on the rocker btw, I have it in my working tree
12:04:36_bilgus__oh I should pply 2811 and see if it fixes it
12:04:48_bilgus__its there I just can't exit it
12:05:03_bilgus__like the button isn't mapped
12:05:27speachyit's a PLA target
12:05:40_bilgus__could be a yield issue too
12:05:49_bilgus__I'll check it out tonight
12:05:50speachyno, I'm ble to quit fine on the H2
12:06:23_bilgus__i'll try a dev version from a few days ago
12:06:40speachytry vol up
12:07:14speachywtf fire uses PLA_CANCEL but not PLA_EXIT
12:07:48 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
12:07:53_bilgus__ah so map issue
12:08:03speachymore like the plugin is stupid. :D
12:08:15_bilgus__there are lots of little things like that through the plugins
12:08:41_bilgus__part of the reason I want to make it more dynamic everyone could share
12:09:12_bilgus__that and its like the most requested thing changing keymaps..
12:09:23fs-bluebot_Build Server message: New build round started. Revision 2cf75bf, 293 builds, 9 clients.
12:10:31speachyso far my alsa rejiggering is holding up, yay.
12:11:13_bilgus__so that kind of tickles me a bit that oscope crashes on scroll when I was doing the patch it just kept crashing no matter what I did
12:11:32_bilgus__that was like a 2 day adventure
12:12:20 Join johnb7 [0] (
12:12:37_bilgus__not that knowing that woulkd have helped me then..
12:22:40fs-bluebot_Build Server message: Build round completed after 796 seconds.
12:22:43fs-bluebot_Build Server message: Revision 2cf75bf result: All green
12:24:02 Quit pamaury (Ping timeout: 265 seconds)
12:42:35***Saving seen data "./dancer.seen"
12:45:29_bilgus__last thought before I go I think I'd like to start making some simple-ish tests as lua scripts to test the underlying target like printf formatting for example :P
12:46:26_bilgus__I already have the capability to read and write memory addresses from lua its locked down ATM but can be expanded to probe any accessible address
12:48:56_bilgus__its how I get around having to pull the entirety of rockbox into the lua interpreter, tables of interface info generated at BUILD time
12:50:13 Join SammysHP_ [0] (
12:50:28 Join Tsesarevich_ [0] (Tsesarevic@fluxbuntu/founder/joejaxx)
12:52:58speachyok, the alsa driver's init code has been reworked again, and it now has recording support, in theory.
12:53:02 Quit johnb7 (Ping timeout: 265 seconds)
12:56:02 Join heredoc [0] (heredoc@2a01:7e01::f03c:91ff:fec1:de1d)
12:57:33 Quit kadoban (*.net *.split)
12:57:33 Quit edhelas (*.net *.split)
12:57:33 Quit ender| (*.net *.split)
12:57:33 Quit Stanley00 (*.net *.split)
12:57:33 Quit Tsesarevich (*.net *.split)
12:57:33 Quit heredoc_ (*.net *.split)
12:57:33 Quit SammysHP (*.net *.split)
12:57:34 Quit koniu (*.net *.split)
12:57:45 Nick Tsesarevich_ is now known as Tsesarevich (Tsesarevic@fluxbuntu/founder/joejaxx)
13:03:02 Join MrZeus_ [0] (~MrZeus@
13:05:24 Join ender| [0] (~ender1@2a01:260:4094:1:6045:6fff:fedd:cbf3)
13:05:33 Quit fs-bluebot_ (Read error: Connection reset by peer)
13:05:33 Quit bluebrother (Read error: Connection reset by peer)
13:05:58 Join fs-bluebot [0] (
13:06:03 Join bluebrother [0] (~dom@rockbox/developer/bluebrother)
13:07:57 Join kadoban [0] (kadobanmat@gateway/shell/
13:08:44 Quit Rower (Ping timeout: 260 seconds)
13:15:17 Quit vmx (Quit: Leaving)
13:15:26 Join lebellium [0] (
13:24:33 Join edhelas [0] (
13:31:53speachysripped out the non-async mode due to the tick-based mode being completely irrecovably broken
13:35:39 Join koniu [0] (~koniu@gateway/tor-sasl/koniu)
13:36:23edhelasthe GIT repository is quite slow to answer, it's normal ?
13:55:29edhelasspeachy this fixes the issue for me :)
14:13:35 Join pamaury [0] (~pamaury@rockbox/developer/pamaury)
14:42:39***Saving seen data "./dancer.seen"
14:48:19ArsenArsenI should mirror it
15:11:20 Join johnb7 [0] (
15:15:02 Join fs-bluebot_ [0] (
15:15:07 Quit bluebrother (Disconnected by services)
15:15:12 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother)
15:16:30 Quit fs-bluebot (Ping timeout: 258 seconds)
15:20:33 Quit johnb7 (Ping timeout: 260 seconds)
16:03:09 Join johnb7 [0] (
16:05:32 Quit pamaury (Ping timeout: 256 seconds)
16:12:28 Quit johnb7 (Ping timeout: 260 seconds)
16:25:05 Quit SammysHP_ (Quit: *wuff*)
16:26:43 Join SammysHP [0] (
16:28:19 Join johnb7 [0] (
16:37:34 Quit lebellium (Read error: Connection reset by peer)
16:37:55 Join lebellium [0] (
16:38:30 Quit johnb7 (Ping timeout: 272 seconds)
16:41:44speachyokay, I think the audio garbage on the hosted targets is actually some sort of core bug
16:41:51speachy(on track skip)
16:41:59 Join kugel_ [0] (~kugel@rockbox/developer/kugel)
16:42:08speachyedhelas: I'll have a look at it later tonight or this weekend
16:42:43***Saving seen data "./dancer.seen"
16:44:12 Join pookie [0] (
16:45:41speachy_bilgus__: I'm able to recreate that oddidty on the X3 nearly at will now. skip to a new track, display updates, but nothing seems to happen until another key is pressed. any key.
16:46:03speachy(I mean, no audio playback starts)
16:47:32speachyI wonder if it's an interrupt delivery thing.
16:48:57speachyand that audio garbage thing sounds like it's basically due to the pcm playback buffer not getting cleared/filled properly before it's being handed over.
16:50:04 Quit Acou_Bass (*.net *.split)
16:50:04 Quit _3dsv (*.net *.split)
16:50:04 Quit ps-auxw (*.net *.split)
16:50:04 Quit rogeliodh (*.net *.split)
16:50:04 Quit beencubed (*.net *.split)
16:50:04 Quit kugel (*.net *.split)
16:50:04 Quit mixfix41 (*.net *.split)
16:50:04 Quit Slasherii (*.net *.split)
16:50:04 Quit galaxy_knuckles (*.net *.split)
16:50:04 Quit olspookishmagus (*.net *.split)
16:50:10 Join Acou_Bass [0] (
16:50:10 Join _3dsv [0] (
16:50:10 Join ps-auxw [0] (
16:50:10 Join rogeliodh [0] (
16:50:10 Join beencubed [0] (~beencubed@
16:50:10 Join mixfix41 [0] (~popebook2@unaffiliated/mixfix41)
16:50:10 Join galaxy_knuckles [0] (~gknux@unaffiliated/galaxy-knuckles/x-1756549)
16:56:52 Join Slasherii [0] (
17:50:14fs-bluebot_Build Server message: New build round started. Revision 46e357f, 293 builds, 9 clients.
17:51:29lebelliumspeachy: g#2892 is more or less the same as g#634, isn't it?
17:51:33fs-bluebot_Gerrit review #2892 at : samsungyp: Enable recording feature. No idea if it works. :D by Solomon Peachy
17:51:33fs-bluebot_Gerrit review #634 at : Samsung YP-R0: record FM radio by Lorenzo Miori
17:51:42lebelliumI talked to Lorenzo tonight
17:51:53speachyno, it's a rewrite of 634 plus a lot more
17:52:01lebelliumhe told me
17:52:03lebellium"yeah, my work on R0 was a brief attempt to mock around with recording but I see we are limited to 8khz or 22khz (don't even remember right now) -> quality sucks -> not worth the time investment to close the feature"
17:52:36speachyor rather, 2891 was the rewrite, and 2892 just enables recording on the R0/R1.
17:55:11lebelliumyou mean g#2888?
17:55:13fs-bluebot_Gerrit review #2888 at : ALSA: Further rework: by Solomon Peachy
17:55:22speachyyeah, that. :D
17:56:18speachyI marked 633 as abandoned (as it's completely obsoleted by 2888) but 634 may be worth incorporating.
17:57:05speachyif nothing else, 2892 will be the only user of the pcm recording code, so we can at least know if something causes it to stop compiling.
17:58:12speachylebellium: since you have a YP-R0, if you'd care to try out the build that's going to spit out in a few and tell me if audio playback still works..
17:58:42lebelliumshouldn't we test that before commiting a patch? :D
17:58:46speachyit's definitely improved on the hiby-based targets
17:59:37lebelliumI don't pretend being able to tell if it sounds better or not but at least I can tell if playback still works indeed
17:59:49speachythat's all I can ask
18:01:20lebelliumregarding recording, without proper keymaps I assume I won't be able to test
18:01:20speachyslowly undoing more layered hacks, basically
18:01:34speachyI'd be surprised if recording worked, honestly
18:03:04fs-bluebot_Build Server message: Build round completed after 770 seconds.
18:03:08fs-bluebot_Build Server message: Revision 46e357f result: All green
18:03:09fs-bluebot_Build Server message: New build round started. Revision a8aa840, 293 builds, 8 clients.
18:16:35 Join S|h|a|w|n [0] (~shawn156@unaffiliated/shawn156)
18:17:23fs-bluebot_Build Server message: Build round completed after 854 seconds.
18:17:24fs-bluebot_Build Server message: Revision a8aa840 result: All green
18:27:12lebelliumspeachy: playback still working on YP-R0
18:29:28lebelliumstarting FM recording: crash
18:30:50lebelliumin the recording settings I see only "44.1kHz" frequency while lorenzo meant in the patch that only 8 and 16kHz are supported
18:30:59lebelliumthis could explain the crash
18:33:04lebelliumthere is no microphone so I'm not sure what the main "recording" menu is supposed to do.
18:33:24lebelliumDoes "#define HAVE_RECORDING" automatically add both voice recording and FM recording ?
18:34:25lebelliumor maybe line in. But there is no line in either
18:42:46***Saving seen data "./dancer.seen"
18:48:02 Quit S|h|a|w|n (Read error: Connection reset by peer)
18:50:07 Join S|h|a|w|n [0] (~shawn156@unaffiliated/shawn156)
19:06:27 Quit lebellium (Quit: Leaving)
19:10:35speachywell, it's clearly something that needs further work.
19:11:14speachythere are REC_CAPS that let one select the source, but obviously the code has to be there on the target-specific code to do the actual switching
19:14:50 Join bluebrother [0] (~dom@rockbox/developer/bluebrother)
19:15:05 Join fs-bluebot [0] (
19:17:24 Quit fs-bluebot_ (Ping timeout: 260 seconds)
19:18:02 Quit bluebrother^ (Ping timeout: 256 seconds)
19:23:40 Join cockroach [0] (~blattodea@pdpc/supporter/active/cockroach)
19:31:06_bilgus__well the sansa clip+ bootloader works but only displays the first letter of each word lol
19:31:26speachylovely, commit 2e708c48c5 is what's leading to that hang. (where I pusuedo-dynamically adjust the mixbuf size based on teh active samplerate)
19:43:26 Quit cockroach (Ping timeout: 272 seconds)
19:47:17_bilgus__speachy can you fill me in on the issue at hand here? was it the one you posited might be the button code?
19:48:22speachyit's not the button code, but something wonky in the mixer. one of the callbacks is failing and explcitly telling the DMA to stop without any sort of real error recovery
19:57:02_bilgus__Clip+ ok so at least its not my printf code failing its the putsxofy function
19:58:53_bilgus__hmm it doesn't appear that the rb logo displays unless the device actually boots I should remove the logo from the boot loader
20:01:17_bilgus__meh save that for next time
20:16:25 Quit MrZeus_ (Ping timeout: 264 seconds)
20:19:08 Join cockroach [0] (~blattodea@pdpc/supporter/active/cockroach)
20:35:38 Join massiveH [0] (
20:39:54_bilgus__ok bootloader is good
20:40:46fs-bluebotBuild Server message: New build round started. Revision d78a376, 293 builds, 9 clients.
20:42:50***Saving seen data "./dancer.seen"
20:54:58fs-bluebotBuild Server message: Build round completed after 853 seconds.
20:55:00fs-bluebotBuild Server message: Revision d78a376 result: All green
20:58:44_bilgus__I think maybe a vector based graphic might work better for our logo
21:19:14_bilgus__the thought just occurred to me for the framebuffer and viewports: I store elems with the intention of using the calculated FB address % elems but I disabled that since I figured it was clipped by LCD_W/H
21:20:21_bilgus__It will protect the buffer along with an ABS fn so that gets rid of all those ifs
21:20:50_bilgus__then clipping can be a pointer to a default vp xy wh clip function or NULL and only one check gets made
21:35:02 Quit massiveH (Read error: Connection reset by peer)
21:36:53_bilgus__and shot down already all those plugins could wreak havoc on core if I do that
21:37:01 Join massiveH [0] (
21:57:42speachyGAH! found it.
21:59:35speachy g#2983
21:59:52speachyor rather, g#2893
21:59:53fs-bluebotGerrit review #2893 at : pcm_mixer: Fix an idle frame calculation bug introduced in 2e708c48c5 by Solomon Peachy
22:00:50fs-bluebotBuild Server message: New build round started. Revision ec2a34b, 293 builds, 9 clients.
22:01:07speachythis is one of those bugs that make me wonder how things actually mostly worked
22:03:00speachy_bilgus__: heh, I kinda wish you'd updated the commit message for your bootloader hacking to mention that you did indeed confirm it worked.
22:04:09 Quit cockroach (Quit: leaving)
22:12:14_bilgus__for the record?
22:14:27fs-bluebotBuild Server message: Build round completed after 816 seconds.
22:14:29fs-bluebotBuild Server message: Revision ec2a34b result: All green
22:22:08_bilgus__speachy that bug is subtle AF too
22:22:40_bilgus__its why people over paren.
22:26:48speachyyeah. Blame it on a brain fart thinking it was equivalent.
22:28:18speachyedhelas: I'm not able to recreate any failure with the gcc patch that's currently committed; indeed, using the changed one you put in gerrit actually results in patch having to offset things.
22:30:58speachy_bilgus__: the reason hitting a key worked to un-stick things is because I had keyclicks on.
22:32:02_bilgus__thats one of those the car works right when i'm barefoot bugs
22:40:08_bilgus__just realized the samsung y targets have a scrolling line to 'test scrolling'?
22:40:52_bilgus__I think disabling the thread won't hurt anyone it will just not scroll so should be removed from them
22:42:53***Saving seen data "./dancer.seen"
22:45:20speachyand if you have more infinite free time, I tore up the pcm-alsa driver more, should have much-reduced intra-track clicking now.
22:45:52speachyI had to move the auto-mute point that the rocker uses, but that might not even be necessary any more.
22:52:29speachythis mute bug might have actually been the underling cause of the pcm-alsa track skip artifact, but the rework needed doing regardless.
22:52:54speachys/mute/idle frame/
22:57:35_bilgus__TBH I didn't really notice it but the hang one I did
22:57:53 Quit prof_wolfff (Ping timeout: 260 seconds)
23:13:28 Join Huntereb [0] (~Huntereb@
23:43:28 Join massive_H [0] (
23:43:55 Quit TheSeven (Disconnected by services)
23:44:05 Join [7] [0] (~quassel@rockbox/developer/TheSeven)
23:46:38 Quit massiveH (Ping timeout: 272 seconds)
23:47:06 Quit Oksana (Ping timeout: 258 seconds)

Previous day | Next day