--- Log for 08.07.121 Server: tantalum.libera.chat Channel: #rockbox --- Nick: rb-logbot_ Version: Dancer V4.16 Started: 10 days and 19 hours ago 00.02.53 Quit sadjhflj333 (Ping timeout: 265 seconds) 00.27.01 # <_bilgus> braewoods, why the addition of the utimebuf struct? 00.27.13 # _bilgus: see man utime 00.27.28 # https://man7.org/linux/man-pages/man2/utime.2.html 00.28.20 # _bilgus: i would review the previous request first since the utime one depends on it 00.29.31 # <_bilgus> ick 00.31.01 # i was just trying to follow a standard approach for it for maximum compatibility 00.32.23 # <_bilgus> aren't we targeting posix though thus far? 00.32.37 # yes. utime used to be in posix but was dropped in 2008. 00.32.41 # even so it tends to stick around. 00.33.07 # <_bilgus> posix will want a fd and a time struct as well 00.33.22 # but it uses filenames 00.33.36 # only the newer ones can use FDs 00.34.17 # <_bilgus> eh you clearly are more aware of it than I 00.34.41 # well we can make our own but they're not much mroe useful than utime 00.34.50 # we don't support sub-second stuff really 00.35.13 # _bilgus: i'll look into it more, just look at my time oncversion 00.36.38 # but i can change it to allow different dirent stuff to be modded 00.36.48 # would be more flexible 00.36.58 # but i can't see anything else worth modding in metadata 00.37.28 # _bilgus: yea it's weird. readlink doesn't work with FDs. 00.38.30 # Build Server message: 3New build round started. Revision 49ca4b3e5e, 297 builds, 8 clients. 00.47.48 # <_bilgus> what about making it take two time struct pointers 00.48.11 # <_bilgus> atm its gonna be a pain to get into a plugin 00.49.01 # _bilgus: why? structs aren't part of the ABI per say. they can just include the header or so. 00.49.54 # i mean if it bugs ya we can just write our own version 00.50.35 # <_bilgus> idk I'll have speachy look at it its surely more his forte 00.51.05 # but afaik all the standard time modifying APIs use structs 00.51.22 # or an array of structs 00.51.38 # <_bilgus> it should match to the native stuff 00.51.47 # <_bilgus> thats most important 00.52.02 # we can do that at the FAT layer but use something else for the generic api 00.52.09 # <_bilgus> and being they are usually linux 00.52.43 # <_bilgus> yeah another translation layer 00.52.52 # <_bilgus> and two more in lua 00.52.55 # <_bilgus> lol 00.53.19 # i just wanted this so my ZIP files can update timestamps after finishing their extraction 00.53.35 # we could make an extension API that just wraps utime or so on real targets 00.53.45 # access time is pretty irrelevant to us as it is 00.53.52 # modtime is the only one we really care about 00.57.16 # Build Server message: 3Build round completed after 1125 seconds. 00.57.18 # Build Server message: 3Revision 49ca4b3e5e result: All green 01.04.26 # the other variants of utime... 01.04.40 # use struct timeval or struct timespec 01.05.29 # so afaik we would need a custom version if we wanted to use a simpler API or so. 01.05.57 # there's so many damn functions for changing these it's not even funny 01.06.09 # utime, utimes 01.06.18 # futimesat 01.06.26 # utimensat 01.06.31 # futimes 01.06.45 # futimens 01.07.32 *** Saving seen data "./dancer.seen" 01.16.08 # <_bilgus> yeah I saw them all 02.20.24 # btw. https://www.rockbox.org/wiki/CreativeZENXFi has the same WiFI chip as sansa connect 03.07.36 *** No seen item changed, no save performed. 05.07.37 *** No seen item changed, no save performed. 05.36.26 Join ufdm_ [0] (~ufdm@c-73-164-63-214.hsd1.mn.comcast.net) 05.37.25 Quit ufdm (Ping timeout: 246 seconds) 05.38.30 Quit ufdm_ (Client Quit) 05.40.44 Quit spork (Ping timeout: 265 seconds) 05.45.54 Join spork [0] (topic@31-151-2-135.dynamic.upc.nl) 06.30.13 Join cockroach [0] (~blattodea@user/cockroach) 06.53.47 Quit cockroach (Quit: leaving) 07.07.41 *** Saving seen data "./dancer.seen" 07.34.49 Join ufdm [0] (~ufdm@c-73-164-63-214.hsd1.mn.comcast.net) 07.36.19 Join MarcAndersen [0] (~no_znepna@193.169.154.231) 07.37.25 # Hi. I now have a physical sansa connect in front of me, and a compiled bootloader and zsitool. Could someone please guide me through installing it so I don't brick it like my c200? 08.01.06 # I am now compiling rockbox itself 08.07.48 # Sansa Connect can pretty much always be recovered as the OF bootloader is hardware write-protected 08.09.06 # to start, enter recovery mode by completely powering down the device (press power button for 10 seconds) 08.09.26 # And where was the power button, sorry. 08.09.42 # at the top, left to the hold switch 08.10.19 # it is round button 08.10.22 # should hold be closest to the edge or to the power button? 08.10.46 # hold is closest to the edge, power button is in the middle 08.11.15 # yes, but shoudl the switch be closest to the edge to make it unlocked? 08.11.33 # closest to the edge unlocks 08.13.21 # to enter recovery mode, press and hold right button (above the wheel) together with volume up button (on the left side) 08.13.40 # while holding the buttons, connect the device to USB 08.13.44 # I try, but don't get any usb devices, maybe it's battery is dead? 08.14.21 # that's possible, if the battery is low it will shut down 08.14.50 # if MTP does not come up, then it's probably charging 08.15.11 # if MTP comes up, then it booted OF (and not recovery mode) 08.15.32 # nothing yet 08.16.01 # when in recovery mode, lsusb should list 0781:7481 SanDisk Corp. Sansa Connect (in recovery mode) 08.16.19 # battery can take like 30 minutes to get the initial charge 08.17.02 # I will give it some time then. It was a new one from ebay, he might have had it lie around for years. It is new though. 08.17.05 # when the firmware (OF or Rockbox) is not running the charging is really slow 08.18.04 # But when I get it into recovery, which of all these files do I need to send to zsitool? 08.18.18 # bootloader.bin 08.18.36 # so ./zsitool -e bootloader.bin? 08.18.42 # yes 08.19.11 # I'll report back when I get that far... Thanks. It's always fun to test new ports. 08.19.14 # it takes a minute or two after zsitool says done for flashing to finish 08.19.38 # then you should see mass storage device with access to ext2 filesystem 08.19.58 # ok. what to put there? 08.20.02 # to run rockbox you can either use microsd card or format the partition to fat 08.20.15 # unzip rockbox-full.zip 08.20.44 # So I format ext2 as fat and copy rockbox to that. That sounds easy. 08.22.06 # In an hour or so I will get someone who can see in here if it goes wrong. 08.22.09 # desowin: g#3528 and g#3529 08.22.12 # 3Gerrit review #3528 at https://gerrit.rockbox.org/r/c/rockbox/+/3528 : 3builds: Move the Sansa Connect to unstable by Solomon Peachy 08.22.31 # Cool 08.22.59 # So then the automatic build system will begin to build it next time? 08.23.50 # MarcAndersen: it's already being built with every commit; this will add it to the stuff retained nightly, and generate voice files etc. 08.23.53 # I can't wait to get this working. 08.24.25 # MarcAndersen: https://build.rockbox.org/data/rockbox-sansaconnect.zip 08.24.39 # Nice 08.25.38 # Build Server message: 3New build round started. Revision e6ee3dd17c, 297 builds, 9 clients. 08.26.20 # What is the difference between bootloader.bin and bootloader-connect.sansa? I see it is 8 bytes longer? 08.26.41 # header, but it's not accepted by OF bootloader 08.26.46 # Oh 08.26.49 # desowin: just added it to the themesite too. 08.27.06 # rockbox.sansa is the main application 08.27.15 # I know 08.27.31 # But still no usb here 08.27.56 # I'll give it some more time. 08.28.29 # usb won't come up automatically, you can either press the power button or replug 08.28.37 # the www change will land in ... 3 minutes. themesite will refresh on the quarter-hour after the build farm goes idle. 08.28.39 # I just tried both 08.29.18 # But I think I can take it from here, thanks a lot! 08.29.21 # if it boots linux, then it will takes some time before usb shows up 08.31.06 # and speaking of new port, I wouldn't consider sansa connect port to be new 08.31.25 # it just took me 10 years to exploit OF in software only way 08.31.37 # thanks to your work it's only now finally becoming usable :) 08.31.58 # (maybe like 3 weeks over these 10 years, but still) 08.32.49 # Yes. Also, in which source files is the voice numbers concattenated? I am going to try to make it say numbers like one and twenty instead of twenty one in danish. 08.34.39 # apps/talk.c 08.35.00 # Igor Poretsky has some patches in his fork that rework how numbers are spoken 08.35.25 # Ok. I don't know if I am skilled enough since I mostly use autoit... But I will at least take a look on how it does it now. 08.36.42 # How exactly do I get patches? Sorry if this is a stupid question. 08.37.49 # https://github.com/poretsky/rockbox/commit/f6de0015d55766402167d66a15b0e8179c5fc66a 08.37.55 # https://github.com/poretsky/rockbox/commit/f6de0015d55766402167d66a15b0e8179c5fc66a 08.38.16 # https://github.com/poretsky/rockbox/commit/73daf7da4df5fcb15c0f6d6206b83a7723b2c775 08.38.28 # (ignore the duplicate please) 08.38.56 # How do I apply these? 08.40.48 # Build Server message: 3Build round completed after 910 seconds. 08.40.50 # Build Server message: 3Revision e6ee3dd17c result: All green 08.54.32 # MarcAndersen: give me a few, I'm trying to rebase them against our current tree. 09.02.24 # I still have no usb connection unfortunately 09.02.38 # Maybe this device is dead... 09.03.20 # <_bilgus> I'd start checking cables 09.04.04 # It is this special sandisk cable that came with it. Like the 30 pin connector but not the same. 09.04.40 # Oh maybe the one from my c200 fits, just a second 09.04.45 # it might be OF welcome screen, press right (above the wheel) like 10 times and then press upper part of the wheel 09.05.13 # <_bilgus> speachy when you get a chance can you look over g#3527 Its over my head looks fine but would like your expert opinion 09.05.15 # 3Gerrit review #3527 at https://gerrit.rockbox.org/r/c/rockbox/+/3527 : 3file/fat: add utime function by James Buren 09.05.59 # Still nothing 09.07.10 # I'll have sighted assistance here in 10 minutes or so anyway, so we can find out what's wrong with this beast. 09.07.36 # MarcAndersen: https://gerrit.rockbox.org/r/c/rockbox/+/3530 09.07.44 *** No seen item changed, no save performed. 09.08.13 # there's a 'download' link on the right side below the "merge conflicts" pane, cut-n-paste the "cherry pick" instructions. 09.10.21 # and the themesite refreshed, 67 themes seem to pass checkwps on the Connect 09.11.09 Join massiveH [0] (~massiveH@ool-18e4e82f.dyn.optonline.net) 09.11.31 # I will look at this time and date thing after I get the thing to boot. 09.12.05 # it'll appear on build.rockbox.org on the _next_ build. 09.12.25 # and voice files will generate tonigh 09.12.27 # So it is merged into master now? 09.13.57 # _bilgus: I think it looks okay? 09.14.33 # MarcAndersen: Connect builds, I mean. that timedate patch is not, having only been compile tested on a single target so far 09.15.05 # (well, it's been in Poretsky's tree for some time, and on my list to port/merge, but I need to at least _run_ it first..) 09.15.32 # Build Server message: 3New build round started. Revision c174d3a544, 297 builds, 9 clients. 09.16.53 # I just got sighted assistance here. It says a 09.17.07 # MarcAndersen: that patch probably doesn't do what you want, but it should indicate a path forward. 09.17.11 # sandisk, then low battery, and then it dies. 09.18.58 # <_bilgus> battery is probably too discharged to safely charge 09.19.09 # keep it connected, don't mess with it 09.19.15 # the power button should be blue 09.19.28 # It is 09.19.32 # do not press power button as every time you do so it discharges more 09.19.36 # MarcAndersen: there isn't currently a mechanism to selectively reorder generic numeric voicing. 09.19.48 # OF bootloader drains more current than gets from USB 09.20.13 # so the only way to get initial charge is to pateintly wait 09.20.36 # Ok 09.20.46 # if anyone could comment on g#3530 I'd appreciate it. I combined two independent patches due to how they were related and stacked. 09.20.48 # 3Gerrit review #3530 at https://gerrit.rockbox.org/r/c/rockbox/+/3530 : 3Time and date format unification (Igor Poretsky) by Solomon Peachy 09.20.57 # <_bilgus> if a day of charge doesn't bring it back then you can try manually charging it use another liion battery and a resistor in a fire safe area 09.21.26 # Is the battery replacable in this thing? 09.21.29 # no 09.21.35 # what is the serial number on the back? 09.21.41 # <_bilgus> yes just not easily 09.21.43 # next to FCC logo 09.23.24 # MarcAndersen: would the "five and twenty" spoken ordering for Danish also apply to how years are voiced? 09.24.37 # I think so, the only real difference is the ones first and then the tens, so two thousand one and twenty is fine, or maybe two thousand and one and twenty 09.25.20 # Serial: UZB-ES20070309 09.26.37 # <_bilgus> he even added date and time to chessbox :) 09.26.38 # rockbox's year voicing currently reads "2021" as "twenty twenty one" -- would it need to be "two thousand one and twenty" ? 09.26.59 # MarcAndersen: this is FCC ID, the serial is painted above it (in very hard to read color) 09.27.35 # I would say. Maybe rasher or someone else from Denmark can verify. 09.28.20 # I'm curious about the expectations/norms of other languages too 09.28.27 # BH0705SZ1017860 09.30.58 # and with that patch it becomes "twenty hundred twenty-one" 09.31.04 # Pronouncing numbers for different languages sounds like a hard problem. 09.31.11 # Build Server message: 3Build round completed after 939 seconds. 09.31.14 # Build Server message: 3Revision c174d3a544 result: 0 errors 343 warnings 09.31.29 # In Danish you'd either want "two thousand one-twenty" or "twenty one-twenty" 09.32.16 # braewoods: ^^^ 343 warnings. :) 09.32.18 # That sounds ok. It's hard to say without listening to it 09.32.49 # rasher: and that same convention is used for years? 09.32.52 # MarcAndersen: it should have the old bootloader so once you get into recovery mode everything should go smoothly 09.33.38 # (new one in refurbished units should work as well, but I just didn't get anyone to report) 09.34.45 # I'm thinking it owuld be relatively simple to add a "one-and-twenty" vs "twenty-one" rule, but the question is if there are other quirks that need to be handled too. 09.35.17 # speachy: Actually that would be the convention for years. "twenty one-and-twenty" would be odd for a regular number 09.35.33 # Sure 09.35.55 # I always say two thousand one and twenty here 09.35.57 # So two-thousand one-and-twenty is the safest bet 09.36.27 # <_bilgus> speachy https://gerrit.rockbox.org/r/c/rockbox/+/3530/1/apps/talk.c#1213 09.37.15 # <_bilgus> oh nm 09.37.20 # <_bilgus> 0 and '0' 09.37.25 # so this patch's unifacion of "year" and "number" pronounciations is misguided. 09.38.31 # _bilgus: I'd think fractions should always be spoken digit-by-digit, so we don't end up with 0.000512 as " point zero zero zero five hundred twelve " 09.38.56 # that's right. after the point everything is digits. 09.39.39 # I'm going out for a few hours. Let's hope my sansa is awake when I come back... 09.40.01 # <_bilgus> agreed 09.42.05 # <_bilgus> ha, https://www.dw.com/en/eu-fines-german-carmakers-over-alleged-cartel-activities/a-58158329 09.42.30 # <_bilgus> wanna a cheap car buy a diesel gate VW 09.44.09 # <_bilgus> buddy has this nice turbo diesel bug I sure hope their rust proofing is good the metal work leaves things to be desired 09.44.43 # I'm gonig to pull out the fractional fixes into a separate patch. 09.45.14 # <_bilgus> oops i'm in the wrong channel sorry 09.55.23 # Build Server message: 3New build round started. Revision a8fd590003, 297 builds, 9 clients. 09.55.46 # _bilgus: g#3531 is the fractional rework 09.55.48 # 3Gerrit review #3531 at https://gerrit.rockbox.org/r/c/rockbox/+/3531 : 3talk: Always read out fractional values digit-by-digit by Solomon Peachy 09.59.53 # <_bilgus> is tbuf limited to numbers only? whats it do with malformed input '/' 09.59.58 # wait, that's what talk_spell already does. that patch is.. pointless. 10.04.25 # Build Server message: 3Build round completed after 540 seconds. 10.04.28 # Build Server message: 3Revision a8fd590003 result: 1989 errors 62 warnings 10.04.53 # wtf...? 10.08.12 # Build Server message: 3New build round started. Revision 78eb87f453, 297 builds, 9 clients. 10.19.08 # speachy: wtf indeed? 10.19.42 # next question. for voiced 24-hour format time, in English at least the convention is "21:00" is voiced as "twenty-one hundred hours" -- 3530 changes that to "twenty-one o'clock" which isn't correct for English, but what about non-English? 10.19.42 # <_bilgus> the law of unintended consequence? 10.20.14 # braewoods: the build going now is a reversion of my "fix", and a correct fix is queued. 10.20.36 # speachy: ah. i didn't know the fat header was even used on non-native ports 10.20.42 # <_bilgus> if you do oclock thats only for 12hr time then? 10.20.46 # because why would it be? 10.20.49 # * braewoods boggles. 10.21.14 # yeah, I tried nuking it as a fix but apparently the dirent structs are used in the file API. 10.21.37 # Build Server message: 3Build round completed after 805 seconds. 10.21.40 # Build Server message: 3Revision 78eb87f453 result: 0 errors 343 warnings 10.21.45 # Build Server message: 3New build round started. Revision 39b82afb45, 297 builds, 9 clients. 10.21.59 # what's the warning? utimbuf? 10.22.15 # i can revamp my API choice if it'd help 10.22.16 # yeah, that needs to comie from #including utime.h 10.22.46 # you can revert my PR and i'll work on a new version 10.22.49 # _bilgus: o'clock is 12h only, at least for English. 10.22.52 # err commit 10.23.07 # i didn't realize utime would be this muchfuss 10.23.34 # the current build running should go all green. 10.23.39 # oh. 10.23.42 # ok. 10.24.02 # bilgus was wanting some rework done 10.24.15 # i just wanted to wait until today since it was so late :P 10.24.37 # <_bilgus> so just pull head and start from there, stick to the prescribed interface will worry about the api later.. 10.25.22 Quit massiveH (Quit: Leaving) 10.25.26 # i had an alternative in time, our own "modtime" function or so. 10.25.35 # takes a single time_t and either a path or FD. 10.25.37 # so can any non-english speakers comment on 12/24h spoken time conventions 10.27.15 # <_bilgus> well you said posix pulled it so I'd stick to the native interface 10.27.32 # i'll update it 10.27.53 # we don't really use modtime 10.28.01 # err 10.28.04 # atime 10.28.14 # <_bilgus> for good reason.. 10.30.02 # 0900 would be "oh-nine-hundred hours". 1923 would be "nineteen twenty three hours" 10.33.18 # i'll work on this some more 10.33.47 # i'll see if this works with an existing FD or not 10.34.02 # truth is i don't know if the closing flush will overwrite my attempts to set the time 10.34.14 # so that's one thing i'd need to consider 10.34.47 # Build Server message: 3Build round completed after 783 seconds. 10.34.49 # Build Server message: 3Revision 39b82afb45 result: 0 errors 10 warnings 10.37.20 # ok, those remaining warnings are in teh android port. 10.37.44 # don't worry about it speachy, i'll work on fixing this need for utimbuf or w/e 10.38.23 # we can implement our own "modtime" for w/e else using the native APIs and don't need to emulate it for native 10.38.59 # just my first time messing with the FAT internals so not surprised there were some hiccups 10.40.39 # what do we plan to do when 2038 hits? 10.40.46 # most of our time_t are 32 bit signed 10.41.00 # assuming rockbox is even still relevant then 10.41.33 # oddly dos timestamps are pretty future proof up to around 2100 or so 10.49.35 # ok... basic redesign done. next up... 10.52.24 # time to see if i can use an existing FD 10.54.16 # i'll probably have to trigger a flush before doing my work 10.59.45 # Build Server message: 3New build round started. Revision a952cf52d5, 297 builds, 9 clients. 11.07.47 *** Saving seen data "./dancer.seen" 11.13.17 # Build Server message: 3Build round completed after 812 seconds. 11.13.22 # Build Server message: 3Revision a952cf52d5 result: 0 errors 10 warnings 11.47.56 # huh. the simulator builds fine with LTO. 11.54.12 Join amachronic [0] (~amachroni@user/amachronic) 12.01.45 # Build Server message: 3New build round started. Revision 0e1a90ea1d, 297 builds, 9 clients. 12.13.56 # pcap format just switched to unsigned 32 bit which is good until 2106 12.14.24 # Build Server message: 3Build round completed after 759 seconds. 12.14.33 # Build Server message: 3Revision 0e1a90ea1d result: 0 errors 10 warnings 12.15.01 # Build Server message: 3New build round started. Revision 17f7dfb9d2, 297 builds, 9 clients. 12.17.10 Quit Romster (Ping timeout: 268 seconds) 12.21.39 Join Romster [0] (~romster@user/romster) 12.21.47 # sent you a more working link, amachronic 12.23.23 # thanks, got it. 12.26.36 # Build Server message: 3Build round completed after 695 seconds. 12.26.39 # Build Server message: 3Revision 17f7dfb9d2 result: 0 errors 10 warnings 12.27.29 Quit j-r (Ping timeout: 252 seconds) 12.27.51 # speachy, _bilgus: small problem in my tests. i managed to write a FD version of "modtime" but it doesn't work at all with write enabled FDs. it only works with read only ones. i have two options. i can add some kind of override inside of FAT to apply a different set of timestamps during the close process or just consider modtime as only a good idea during a separate file phase. in which case i'd 12.27.53 # switch back to taking a file path since it's pretty pointless to take a FD if you don't work on both kinds. 12.29.20 # i'm leaning towards the latter due to how narrow the use case for this is. i don't think it's a good idea to introduce hacks into the FAT driver to accomodate this. 12.29.33 # thoughts? 12.31.23 # it's funny how it's a problem even when i don't write anything during closing 12.31.29 # err before 12.31.37 # i just open for writing 12.34.07 # g#3535 12.34.09 # 3Gerrit review #3535 at https://gerrit.rockbox.org/r/c/rockbox/+/3535 : 3DM320: Regorganize LCD and TTB memory layout by Tomasz Moń 12.34.37 # this trades off the (MMU) 1 MiB alignment for 858 KiB larger audio buffer 12.34.58 # as we don't do anything with MMU, I strongly favor larger audio buffer 12.37.11 # braewoods: tailor it for the specific use case until we have a need for sometihng more general. 12.38.01 # ok. i'll just have it work as a separate open phase. 12.38.20 # that won't require me to modify how we flush data. i'm concerned i'd introduce new bugs by doing so. 12.38.58 # thanks 12.41.44 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:f86b:93ab:cfff:61aa) 12.42.29 Quit Romster (Ping timeout: 255 seconds) 12.47.53 Join Romster [0] (~romster@user/romster) 12.49.36 # This stupid connect still says battery low 12.54.41 # I had mine discharged for few years and then just plugging it for a day did the trick 12.55.05 # that is, get from bootloader to firmware and only then it actually charges properly 12.55.18 # Ok. Waiting time... 12.55.29 # you might want to not enter recovery mode before it is fully charged 12.55.45 # That sounds like a good idea 12.56.27 # just boot OF and leave it charging, if there's welcome screen just keep pressing right and then upper part of the wheel 12.56.44 # OF menu scrolling should be audible 12.56.52 # speachy: https://twitter.com/noradotcodes/status/1412741339771461635?s=21 did you see this? 12.56.58 # if true oh boy. 12.57.19 # their software may be assisting in copyright or license infringement. 12.57.33 # Only sandisk, battery low, then loop forever 12.58.28 # that's still in bootloader, not even booting linux (which I call OF) 12.58.32 # yep. I'll leave the folks with deeper pockets to take them to task. 12.58.58 # Ok. So I should just wait forever? 12.59.41 # probably leave it overnight and check tomorrow it is is any better 12.59.47 # MarcAndersen: no idea. your unit's battery may be completely worn out. hard to say at this point. 12.59.47 # Will do 13.00.15 # i usually replace batteries in used electronics if i can, especially if i'm planning to keep them. 13.00.18 # OF bootloader has a bug in it regarding the charging 13.00.40 # Which bug 13.00.55 # getting out of the low battery is taking very long, then when in proper firmware it works 13.01.07 # that they mention in linux init scripts ;-) 13.01.24 # My ipod classic 6g and zen x-fi does something simular 13.02.44 # also if you get into recovery mode and leave it connected, it'll eventually drain the battery and get you to the low battery problem again 13.02.57 Join lebellium [0] (~lebellium@2a01:cb10:2e:2000:69ec:1efa:f053:e15) 13.02.58 # so first step is just to try to boot OF and charge it 13.07.13 # Build Server message: 3New build round started. Revision a0f1236e88, 297 builds, 9 clients. 13.07.50 *** Saving seen data "./dancer.seen" 13.18.05 Quit amachronic (Ping timeout: 252 seconds) 13.18.52 # Build Server message: 3Build round completed after 699 seconds. 13.18.56 # Build Server message: 3Revision a0f1236e88 result: All green 13.33.51 Join sadjhflj333 [0] (~sadjhflj3@2607:fb90:17c7:aba2:ceab:9048:ad08:6407) 13.48.34 Quit sadjhflj333 (Quit: Konversation terminated!) 13.51.32 # g#3536 13.51.34 # 3Gerrit review #3536 at https://gerrit.rockbox.org/r/c/rockbox/+/3536 : 3file/fat: rework utime function as modtime extension by James Buren 13.51.49 # This is my reworking. It should be a minor improvement and good enough for now. 14.20.07 # _bilgus: you mentioned wanting to use this for themes. did you have any ideas for how that would work? 14.21.10 # if all the theme files are loaded into RAM, we could just load from the ZIP instead of extracting them. 14.22.01 # for now i'm just going to focus on my use case 14.22.22 # but there's nothing stopping us from adding custom loaders that use this to load files directly into RAM from an archive 14.23.10 Quit desowin (Ping timeout: 272 seconds) 14.23.54 Join j-r [0] (~j-r@p5df2ecee.dip0.t-ipconnect.de) 15.07.51 *** Saving seen data "./dancer.seen" 15.57.18 Join LiteralBrainlet [0] (~LiteralBr@c-73-128-188-136.hsd1.va.comcast.net) 15.57.28 # howdy fellas 15.57.45 # I have a problem installing RB on my iPod Classic 6gen 15.58.31 # I get stuck on 15.58.49 # "action required press and hold select + menu" 15.59.50 # In the past I successfully got the software on the iPod manually using a friend's mac, but even after hard resetting the device I'm still stuck with Apple's OS 16.00.14 # A1238 - 160gb version 16.08.00 # LiteralBrainlet: so what does that come after? 16.45.39 # oh fuck disregard, after 2 years of attempts I finally got it to work 16.46.22 # Although, whenever I plug the device into my PC Windows prompts me to format it 16.46.56 # erm. you usually need to format iPods with windows itunes so it'll be FAT based. 17.07.44 # I did. I originally formatted it as FAT32, but now it keeps telling me to do it again. I don't think it matters because I can still move music files onto the iPod 17.07.55 *** No seen item changed, no save performed. 17.34.25 Quit lebellium (Quit: Leaving) 17.45.03 Quit ZincAlloy (Quit: Leaving.) 17.53.34 # sweet. Got the X3 compiling cleanly with LTO! 17.54.11 Quit LiteralBrainlet (Quit: Client closed) 17.56.28 # just the main binary, plugins are shot. 17.59.13 Join cockroach [0] (~blattodea@user/cockroach) 18.35.32 # <_bilgus> braewoods, for the time being its fine just to unpack to a directory we can integrate later 18.43.30 # _bilgus: ok. i'm just waiting for my next review. 18.45.42 Quit cockroach (Quit: leaving) 18.45.59 Join cockroach [0] (~blattodea@user/cockroach) 18.54.00 # <_bilgus> i'm looking at it but busy atm 18.55.02 # ok 19.03.59 # Build Server message: 3New build round started. Revision a9f36efa62, 297 builds, 8 clients. 19.05.34 # <_bilgus> that'll be much easier since its custom you might wanna add flags to hit atime or at least have the flag in the proto 19.07.59 *** Saving seen data "./dancer.seen" 19.21.05 # Build Server message: 3Build round completed after 1025 seconds. 19.21.08 # Build Server message: 3Revision a9f36efa62 result: All green 19.54.22 # Build Server message: 3New build round started. Revision 2c984f3714, 297 builds, 8 clients. 20.09.12 # Build Server message: 3Build round completed after 891 seconds. 20.09.17 # Build Server message: 3Revision 2c984f3714 result: All green 20.37.33 # speachy: isn't it a bit early for LTO? 20.50.32 # the core is solid. the X3 main binary shrinks by ~4%. 20.50.50 # I have some codecs and plugins building, but others are going boom for a reason I don't yet understand. 20.55.01 # <_bilgus> how does that work with plugins and codecs sharing the same address space? 20.55.36 # it's just fancy compile-time crap; it still has to confirm to the appropriate link map 20.57.02 # <_bilgus> I'm surprised it works at all tbh 20.57.05 # what's going on (I think) is that the LTO is stripping out the codeclib's memcpy() 20.57.19 # because we force -nostdlib etc 20.57.51 # what surprised me is that LTO on the main (X3) binary only generated a single warning. 21.03.44 # Build Server message: 3New build round started. Revision 2e9b93dc5d, 297 builds, 8 clients. 21.08.00 *** No seen item changed, no save performed. 21.16.04 # Build Server message: 3Build round completed after 740 seconds. 21.16.06 # Build Server message: 3Revision 2e9b93dc5d result: All green 21.16.09 # speachy: what does rockbox do with trailing slashes in path? 21.16.17 # is 21.16.24 # /a/b/c the same as /a/b/c/? 21.16.51 # if it's a directory, I don't think it matters. but that trailing slash is an illegal filename. 21.19.05 # but, as always, use the source, luke.. 21.41.05 # strange seeing a function return ssize_t when it can't return negatives by design 21.44.00 # <_bilgus> some of those are because of sticking to prototypes others might be erroneous 21.45.14 # it's kinda moot anyway since unless we deal with RAM above 2GB we'd never hit it 21.47.02 # found a small optimization for my code for path construction 21.47.27 # by writing the root directory only once i can reduce some extraneous writes, saving a bit of time 22.14.11 Quit cockroach (Quit: leaving) 23.08.03 *** Saving seen data "./dancer.seen" 23.19.14 Quit F3l1x_10m (Read error: Connection reset by peer) 23.35.17 Join F3l1x_10m [0] (~Al3x_10m@user/f3l1x-10m/x-3393542)