--- Log for 23.05.118 Server: hitchcock.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 15 days and 8 hours ago 00.08.33 # saratoga theres the beginning of this conversation: https://www.rockbox.org/irc/log-20171111#06:55:03 00.11.48 # Bilgus: is there a patch somewhere with all of this? 00.12.32 # I thought there was but I'm not finding it 00.13.03 # i have no idea what i'm looking at for that unicode change 00.15.15 # i was going to ifdef out the priority threads on AMS just to get it to at least build, but that actually isn't enough 00.16.10 # There must be some newer commit because it was like bytes over on the clip+ 00.16.32 # literally a handfull of bytes 00.17.47 Quit amayer (Quit: Leaving) 00.30.27 # its gained 2kb since last november 00.37.52 # Version: 8157871M-180522 00.37.52 # mkamsboot Version ee2eb13M-171106 00.37.53 # [INFO] Original firmware MD5 checksum match 00.37.53 DBUG Enqueued KICK Bilgus 00.37.53 # [INFO] Model: Sansa Clip+ v1 - Firmware version: 01.02.16 00.37.53 # [INFO] Original firmware size: 134008 bytes 00.37.53 *** Alert Mode level 1 00.37.53 # [INFO] Packed OF size: 86447 bytes 00.37.55 # [INFO] Bootloader size: 65712 bytes 00.37.59 # [INFO] Packed bootloader size: 45238 bytes 00.38.01 # [INFO] Total size of new image: 132549 bytes 00.38.31 # here is what I had the last time I compiled the bootloader let me pull whats creent and see what has changed 00.38.38 # *current 00.41.21 # Bilgus: not sure i understand the map files, but there is a lot added in january 00.41.52 # this is all new: https://pastebin.com/fen9t3uJ 00.46.50 # any idea why the bootloader suddenly gained a lot of stuff related to _divdi3? 00.47.54 *** Alert Mode OFF 00.48.22 Quit ender` (Quit: 99% of lawyers give the rest a bad name.) 00.55.14 # saratoga Ok first, make clean then ../tools/configure --thumb 62 b make then make ams that brings it down to 400 bytes over 00.56.31 # could be random, but bissect says this is the offending commit: https://git.rockbox.org/?p=rockbox.git;a=commit;h=01c6dcf 00.56.37 # my guess is that it has something to do with vuprintf We were using a slimmed down version in the bootloader 00.57.07 # I guess that kinda comfirms it 00.57.37 # I know jhmikes had flags that pulled out un-needed functionality I wonder if that bypassed it 00.58.22 # but that commit was reverted 00.58.26 # so i'm a little confused 01.00.37 # http://gerrit.rockbox.org/r/#/c/1679/8/firmware/common/vuprintf.c 01.00.44 # yeah, so that commit increased the bootloader size, but reverting it did not decrease it 01.01.38 Quit krabador (Remote host closed the connection) 01.01.48 # I bet a conditional flag will fix it for now and we can let __builtin figure out what he broke 01.02.04 # <__builtin> damn, what'd I break? 01.02.33 # wait it wasn't fully reverted? 01.02.35 # <__builtin> I did revert that patch 01.02.57 # https://git.rockbox.org/?p=rockbox.git;a=blobdiff;f=firmware/common/vuprintf.c;h=e233022bc3edc899dc40286d58fade0fff86ccad;hp=c32b690cf824a8731569e08d8195add4a7d21175;hb=HEAD;hpb=5c9688961ef9166cec5225db50d5f73691d8292d 01.03.02 # that define changed 01.05.51 # yep change it to #ifndef BOOTLOADER 01.06.07 # and it knocks off 2k 01.06.28 # <__builtin> I evidently changed that in the Duke3D commit 01.06.39 # so yeah JhMikes Added conditional flags but the rest of that commit turned them all on 01.07.06 # In the bootloader we need %s and maybe %d IIRC 01.07.39 # still fails, but by less than 400 bytes 01.08.04 # and since that patch We spoke about earlier saratoga only freed 9bytes I bet its been superseded 01.08.23 # saratoga Ok first, make clean then ../tools/configure --thumb 62 b make then make ams that brings it down to 400 bytes over 01.08.36 # that will bring it under 01.08.48 # but let me investigate for a bit 01.10.14 # Build Server message: 3New build round started. Revision 0b2f518, 273 builds, 11 clients. 01.10.45 # can we just disable the priority thread thing on AMS? 01.16.23 # I swear mike already did 01.16.37 # no its still enabled 01.18.37 # CP_STATIC_ALLOC should knock off the rest but I have to look for the flag 01.23.35 # you want to commit that? 01.24.53 # Fixing vuprintf and knocking out the scroll worker code frees up plenty 01.24.59 # g#1724 01.25.01 # 3Gerrit review #1724 at http://gerrit.rockbox.org/r/1724 : 3Remove lcd_scroll_worker from bootloader except remote displays and charcell by William Wilgus 01.25.06 *** Saving seen data "./dancer.seen" 01.25.16 # push it? 01.25.49 # looks pretty safe 01.26.10 # Its been tested but not across the whole codebase 01.26.31 # Build Server message: 3Build round completed after 977 seconds. 01.26.32 # Build Server message: 3Revision 0b2f518 result: 5 errors 0 warnings 01.26.48 Join MrZeus_ [0] (~MrZeus@2a02:c7f:7066:fb00:e069:75b3:e3be:190) 01.27.46 # i don't see any errors in the build table 01.28.13 # are there any bootloaders that need scrolling text? 01.28.45 # to be readable? 01.28.49 # Charcell bootloaders were the only ones I saw 01.29.03 Join exec_ [0] (185d7e20@gateway/web/freenode/ip.24.93.126.32) 01.29.12 Quit ZincAlloy (Quit: Leaving.) 01.29.31 # the zip is one of the narrower devices, and while the text does clip off the edge, the bootloader doesn't scroll anyway 01.29.59 # i think you can commit it, should be obvious if something breaks 01.30.20 # I don't have the permissions 01.31.08 # you don't? 01.32.22 # Nope I never bothered asking either lol 01.33.20 Quit cc___ (Ping timeout: 260 seconds) 01.33.31 # i'll see about changing that 01.36.31 # i'll see about committing that patch 01.37.47 # I'd ask JhMikes about CP_STATIC_ALLOC as well I know theres a flag that enables it but I'd have to go through the logs to find it 01.38.13 # i always forget with git, i can just cherry pick and then push to origin right? 01.38.40 # Build Server message: 3New build round started. Revision 0999a22, 273 builds, 11 clients. 01.38.47 # yeah thats right 01.40.59 # fits by 60 bytes now 01.41.21 # i bet at least something fails to patch still though 01.45.07 Quit exec_ (Quit: Page closed) 01.45.59 # well If you do --thumb it frees a bit more 01.46.40 Join Strife89 [0] (~quassel@adsl-98-80-193-80.mcn.bellsouth.net) 01.46.44 # My rework of the codepages frees another 80bytes and it has no side effects its just organized better in ram 01.47.48 # g#1731 01.47.51 # 3Gerrit review #1731 at http://gerrit.rockbox.org/r/1731 : 3Optimize is_diacritic by William Wilgus 01.50.05 Quit Strife1989 (Ping timeout: 252 seconds) 02.19.32 Quit mmint (Ping timeout: 260 seconds) 02.26.50 Quit MrZeus_ (Ping timeout: 245 seconds) 02.32.59 # <__builtin> is anyone thinking about doing another release some time soon? 03.05.15 Quit Strife89 (Ping timeout: 252 seconds) 03.05.17 Join Strife1989 [0] (~quassel@adsl-98-80-193-80.mcn.bellsouth.net) 03.25.09 *** Saving seen data "./dancer.seen" 04.33.51 # So is the build system stuck then? 04.52.34 Join ttim__ [0] (~not@p4FDF6291.dip0.t-ipconnect.de) 04.56.21 Quit ttim_ (Ping timeout: 260 seconds) 05.07.36 Quit quaz0r (Quit: reboot) 05.25.10 *** Saving seen data "./dancer.seen" 05.35.05 Join quaz0r [0] (~quaz@c-24-18-93-195.hsd1.wa.comcast.net) 05.37.42 Join mmint [0] (~mmint@unaffiliated/mmint) 06.06.17 Join this_is_a_nick [0] (~amofiuhr_@ip217-132-50-179.ct.co.cr) 06.06.29 Quit TheSeven (Ping timeout: 245 seconds) 06.16.45 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 07.16.32 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:90df:46e1:5531:d2d4) 07.21.13 Quit ZincAlloy (Client Quit) 07.25.11 *** Saving seen data "./dancer.seen" 07.36.51 Quit dys (Ping timeout: 245 seconds) 08.06.51 Join ernestask [0] (~ernestask@78-56-62-157.static.zebra.lt) 08.14.33 Join deevious [0] (~Thunderbi@193.226.142.214) 08.19.48 Join ender` [0] (krneki@foo.eternallybored.org) 09.24.04 Join petur [0] (~petur@91.183.48.77) 09.24.04 Quit petur (Changing host) 09.24.04 Join petur [0] (~petur@rockbox/developer/petur) 09.25.13 *** Saving seen data "./dancer.seen" 10.07.24 # I don't know what the exact state of the build system is, but I noticed that one of my clients (which does Android) wasn't running, and when I started it it got some jobs 10.12.55 # Build Server message: 3Build round completed after 30854 seconds. 10.12.57 # Build Server message: 3Revision 0999a22 result: 125 errors 36 warnings 10.19.16 Join LinusN [0] (~linus@giant.haxx.se) 10.42.04 Quit this_is_a_nick (Remote host closed the connection) 10.48.34 Quit Acou_Bass (Ping timeout: 245 seconds) 10.59.33 Join this_is_a_nick [0] (~amofiuhr_@ip104-237-64-186.ct.co.cr) 11.25.16 *** Saving seen data "./dancer.seen" 11.36.38 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.41.54 Join Acou_Bass [0] (~Acou_Bass@host-89-241-254-192.as13285.net) 12.18.38 Join asymsucon [0] (5b5ab5db@gateway/web/freenode/ip.91.90.181.219) 12.19.10 # Hi, is there a fix for fading display on Clip Zip? 12.22.36 Quit TorC (Ping timeout: 265 seconds) 12.42.25 Join TorC [0] (~Tor@fsf/member/TorC) 12.56.35 Quit deevious (Quit: deevious) 12.56.54 Join deevious [0] (~Thunderbi@193.226.142.214) 12.59.30 # asymsucon: I didn't know this was a thing 13.00.09 # pamaury http://forums.sandisk.com/t5/Sansa-Clip-Sansa-Clip/Screen-is-extremely-dim-basically-black/td-p/225802 13.00.45 # It happens intermittently, I can´t get a good photo of it 13.00.46 # looks like a hardware problem 13.01.33 # Though it doesn´t seem like cold joint because it´s not affected by manipulation 13.03.50 # Original FW somehow always restore the backlight when loading 13.08.31 # you mean that it only happens in Rockbox? 13.09.52 # So far I haven´t seen it outside RB, but as I said, it´s intermittent, so it might be just subjective conclusion 13.10.44 # Since I increased the brightness, the issue has yet to appear 13.25.19 *** Saving seen data "./dancer.seen" 13.27.51 Join massiveH [0] (~massiveH@ool-18e4e27c.dyn.optonline.net) 14.16.31 # asymsucon it is most likely still an issue with the hardware you just happen to be pushing the oled with enough current that it is working ok for now but the minimum amount that will work will probably increase over time 14.17.14 # Bilgus any way to prevent this, or slow down the progress? 14.17.26 # I guess all OLED screens are limited in lifespan 14.17.48 Join amayer [0] (~amayer@107-1-97-172-ip-static.hfc.comcastbusiness.net) 14.18.15 # the brighter it is the worse the lifetime 14.25.56 # Technically, the screen is using PWM dimming so it´s always reaching 100% within its duty cycle 14.26.34 # so as the screen ages, more duty cycle is needed? 14.33.45 # IIRC those displays use a current driver that is controlled by a pwm signal and the actual display is complicated there is a pre-charge current that gets them primed/biased then they get a little extra kick that pushes them over the threshold so its more like that threshold is a little higher now 14.34.55 # yep, that´d explain the behaviour I was experiencing 14.54.56 Quit asymsucon (Quit: Page closed) 14.57.11 Quit massiveH (Quit: Leaving) 15.25.23 *** Saving seen data "./dancer.seen" 15.35.27 Quit prof_wolfff (Ping timeout: 252 seconds) 15.43.32 Join ttim_ [0] (~not@p4FDF6291.dip0.t-ipconnect.de) 15.46.32 Quit ttim__ (Ping timeout: 264 seconds) 15.51.31 Join prof_wolfff [0] (~castor@95.211.203.179) 16.24.21 Quit this_is_a_nick (Read error: Connection reset by peer) 16.24.24 Join amofiuhr_ [0] (~amofiuhr_@ip104-237-64-186.ct.co.cr) 16.28.28 Quit duo8 (Ping timeout: 260 seconds) 16.30.09 Join duo8 [0] (~ZNC-SRV-H@27.79.243.71) 16.45.29 Join krabador [0] (~krabador@unaffiliated/krabador) 17.07.43 Quit TheSeven (Ping timeout: 245 seconds) 17.08.00 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 17.25.24 *** Saving seen data "./dancer.seen" 17.27.31 Quit petur (Quit: Connection reset by beer) 18.06.54 Quit krabador (Remote host closed the connection) 18.07.14 Join krabador [0] (~krabador@unaffiliated/krabador) 18.16.54 Join krabador_ [0] (~krabador@unaffiliated/krabador) 18.17.30 Quit krabador (Read error: Connection reset by peer) 18.24.16 Join ZincAlloy [0] (~Adium@ip1f12fcfd.dynamic.kabel-deutschland.de) 18.40.03 Quit krabador_ (Remote host closed the connection) 19.01.09 Quit pamaury (Ping timeout: 252 seconds) 19.03.34 Join lebellium [0] (~hexchat@89-93-177-206.hfc.dyn.abo.bbox.fr) 19.14.55 Join cc___ [0] (~ac@2001:910:1033:1:6a05:caff:fe1c:1627) 19.19.20 Join petur [0] (~petur@rockbox/developer/petur) 19.25.28 *** Saving seen data "./dancer.seen" 19.40.42 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 19.46.32 Quit ZincAlloy (Ping timeout: 264 seconds) 19.55.05 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:5cae:7b33:5b21:fc1e) 20.03.57 Join MrZeus_ [0] (~MrZeus@2a02:c7f:7066:fb00:9dbe:e012:865c:265) 20.13.24 Quit amofiuhr_ (Remote host closed the connection) 20.33.30 Quit Galois (Remote host closed the connection) 20.34.16 Join Galois [0] (djao@efnet-math.org) 20.51.46 Join noobineer [0] (~noobineer@c-68-55-184-193.hsd1.mi.comcast.net) 21.00.56 Quit michaelni (Quit: Leaving) 21.02.03 Quit prof_wolfff (Ping timeout: 240 seconds) 21.03.58 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 21.11.33 Join ttim__ [0] (~not@p4FDF6291.dip0.t-ipconnect.de) 21.11.49 Join krabador [0] (~krabador@unaffiliated/krabador) 21.14.28 Quit ttim_ (Ping timeout: 260 seconds) 21.16.50 Quit MrZeus_ (Ping timeout: 245 seconds) 21.17.04 Join prof_wolfff [0] (~castor@82.102.26.212) 21.25.30 *** Saving seen data "./dancer.seen" 21.30.25 Join this_is_a_nick [0] (~amofiuhr_@201.199.104.92) 21.44.15 Quit ernestask (Quit: ernestask) 21.54.50 Join paulk-gagarine-s [0] (~paulk-gag@220.107.128.77.rev.sfr.net) 21.56.47 Quit paulk-gagarine (Ping timeout: 248 seconds) 22.05.44 Quit noobineer (Ping timeout: 264 seconds) 22.20.43 Join dys [0] (~dys@tmo-113-74.customers.d1-online.com) 22.37.24 Quit amayer (Quit: Leaving) 22.46.14 Join CrashBash-Kun [0] (~CrashBash@unaffiliated/crashbash-kun) 22.51.31 Quit petur (Remote host closed the connection) 23.02.43 Quit ZincAlloy (Ping timeout: 245 seconds) 23.10.30 Quit WakiMiko (Ping timeout: 256 seconds) 23.10.32 Join noobineer [0] (~noobineer@c-68-55-184-193.hsd1.mi.comcast.net) 23.11.09 Join WakiMiko [0] (~WakiMiko@unaffiliated/wakimiko) 23.25.31 *** Saving seen data "./dancer.seen" 23.26.39 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:5cae:7b33:5b21:fc1e) 23.40.20 Join Strife89 [0] (~quassel@adsl-98-80-187-28.mcn.bellsouth.net) 23.40.32 Quit Strife1989 (Ping timeout: 252 seconds) 23.43.56 Quit CrashBash-Kun (Ping timeout: 256 seconds) 23.47.54 Quit pamaury (Ping timeout: 256 seconds) 23.54.31 Join JanC_ [0] (~janc@lugwv/member/JanC) 23.56.07 Quit JanC (Killed (niven.freenode.net (Nickname regained by services))) 23.56.07 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC)