--- Log for 01.08.102 Server: lerouge.openprojects.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 12 days and 9 hours ago 00.02.10 Join Bagder [0] (~daniel@as3-3-2.ras.s.bonet.se) 00.54.13 *** Saving seen data "./dancer.seen" 01.18.47 Part Bagder 01.51.03 Join MeRWiN [0] (~merwin@63.98.122.204) 01.56.48 Quit MeRWiN () 02.11.49 Join mistaRx [0] (mistaX@t4o75p117.telia.com) 02.30.03 Quit datazone ("Client Exiting") 02.37.47 Quit mistaRx () 02.45.56 Quit Tumm (Read error: 113 (No route to host)) 02.54.17 *** Saving seen data "./dancer.seen" 03.32.24 Join MeRWiN [0] (~merwin@63.98.122.204) 03.48.51 # how often is a tick? 04.00.42 # a tick or a tock? 04.04.22 # heh 04.04.59 # OK, any clue on how to sleep() a thread from within wps.c? 04.09.57 # give it a bed. Some nice pillows will help too. Maybe some soft music and warm milk. 04.15.15 Join MrHad [0] (~chad@sub18-251.member.dsl-only.net) 04.24.53 # that is true 04.24.56 # i should try that 04.25.05 # although i think the archos wouldn't like that too much 04.28.58 Join Bombelman [0] (george@206.61.44.18) 04.29.04 # hi 04.29.39 # anyone here ? 04.30.13 Quit Bombelman (Client Quit) 04.54.19 *** Saving seen data "./dancer.seen" 05.03.26 # Hi all great project. 05.03.27 Quit MeRWiN (Read error: 104 (Connection reset by peer)) 05.09.45 Join datazone [0] ([d8A2tDIdR@207.136.36.203) 05.25.32 Quit elinenbe ("User pushed the X - because it's Xtra, baby") 05.28.13 Nick dwihno is now known as dwihno|gone (dwihno@193.180.246.67) 05.30.33 Quit MrHad (Remote closed the connection) 05.52.57 Join MeRWiN [0] (~merwin@63.98.122.204) 06.16.32 Join elinenbe [0] (trilluser@pcp02254422pcs.wanarb01.mi.comcast.net) 06.24.29 Join elinenbe_ [0] (trilluser@pcp02254422pcs.wanarb01.mi.comcast.net) 06.24.30 Quit elinenbe (Read error: 104 (Connection reset by peer)) 06.54.24 *** Saving seen data "./dancer.seen" 06.56.53 Quit MeRWiN () 07.27.09 Join Linus [0] (~linus@193.15.23.131) 07.32.56 # morning Linus. 07.33.00 # I must head to sleep soon 07.33.10 # morning 07.34.59 # well, I am going to sleep. Good luck on the project today. What do you think about dynamic watermarks? 07.35.11 Nick elinenbe_ is now known as elinenbe|snooze (trilluser@pcp02254422pcs.wanarb01.mi.comcast.net) 07.35.36 # i don't think it is the solution to Alex's problem 07.35.52 # my unit doesn't skip 07.36.00 # on 320kbit/s songs 07.36.42 # but, wouldn't that be a more elegant solution anyway? 07.37.17 # yeah, probably 07.40.48 # does anybody else experience skipping? 07.49.01 Join MeRWiN [0] (~merwin@63.98.122.204) 08.09.56 # hey linus 08.10.24 # yo 08.10.48 # I tried to get some sort of scroll_sleep function going, but couldn't quite get it 08.10.55 # ok 08.11.08 # without creating propriatery code inside of lcd.c 08.11.21 # ie: linking it to wps.c 08.11.24 # and such 08.11.50 # why? 08.12.34 # well, basically I didn't know how to sleep a particular thread from within wps.c 08.13.30 Join Bagder [0] (~daniel@as3-3-2.ras.s.bonet.se) 08.13.39 # morning 08.13.40 # morn 08.14.27 # Bagder: what time is it over there? 08.14.39 # 08:12 am 08.14.49 # you get up early :) 08.14.56 # i was here at 7 08.15.05 # I'm going to have to get up at 8:30am east coast time this morning... it's already 2:15 am 08.15.18 # Bagder and I live in the same town 08.15.19 # strange strange people :) are both of you at work? 08.15.25 # * Bagder nods 08.15.27 # yup 08.15.40 # * Bagder eats his breakfast sandwich right now 08.15.42 # ahh... that explains it. I usually get to work around 9 or 9:30... 08.15.58 # unless i'm traveling (80% of the time) at which point i'm at work 24/7 08.17.14 # I've decided that i'm a much better UI person for now... until i learn the code more deeply 08.18.03 # I fsck'ed my disk last night, and yes it had some bad clusters 08.18.58 # ouch 08.19.12 # Bagder: been shakin' and droppin' your rockbox? 08.19.24 # no 08.19.31 # I don't know why it happened 08.19.36 # original hd? 08.19.40 # yeps 08.19.44 # bah, return it to archos 08.23.03 # MeRWiN: use a boolean in scroll_thread called, for example, scroll_allowed 08.23.51 # excuse me? i didn't quite get that 08.25.18 # even easier, set scroll_count to 0 to stop scrolling, and set it to 1 to continue 08.26.10 # but how does scroll_thread know to set the scroll_count to 0? you need to perform the sleep inside of scroll_thread 08.27.18 # add a function, pause_scroll() that sets the count to 0 08.27.32 # and another function, resume_scroll() that sets it to 1 08.27.42 # and call those from wps.c 08.27.54 # Linus: how do i tell how much time has passed then? 08.28.06 # wps has to know that 08.28.32 # that is the easy solution 08.29.26 # the only way i see of doing that is using the remaining time in the song, but what if there is only like 1 second left in the song and you want to sleep for 5 seconds 08.30.53 # why does the song time has anything to do with the scroll pause? 08.30.57 # we should offer some kind of timeout-functionality 08.31.08 # Bagder: i have been thinking of that 08.31.14 # how do i tell elapsed time i mean 08.31.26 # a soft timer that posts events, and a button_get(timeout) 08.31.38 # MeRWiN: current_tick 08.31.46 # how long is a tick 08.32.06 # a tick is 1/HZ seconds long 08.32.15 # so 3 seconds is HZ*3 08.32.19 # today HZ = 100 08.32.25 # that's what i thought HZ meant 08.32.34 # thus, a tick is 10ms 08.33.39 # ok, so then would I create a thread and have it terminate when it hits the appropriate amount of ticks? 08.33.47 # no 08.34.02 # no dynamic threads please ;-) 08.34.07 # aww 08.34.10 # we can't kill threads 08.36.10 # maybe it is time for an timeout_event function? 08.36.19 # what is that? 08.36.43 # yes, I think it would be a useful addition 08.38.34 # MeRWiN: it would send an event to a queue after an amount of time 08.38.48 # ahhh... yes, we need that :) 08.40.16 # woo! that simple addition worked... just use lcd_pause_scroll() before calling display_keylock_text() and lcd_resume_scroll() after it 08.40.19 # works like a charm :)\ 08.41.06 # or rather, i should do it inside of display_keylock_text() 08.44.17 # in today's solution, yes 08.44.35 # tomorrow, we should use timeout_event 08.45.09 # hehe, i have doubled the bitswap speed by putting the code in internal RAM 08.45.32 # nice! 08.46.05 # either way, for the display_keylock_text you need to do it this way i think.... it needs to keep the screen clear and not let anything else on the screen update while it's being displayed. that's why the sleep function is inside of the display_keylock_text() function 08.47.14 # i think draw_screen should do the screen updates, and output the "keylock ON" message while the timeout hasn't occurred yet 08.47.33 # would it even know that the timeout is there? 08.48.01 # yes, because you would use a state variable that it can read 08.48.26 # hmm.... 08.48.32 # like enum display_state(NORMAL, KEYLOCK, ...) 08.48.47 # and draw_screen whould check that 08.49.00 # and muted? 08.49.07 # and whatever 08.49.41 # that seems like it would just over-complicate things 08.49.58 # really? 08.50.17 # the sleep() effectively slows down the responsiveness 08.50.24 # it is bad, bad, bad 08.50.50 # * Bagder agrees with Linus on this 08.50.55 # that is true... it would get rid of the problem with pressing the keylock key 5 times in a row taking 5 seconds to get through 08.51.00 # yes 08.51.24 # does current_tick ever reset itself? 08.51.32 # seems as if that number would grow big very quickly 08.51.38 # yes it wraps 08.51.53 # there are macros in kernel.h that takes that into account 08.52.04 # TIME_BEFORE() and TIME_AFTER() 08.52.19 # look in kernel.c and watch how sleep() is implemented 08.52.46 # k 08.53.23 # what does continue() do? 08.53.45 # the continue keyword starts the loop over again 08.54.26 *** Saving seen data "./dancer.seen" 08.54.44 # that is, it goes to the top of the loop without executing the rest of the loop body 08.54.50 # ahh... 08.55.00 # like "next" in Perl 08.58.09 # I don't quite understand how you could implement a timeout function that wouldn't interrupt other code 08.58.22 # without creating a different thread for it 08.59.43 # you mean how to implement timeout_event()? 08.59.48 # yeah 09.00.32 # i would implement timeout_event by adding a list of timers that are decremented by the tick interrupt 09.00.56 # and the tick interrupt code would send an event to the queue that "owns" the timer that has reached 0 09.01.06 # a kernel functionality 09.01.40 # ahhh... something just a bit above my head right now. 09.01.56 # i can implement that later if you wish 09.02.09 # if you can implement it, i can fix code to use it :P\ 09.02.32 # good, but it'll have to wait a little. many things to do right now... 09.02.35 # coffee! 09.02.42 # conceptually, i've got threading down... actually in practice i'm not so good at it 09.03.05 # good, learning by doing is the best practice 09.04.09 # I wish I had a laptop that worked right. heh. I'd do it on the plane ride home if I did. 09.07.28 # time for sleep 09.07.39 Nick MeRWiN is now known as MeRWiN|Sleep (~merwin@63.98.122.204) 09.10.24 # night MeRWiN 09.18.13 # http://daniel.haxx.se/logo-contest/rockbox3540.png 09.18.21 # this image is broken, isn't it? 09.18.27 # mozilla shows it very oddly 09.18.32 # hey can the firmware be able to read from the HD while in usb mode? 09.19.21 # PsycoXul: no 09.19.36 # oh :/ 09.19.39 # Bagder: it is a large "Box" 09.19.44 # Bagder: all i can see is a really big "box" in the middle 09.20.01 # yeah :-/ 09.21.15 # convert doesn't manage to create a good png from the tif 09.22.00 # http://daniel.haxx.se/tshirt-contest/ 09.22.10 # anything preventing me from announcing this asap? 09.24.08 # Bagder: maybe we should discuss it you and me first 09.24.18 # yes 09.24.29 # Bagder: switch to the secure frequency 09.24.34 # hehe 09.24.38 # roger that ;-) 09.30.35 # * adi|home wants in on it too 09.30.37 # wahhhhhh 09.47.11 # Bagder: why can't i access any of those webpages? :p 09.47.18 Nick MeRWiN|Sleep is now known as MeRWiN|SleepWalk (~merwin@63.98.122.204) 09.47.21 # I moved it 09.47.28 # aww 09.47.35 # they are not official yet 09.47.39 # Linus and I are discussing it just now 09.47.50 # I don't even know what they are. heh 09.47.57 # hehe 09.48.11 # I've officially given up on sleep 09.50.29 # * PsycoXul starts designing :p 09.50.30 # mwahahaha 09.53.11 # :-) 09.56.54 Quit MeRWiN|SleepWalk () 10.20.15 Join MeRWiN|SleepWalk [0] (~merwin@63.98.122.204) 10.20.19 Nick MeRWiN|SleepWalk is now known as MeRWiN (~merwin@63.98.122.204) 10.20.29 # anyone around willing to take a look at my resume and offer suggestions? 10.20.43 # sure 10.20.48 # where can i find it 10.20.50 # k.. what format you want it in? 10.20.57 # i can dcc it to you in a min if you want 10.21.00 # ok 10.21.02 # in doc format if you please 10.21.06 # np.. 10.21.06 # i think dcc will work. 10.21.17 # Hmm, are these internal RAM changes speedups? faster than the flash rom? 10.21.33 # faster than Dynamic RAM 10.21.45 # internal RAM is on the cpu? 10.21.54 # Linus: what will this speed up? 10.22.07 # double speed disk read and bitswap 10.22.09 # way cool. 10.22.20 # we need faster disk reading, so this is great 10.22.21 # i'm stunned. 10.22.21 # definately 10.22.28 # i havent benchmarked the thread swutch though 10.22.45 # but it should be way faster now 10.22.58 # please try it out 10.23.11 # when is it going to be in cvs? 10.23.31 # it is now 10.23.43 # that's how the others found out 10.23.52 # how often are things updated on the webpage then? 10.24.04 # every X minutes 10.24.44 # but some of us have joined the CVS update mailing list 10.24.54 # i try clicking on anything in the "batch" column on the daily build page and it shows only a blank page 10.24.59 # so we get instant CVS activity reports 10.25.20 # Must upgrade by recorder right away. 8-) 10.25.37 # the "batch" column? 10.25.54 # ah 10.25.55 # CVS compile status on the daily build page... 10.25.57 # MeRWiN: blank? no. i get a CVS history report 10.26.03 # what browser? 10.26.12 # they should cvs logs to me 10.26.12 # Linus: IE... it was just working 10 minutes ago 10.26.14 # show 10.26.46 # it is still working for me 10.27.39 # I'm going to reboot... i think my stupid compaq is freakin' 10.27.42 Quit MeRWiN () 10.35.33 Join MeRWiN [0] (~merwin@63.98.122.204) 10.36.27 # heh, that looks much better 10.37.11 # goodie 10.39.19 # The new build does not seem to boot for me. 10.39.30 # The thing boots to the archos firmware. 10.39.39 # uuh 10.39.58 # hes: try again 10.40.02 # copy it over again 10.40.21 # I'm already doing my 3rd try 8-) now building again too. 10.40.51 # hessu@funk:/opt/src/archos/src/build$> mount /archos/ 10.40.51 # hessu@funk:/opt/src/archos/src/build$> md5sum ajbrec.ajz /archos/ajbrec.ajz 10.40.51 # 15e91badcd26c3e281f1236347f23f26 ajbrec.ajz 10.40.51 DBUG Enqueued KICK Hes 10.40.51 # 15e91badcd26c3e281f1236347f23f26 /archos/ajbrec.ajz 10.40.51 # hessu@funk:/opt/src/archos/src/build$> umount /archos/ 10.41.18 # Seems to be ok (i invalidated the cache after the copy by disconnecting and unmounting) 10.41.43 # hmm... 10.41.46 # mine booted to archos too 10.41.49 # Won't bood. 10.41.51 # Won't boot. 10.42.20 # I didn't even know it could boot into archos firmware if the file is there 10.42.27 # apparently it can :) 10.42.38 # It can, i've seen it with a broken firmware before 10.42.54 # i'm doing a make clean and remake it 10.43.03 # so how does it know when to run the internal? 10.43.10 # Bagder: yeah of course it can.. if it fails to boot the file 10.43.25 # yes, but the scramble and things should be fine here 10.43.41 # hehe.. the archos.mod file is 318k :) 10.43.46 # Bagder: when the file is no good, or over ~200K according to my tests on my player, it boots the internal rom 10.43.52 Part Bagder 10.44.03 Join Bagder [0] (~daniel@as3-3-2.ras.s.bonet.se) 10.44.10 # Bagder: my archos.mod is 318k 10.44.18 # whoops 10.44.19 # gosh 10.44.34 # -rw-rw-r-- 1 hessu hessu 364470 Aug 1 11:38 ajbrec.ajz 10.44.41 # yeah, too big that's why 10.44.41 # whoa! 10.44.44 # it isn't loaded 10.44.53 # Linus changed the link control file 10.45.02 # I think it needs to be re-looked at :) 10.45.05 # maybe i broke something really bad 10.45.16 # Linus: yours booted? 10.45.17 # amen 10.45.19 # :-) 10.48.01 # well this is problematic with such a nice feature added 10.48.27 # which feature was added? 10.48.28 # This is as bad as microsoft... add one optimization and the code size multiplies by 10 :) 10.49.10 # adi|work: go to the home rockbox page 10.49.28 # adi|home: check out the cvs updates 10.49.48 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 10.49.48 # * adi|home is lazy :) 10.50.00 # adi|home: things were moved into internal RAM 10.50.07 # speeds up stuff about 100% 10.50.11 # some stuff 10.52.13 # got ya 10.52.39 # what exactly is that doing? 10.52.46 # * adi|home isnt a hard wear guy too much 10.52.50 # got me :) 10.53.00 # i just know that it's faster 10.53.01 # executes code in a different ram location 10.53.03 # lol 10.53.05 # faster ram 10.53.30 # Bagder: could you give a "laymens, adi is a dumb post" kinda explaination of how we got there? 10.53.57 # we have "internal" and "external" ram on the CPU 10.54.11 # we can have code in both 10.54.20 # executing code in the internal ram is faster 10.54.25 # okay... 10.54.27 *** Saving seen data "./dancer.seen" 10.54.34 # up until now, we only used the external one 10.54.39 # is there any similarity for this to a desktop pc? 10.54.46 # not really 10.54.48 # * adi|home tries to draw a mental map 10.54.51 # nods 10.55.09 # okay, so internal and external ram 10.55.16 # it's like if you insert two different SIMMs in a PC, one is fast and one is slow 10.55.23 # * adi|home nods 10.55.27 # that makes sense.. 10.55.39 # the external one is of course much bigger than the internal 10.55.43 # nods 10.55.57 # since its bigger, bigger address space, slower look ups? 10.56.04 # or is there another reason its slower? 10.56.32 # dynamic ram is slow 10.57.41 # * adi|home avoids driving you nuts like he did to his science teachers, always asking 'why?; 10.57.55 # okay.. so when we boot, we load from ext ram to int ram 10.58.01 # how exactly is that done? 10.58.10 # do we write to a specifc location in the int ram? 10.58.22 # and the processor just knows to pull from there if there is data? 10.58.36 # the different rams are on different addresses 10.59.15 # so you just reference the correct address when you go to write.. got ya.. 10.59.26 # correct 10.59.30 # so do we know what is wrong with the current code? 10.59.48 Join yro [0] (~yves@ns1.alcove-solutions.com) 10.59.53 # Hi there 10.59.56 # hey yro 11.00.06 # okay.. one last question on this... 11.00.11 # hehe 11.00.19 # i just committed a correction to the linker scripts 11.00.23 # how are we deciding what does and does not go into the ram? 11.00.45 # adi|home: the internal ram is *very* small, we can only have a few selected and important functions there 11.00.50 # adi|home: you set an attribute to the function, telling which section it should go to 11.01.10 # look at thread.c for example 11.01.32 # Linus: so a CVS update should fix it? 11.01.41 # it does, I just tried 11.01.42 # k... 11.01.59 # * adi|home hasn't updated his cvs version in like 2 months 11.02.00 # * adi|home smirks 11.02.11 # mine is still 318686 11.02.38 # Linus: did you fix the player version too? 11.07.52 Join notch [0] (hidden-use@212.250.215.13) 11.09.12 # fixed 11.09.30 # thanks :) worked 11.09.35 # or at least it's the correct size now 11.10.39 # The internal RAM is 4Kbytes 11.11.02 # and i have second thoughts about putting the LCD frame buffer in iram 11.11.26 # putting data in iram does not give that much impact 11.11.41 # code is better 11.11.47 # it seems as if the disk spins down very quickly 11.12.15 # Linus: so maybe lcd_update() should go there instead 11.12.19 # yes 11.12.53 # Linus: is there any way to keep the disk spinning for say like... 3 seconds? (or at least when you're switching tracks) 11.12.59 # just curious 11.13.32 # MeRWiN: the disk spin down timeout is 5 secs 11.13.39 # or at least, should be 11.14.14 # but not when playing music 11.14.33 # is there a way to set it to 5 second spindown when switching tracks? 11.14.35 # the mpeg loader spins down the disk as soon as the track has loaded 11.15.00 # MeRWiN: of course there is a way 11.15.07 # I think that may be part of the problem with not being able to change tracks correctly immediately after loading a track 11.15.07 # this is software 11.15.59 # the disk spindown is not the track switch problem 11.16.23 # it is the MPEG_NEED_DATA and MPEG_SWAP_DATA event queue 11.16.27 # would leaving the disk spinned up for a couple seconds speed up immediate track changes though? 11.16.30 # WHOA 11.16.53 # the speed increase is really noticeable, I didn't expect it to matter _this_ much 11.17.12 # very much faster while browsing directories & starting playback 11.17.25 # MeRWiN: all disk accesses would of course be faster if the disk didn't spin down 11.17.27 # will we see a noticable increased battery life time? 11.17.31 # yes 11.17.35 # i think so 11.17.57 # Linus: where would I go to change the spindown time on track changes? 11.18.22 # there is no such thing in the code that takes care of track chenges 11.18.37 # or rather, spindown time when playing 11.18.44 # you can remove the ata_spindown call in mpeg.c 11.18.50 # k 11.19.16 # then it will always wait 5 secs before it spins down 11.19.28 # isn't that spindown causing problems if another thread is using the disk while it is called? 11.19.55 # there is no ata_spindown in mpeg.c 11.20.04 # there's an ata_sleep though 11.20.10 # same thing 11.20.12 # k 11.20.27 # Bagder: no, the mutex takes care of thet 11.21.00 # Linus: yes, but it will make the other thread perform worse, right? 11.21.24 # and require an extra spinup 11.21.41 # Bagder: of course 11.22.02 # do you have a better idea? 11.22.26 # Linus: removing the ata_sleep speeds up an immediate track change about 200%... probably uses a bit more battery though 11.22.54 # Linus: well, it would be if it would somehow be able to detect that the other thread uses the disk 11.22.57 # Linus: and also fixes the playlist immediate trackchange problem!!! 11.24.31 # it could be compensated for somewhat by changing the spindown time to 3 seconds from 5... seems as if that may be sufficient 11.25.25 # Linus: wouldn't it be possible to instead of doing ata_sleep(), just set a timeout on like 0.5 seconds, so that if another thread is using the disk within that time, it won't spindown? 11.26.19 # you mean that mpeg.c only would alter the timeout instead of calling ata_sleep() 11.26.26 # yes 11.26.31 # hmmm 11.26.36 # the timeout would have to be set back though... 11.26.53 # yes, but I guess that anything that uses the disk will do that 11.27.34 # the ata_sleep() seems to be a problem in any case 11.28.14 # i just did the coolest thing 11.28.31 # what would that be 11.28.31 # you streaked across your work office? :-P 11.28.34 # haha 11.28.58 # instead of telling the disk to go to sleep, i just shut off the power to it 11.29.15 # and it works 11.29.25 # what a battery saver! 11.29.30 # hehe 11.29.34 # hmm... would that hurt it at all? 11.29.39 # i guess not 11.30.06 # except that it works only on the recorder 11.30.09 # ahh 11.30.50 # I think it's safter to shut of the power only when you know you are not reading writing to the disk... 11.32.20 # but I'm guessing that's the case? 11.32.20 # notch: of course 11.32.41 # the sleep is done only when nobody is accessing the disk 11.32.57 # even before my power down change 11.33.05 # it is essential 11.33.27 # how much battery drain would increase by getting rid of the ata_sleep in mpeg.c? 11.33.41 # but i don't think the power down will increase the battery life that much 11.34.07 # Linus: it's nice to be able to change the song within 5 seconds of starting it and not have to spin up the drive 11.34.10 # :) 11.35.10 # how about this: 11.35.37 # directory reads sets the timeout to 5 secs, and file reads set it to 0.5 sec 11.35.49 # Linus: make it 2 and you've got a deal :) 11.35.50 # heh 11.36.16 # i smell config options... 11.36.23 # no.. 11.36.24 # thats just me 11.36.26 # AHH!! I'll write that one :) 11.36.28 # i haven't showered yet 11.36.38 # * Bagder chuckles 11.36.42 Join ripnetuk [0] (~george@ripnet.fsnet.co.uk) 11.36.54 # Linus: config options i can do. heh. create a new global variable? 11.36.57 # http://www.asmparty.net/cam/webcam.jpg ... asm '02 is opening 11.37.04 # Linus: 5 / 0.5 is fine to run as a test to start with 11.37.07 # that would make two hard disk sleep timers 11.37.26 # oh my god... a stadium full of geeks 11.37.30 # we need to think about this 11.37.37 # Hes: What was the link? 11.37.46 # Linus: it could be one timer still, only raised to 5 or 0.5 by different functions 11.37.51 # notch: ? 11.37.58 # maybe we don't want playlist file reads to timeout that quickly? 11.38.12 # Bagder: i was talking about the config options 11.38.12 # Linus: why not? 11.38.16 # ah 11.38.25 # I don't think we need them as config options yet 11.38.40 # starting to play a playlist would require two spindowns 11.38.46 # why? 11.38.57 # Bagder: config would be good... you either get longer battery life, or quicker track changes 11.39.23 # read playlist (0.5s timeout)...parse it...scramble it...start playing first somg 11.39.43 # the disk will spin down before the first song starts playing 11.39.45 # Linus: hm, yes I guess you're right, for big playlists it'll take longer than 0.5 11.39.54 # will it be less than 1 second still? 11.40.02 # but then, the playlist code could deliberately prolong the time-out 11.40.07 # about 1 sec per 1000 tracks 11.40.16 # Bagder: that's true 11.40.20 # Linus: the load time, yes 11.40.21 # Hes: Guess I'm not a geek! :-) 11.40.28 # Bagder: delay it to a few seconds 11.40.57 # Linus: the post-load code will not take 1 sec per 1000 tracks 11.41.10 # it is only a fraction of a second on my 3200 song playlist 11.41.12 # notch: You should be seeing over 3000 nerds in that webcam in a single shot tomorrow evening 8-) 11.41.12 # meybe not 11.41.26 # and over the weekend... slightly less today. 11.42.19 # according to Fujitsu, the power requirements say 2.3W for an active drive and 0.1W for a sleeping drive 11.42.41 # so shutting it off completely would probably not make that much of a difference 11.43.02 # so leaving the drive active for a couple seconds won't make too much of a power drain? 11.43.33 # MeRWiN: leaving it active makes a difference 11.43.36 # That's 25mA ! 11.43.58 # 0.1W that is 11.44.01 # Linus: would the config option be a global var? 11.44.20 # i will let my recorder play until it drops and see how much longer the battery life is 11.44.32 # MeRWiN: a global_option 11.44.48 Nick notch is now known as notch|learningto (hidden-use@212.250.215.13) 11.44.58 # global_settings.spindown 11.45.02 # or something 11.45.11 # yeah 11.45.25 # but we need to work out the technical details first 11.45.29 # yeah... 11.46.46 # doesn't hurt to create the menu though :) 11.48.13 # no, i guess not 11.50.40 # the CPU takes about 60-90 mA when running 11.52.11 # There, there's a menu for it now... 11.52.58 # Linus: where is the 5 second spindown actually set? 11.55.25 # ata.c 11.55.30 # sleep_timeout 11.57.40 # what would be the "legal" way to set sleep_timeout to global_settings.spindown 11.57.42 # ? 11.57.51 # no 11.58.16 # it should be done in the same way as the scroll_timer 11.58.22 # and the backlight timer 11.58.25 # ? 11.59.33 # i thought you would look at the code when i wrote that 12.00.03 # i mean that the load_settings() calls the set_xxx_timer() functions when it loads the settings 12.03.11 # ahh 12.14.00 Quit notch|learningto (Read error: 104 (Connection reset by peer)) 12.14.23 # got the config item working... it sets the default GLOBAL spindown time :) setting it to 1 second actually seems to function properly 12.14.34 # unless you hit something like a playlist and try to change immediately 12.14.52 # I personally like 3 seconds 12.21.21 # time to get food 12.28.38 # I made some measurements regarding the power usage 12.29.04 # with ATA_SLEEP: 200mA 12.29.14 # with ATA poweroff: 75mA 12.29.20 # whabang! 12.29.41 # wow 12.29.43 # nice power change 12.29.58 # and it's about 500mA when reading from disk 12.30.10 # and about 7-800 when spinning up 12.30.50 # in some cases, leaving it spinned up is better than spinning it up every 3 seconds? 12.31.17 # and 250 when the disk is spinning and idle 12.32.28 # from this, i can see that our SLEEP doesn't work as expected 12.32.44 # nah 12.32.49 # it draws too much current when sleeping 12.33.07 # the sleep should take about 50mA 12.33.33 # and the CPU about 70 12.33.50 # hmm 12.34.52 # any clue why? 12.35.08 # how can sleep take less than poweroff? 12.35.20 # it doesn't 12.35.32 # you said that sleep is supposed to be 50mA and poweroff is 75mA 12.35.47 # i was talking about the HD itsels, sorry 12.35.52 # itself 12.35.52 # ah 12.36.03 # HD+CPU+memory+LCD....it all adds up 12.36.23 # yeah 12.36.24 # Uwe measured the Archos firmware power consumtion 12.36.45 # they use 95mA when idle 12.37.09 # yeah, definately too much for ours 12.38.11 # that must mean that they use the SLEEP function for the HD 12.38.28 # and that they put the CPU to sleep 12.39.03 # hmm... why would you put the cpu to sleep 12.39.12 # to save power of course 12.39.25 # you save 20mA 12.39.44 # not really. 12.39.49 # those numbers are for 5V 12.40.04 # aren't we 5v? 12.40.36 # 3V 12.40.58 # oh 12.41.09 # so it would be more like saving 12mA? 12.41.21 # i guess 12.41.54 # i wonder why our ata sleep takes so much power... 12.42.18 # dunno, but it's a great power drain though. Probably reduces overall life by about an hour 12.43.34 # but maybe the drive wears out faster because of all the power cycling? 12.43.52 # hmm. 12.45.27 # i'm working on a quick track skipping method right now (holding down the next track button to cycle through tracks) 12.45.47 # don't do that 12.45.57 # why? 12.46.13 # we want to use those keys for fast wind/rewind 12.46.17 # It's needed for seeking inside a file 12.46.35 # ah... 12.46.42 # well, i'll trash that code then :) 12.50.26 # in any case, I've got that HD spindown code done.... 12.51.26 # i tried using ATA_STANDBY instead, and i got less power consumption than ATA_SLEEP... 12.51.41 # weird indeed! 12.51.44 # weird 12.51.53 # how much less? 12.53.57 # 200mA with sleep 12.54.02 # 125 with standby 12.54.10 # woo 12.54.30 *** Saving seen data "./dancer.seen" 12.54.31 # we must do something wrong when using SLEEP 12.56.10 # lunch time 12.56.25 Nick Linus is now known as Linus|lunch (~linus@193.15.23.131) 13.01.11 Nick yro is now known as yro|lunch (~yves@ns1.alcove-solutions.com) 13.04.08 # how do i use patch? 13.04.17 # to redo a diff that I made 13.04.28 # err.. implement a diff that i made 13.04.35 # patch < file 13.05.19 # thanks 13.23.50 Quit MeRWiN (Read error: 110 (Connection timed out)) 13.25.06 Nick Linus|lunch is now known as Linus (~linus@193.15.23.131) 13.36.59 Part Bagder 13.37.09 Join Bagder [0] (~daniel@as3-3-2.ras.s.bonet.se) 13.37.29 Mode "#rockbox +o Bagder " by ChanServ (ChanServ@services.) 13.44.26 Nick yro|lunch is now known as yro (~yves@ns1.alcove-solutions.com) 13.57.43 Join Mighty [0] (mboss@h76n2fls35o931.telia.com) 14.05.05 # The deep discharge mode of the charger seems to work too. 14.05.15 # deep discharge? 14.05.49 # the charger patch has a toggle to change the max charge level to start charging 14.05.54 # between 10% and 90% 14.06.09 # in 'deep discharge' mode it only starts charging when the charge has gone down to 10%. 14.07.07 # aha 14.07.29 # is the battery charging code cleanly separated from the graph code? 14.10.49 # Yes, quite well 14.11.18 # can easily remove/disable the graph/debug stuff 14.11.32 # there are some global variables used instead of functions to set them 14.11.45 # which could be cleaned up if that's the preferred way 14.12.06 Quit fragglet (lerouge.openprojects.net irc.openprojects.net) 14.12.06 NSplit lerouge.openprojects.net irc.openprojects.net 14.12.42 # i have no problems with global variables, quite the opposite 14.14.47 Quit Mighty ("BitchX: its wax ecstatic") 14.16.24 NHeal lerouge.openprojects.net irc.openprojects.net 14.16.24 NJoin fragglet [0] (~fraggle@pc1-guil4-0-cust151.gfd.cable.ntl.com) 14.17.41 # so linus, any thoughts on 1.2? 14.18.30 # I've seen the approach of set_foo_bar() being exported from the firmware side, and the function actually just sets a local variable in the firmware 14.18.40 # sounds like a waste of time for most cases 14.19.15 # yes, but sometimes it is handy to begin with if we haven't quite thought out all details 14.20.02 # but for a single global, I agree that it makes little sense 14.26.12 Quit fragglet (lerouge.openprojects.net irc.openprojects.net) 14.26.29 NJoin fragglet [0] (~fraggle@pc1-guil4-0-cust151.gfd.cable.ntl.com) 14.26.44 # Bagder: i still haven't worked out the distortion issue 14.31.47 # a "Hold function" is the key lock we already have, isn't it? 14.31.57 # * Bagder reads feature-requests 14.32.39 # Yes 14.34.04 Join jedix [0] (~liam@fwott1-1.cis.ec.gc.ca) 14.36.35 # Bagder: i have already browsed all the feature requests 14.36.53 # but i decided not to close them until they are implemented in an official release 14.38.18 # I don't think that very good, as people will use the feature-request list as items to implement as long as they're open and uncommented 14.38.41 # maybe you are right... 14.39.09 # I also find it very odd that only 3 people can get a feature request assigned to them 14.39.25 # and the categories and groups stink 14.39.42 # I know, that's Björn's area 14.40.04 # it also stinks that we can't remove groups and categories 14.40.17 # yes 14.41.11 Quit fragglet (lerouge.openprojects.net irc.openprojects.net) 14.41.11 NSplit lerouge.openprojects.net irc.openprojects.net 14.41.24 NHeal lerouge.openprojects.net irc.openprojects.net 14.41.24 NJoin fragglet [0] (~fraggle@pc1-guil4-0-cust151.gfd.cable.ntl.com) 14.42.06 # gosh 14.42.12 # I could add people ;-) 14.45.09 Quit fragglet (lerouge.openprojects.net irc.openprojects.net) 14.45.09 NSplit lerouge.openprojects.net irc.openprojects.net 14.45.38 NHeal lerouge.openprojects.net irc.openprojects.net 14.45.38 NJoin fragglet [0] (~fraggle@pc1-guil4-0-cust151.gfd.cable.ntl.com) 14.54.31 *** Saving seen data "./dancer.seen" 14.57.53 # Btw... the idle poweroff timer would be nice to have 14.58.10 # I've accidentally powered it on a few times and then it has discharged in the bag.... um... pouch. 14.58.28 # Hes: care to implement it? 14.58.32 # It'd be good for charging too (can the device be powered off while connected to a supply?) 14.58.51 # you can shut off the hard drive 14.59.15 # if the device is not being used, it should be turned as off as possible when the battery is fully charged 14.59.22 # and yes, you can shut off the unit, but it will restart again, to the archos charger 14.59.35 # Doh. 14.59.42 # So we just sleep as well as we can, right? 15.00.01 # lcd_update in DRAM: 36ms 15.00.12 # lcd_update in IRAM: 20ms 15.00.24 # neat 15.00.35 # i was thinking about memset() 15.00.39 # amd memcpy() 15.00.44 # ah, good idea 15.00.48 # more candidates? 15.00.53 # Very neat. It feels and looks much faster now. 15.01.19 # Screen drawing routines? 15.01.24 # yeah 15.01.51 # yeay, lcd_bitmap() is a candidate 15.02.49 # Argh, i'm going to the machine room to fix a switch. 15.03.02 # The bandwidth limiter for asm02 just melt down. 15.13.29 # so maybe we can get the charger code comitted too before 1.2 is released 15.13.39 # yeah 15.13.58 # I'd like to test it though 15.14.09 # yeah, me too 15.14.10 # but i want his lates patch 15.14.38 # the rockbox really flies with the IRAM patch 15.14.41 # hoe large is the internal ram? 15.14.45 # but it feels so unproductive having to mail around patches instead of simply comitting and sit on the bleeding edge instead 15.14.46 # 4Kbytes 15.14.53 Nick elinenbe|snooze is now known as elinenbe|wake (trilluser@pcp02254422pcs.wanarb01.mi.comcast.net) 15.15.14 # * Bagder wants to fly too 15.15.22 # Bagder: you are right, but killing batteries is nothing to be taken lightly 15.15.33 # I guess not 15.15.52 # Badger: agreed. too many patches on the email list -- they should be in the CVS 15.15.56 # i would like to enable the disk saving of settings too 15.16.27 # Zagor is away, let's dance on the table and merge those suckers 15.16.34 # :-) 15.16.39 # hehe 15.17.07 # We should merge the charger patch first, because the disk save depends on the battery status filter 15.17.33 # has anyone tried the "ipod UI" patch that was posted to the list? 15.17.40 # what? 15.18.01 # "[PATCH] progressbar and slidebar" ? 15.18.24 # yeah, that is the one. 15.18.31 # I'm about to apply 15.18.34 # I am checking that out right now. 15.18.35 # This is a patch from me. Hope the code is not too bad :) 15.18.50 # looks fine 15.19.16 # BTW. Is someone working on the remote? 15.19.23 # no 15.19.31 # you go ahead ;-) 15.19.34 # Yes, i can't remember who it is, though 15.19.39 # oh 15.19.49 # check the irc logs 15.19.57 # OK .... 15.20.06 # nothc? 15.20.09 # notch? 15.20.21 # anyone, how do you apply a diff? 15.20.30 Nick elinenbe|wake is now known as elinenbe (trilluser@pcp02254422pcs.wanarb01.mi.comcast.net) 15.20.40 # patch < file 15.20.48 # or sometimes patch -p0 < file 15.20.59 # like in mbr's patch 15.23.54 # mbr_: you happen to have a screen dump of your progress bar running? 15.24.14 # No, sadly not. 15.24.19 # ok 15.26.00 # I make on in simulator. One moment please ... 15.29.08 # Badger: http://www.stz-softwaretechnik.de/~mb/slide.png and http://www.stz-softwaretechnik.de/~mb/progress.png 15.29.17 # This is my test screen 15.29.19 # I'm pretty sure the charger can't kill batteries. It might not charge them to the absolute max, which could reduce their capacity, but just a little. 15.29.56 # they look great! 15.29.56 # mbr_: looks cool! 15.30.17 # I'll commit 15.30.40 # cool, my first code in rockbox :) 15.31.58 # congrats! 15.32.03 # and thanks 15.32.33 # np, thats what oen source is for 15.32.39 # open source 15.32.45 # I think it looks great too. 15.33.00 # now we just need a slider like that for the volume,bass,etc... 15.33.02 # its now in CVS 15.34.00 # Bagder: don't forget credits.c 15.34.05 # ah 15.34.17 # we should automate 15.34.22 # maybe a script? 15.35.54 # yes, "one day" ;-) 15.36.00 # I think that widgets like mbr_'s are wonderful. Our entire UI should be full of widgets. Sliders, tabs, etc... 15.36.56 # yes, it makes it more good-looking 15.37.07 # and look *is* important 15.38.15 # I couldn't agree more. 15.38.19 Join mistaRx [0] (mistaX@t1o975p93.telia.com) 15.39.29 # hello?! 15.39.52 # hey ho 15.40.37 # it was u who gave me a "#define Save_To_disk" mo, right?! 15.40.38 # yo 15.40.44 # i did 15.40.50 # i think 15.41.10 # does it matter who? 15.41.31 # ok, it doesn't work, can't u do a new one with the newest build, pleez..?! 15.41.37 # hang on... 15.41.57 # old LCD, right? 15.42.08 # right 15.42.54 Quit yro ("ircII EPIC4-1.1.5 -- Are we there yet?") 15.43.24 # http://linus.haxx.se/archos.mod 15.43.38 # loading... 15.43.53 # woo, linus.haxx.se! ;-) 15.44.15 # "Hejsan alla barn" 15.44.20 # * Bagder laughs 15.45.05 # thanks 15.49.55 # WEHEEJ!! it's working 15.51.35 # do u know if it afects the battery life?! 15.52.26 # only very, very slightly 15.52.49 # since it only writes to disk when you change anything via the settings menu 15.53.01 # pictures of latest firmware in action (with slider) http://www-personal.umich.edu/~elinenbe/archos/temp/2.jpg 15.53.04 # http://www-personal.umich.edu/~elinenbe/archos/temp/3.jpg 15.53.05 # ok, was just going to ask that.. 15.53.24 # http://www-personal.umich.edu/~elinenbe/archos/temp/1.jpg 15.53.44 # the pictures were taken with a $5 digital camera so beware! 15.55.20 # hehe, yeah the quality of the pics ain't top notch but I get the point ;-) 15.55.54 # well gotta go, bye bye 15.56.00 # bye 15.56.05 Quit mistaRx () 15.56.59 # i'm running the slider patch now. looks great! 15.59.12 # what used to be on that line? 15.59.23 # nothing 15.59.26 # nothing, i think 15.59.30 # just the battery line below it 15.59.36 # There was nothing before 16.00.13 # mbr_: since you are at it, would you like to do a status bar? 16.00.26 # Status bar? 16.00.29 # containing battery status, play status, volume and so on 16.00.36 # with battery and so on? 16.00.49 # that one would be dislayed in almost every screen 16.01.00 # just do the status_draw() function 16.01.08 # see upcoming mail from me 16.01.09 # status.c 16.01.13 # apps/status.c 16.01.22 # Can do it, but i am not a gui design guru 16.01.32 # now you are ;-) 16.01.33 # ok 16.01.55 # I'll look into it this evening 16.02.13 # no pressure 16.02.31 # OK. 16.03.13 # gotta go. cu guys! 16.03.24 Part Linus 16.03.41 # I have to go too, bye! 16.03.46 # see ya 16.06.56 Join sam___ [0] (nio@80.9.49.206) 16.07.15 # Hi 16.07.21 # hey 16.11.46 # Got a question , read yahoo groups mailing archive but only find few answer, i'm going to by a pda and want to know if there is a way to use my archos jukebox as mass storage ? 16.12.55 # I prefer palmos but i was thinking that if somebody port an usb driver will be more easy on windows ce 16.13.09 # if the PDA can act as a USB master, then yes 16.14.30 # hum , ok found this on msdn http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceddk40/htm/cxconSampleUSBMassStorageClassDriver.asp so seems to be possible 16.15.36 # yes, it indicates that windows CE can run as a USB master 16.15.45 # it doesn't necessarily mean that all PDAs running it can 16.16.17 Nick dwihno|gone is now known as dwihn0r (dwihno@193.180.246.67) 16.16.22 # Has anyone seen edx lately? 16.16.36 # he popped in quickly the other day and vanished again 16.16.54 # has he gone for a trip or something? 16.17.24 # I don't know 16.18.50 Quit sam___ () 16.23.33 # :-) 16.23.39 # * dwihn0r hands Bagder some coffee 16.23.57 # I need to get the win32.mak files so I can compile rockbox on my new development (kickass) box :) 16.24.16 # I see you merged the patch with the progress bar. Is it neato? 16.24.33 # it is n-e-a-t-o ;-) 16.24.42 # :-D 16.24.55 # * dwihn0r went to Ö.B and bought cheap noodles 16.25.01 # and cheap godis 16.27.47 # Excellent, now we have a GUi design guru 8-) 16.28.04 # heheh, exactly 16.32.23 # anyone with a build I can test? I'd love to see :) 16.32.56 # hang on 16.33.30 # yay :) 16.33.31 # http://storebror.haxx.se/archos/ 16.34.13 # it is also much faster now 16.34.49 # it is? 16.34.57 # yes 16.34.58 # many tweaks? 16.35.16 # lots of important functions now run in the faster internal ram 16.37.01 # cool 16.37.06 # I read something in the CVS logs 16.37.14 # The sound settings has gone through a major improvement as well 16.38.19 # gotta run, see ya 16.38.20 Part Bagder 16.54.35 *** Saving seen data "./dancer.seen" 17.00.22 Join elinenbe- [0] (~elinenbe@vanguard.gpcc.itd.umich.edu) 17.00.27 # hi 17.00.53 # i am on my palmphone 17.01.07 # bye 17.01.09 Quit elinenbe- (Client Quit) 17.03.39 Join notch|learningto [0] (hidden-use@arthur.techprt.co.uk) 17.04.11 # just built a serial remote for the player... 17.04.39 # works fine on a recoreder, but does not work at all on the player... 17.04.42 # any ideas? 17.13.15 Join elinenbe_ [0] (~elinenbe@asteroids.gpcc.itd.umich.edu) 17.13.15 Quit ripnetuk (Read error: 104 (Connection reset by peer)) 17.13.31 # Hello there again. 17.17.28 # exit 17.17.32 Quit elinenbe_ (Client Quit) 17.17.47 Quit ironi_ (Read error: 110 (Connection timed out)) 17.18.01 Quit notch|learningto () 17.40.12 Join ironi__ [0] (~ironi@80.88.116.93) 17.43.41 Join Tumm [0] (coyote@mysko.net) 18.40.29 # ironi: I got my new box now ;D Yay! 18.54.39 *** Saving seen data "./dancer.seen" 19.04.45 Join ripnetuk [0] (~george@62.137.133.101) 19.24.02 Quit ripnetuk () 19.24.05 Join ripnetuk [0] (~george@ripnet.fsnet.co.uk) 19.24.08 Quit ripnetuk (Client Quit) 19.33.51 Join ripnetuk [0] (~george@ripnet.fsnet.co.uk) 19.58.06 Join champi [0] (~champi@AVelizy-108-1-3-138.abo.wanadoo.fr) 20.01.13 Quit champi (Client Quit) 20.05.18 Join mistaRx [0] (mistaX@195.198.190.205) 20.14.39 Quit mistaRx () 20.54.41 *** Saving seen data "./dancer.seen" 21.23.47 Join WetFlax [0] (~wettoad@flax.mbi-berlin.de) 21.46.46 Join mistaRx [0] (mistaX@t2o975p85.telia.com) 21.56.30 Part mbr_ 21.58.21 Join mbr [0] (~tiw4mabr@rhlx01.fht-esslingen.de) 22.19.34 Quit datazone (Read error: 110 (Connection timed out)) 22.31.00 Quit mistaRx () 22.42.34 Quit adi|home (Read error: 110 (Connection timed out)) 22.54.42 *** Saving seen data "./dancer.seen" 23.09.25 Join adiamas [0] (~adiamas@as5300-9.216-194-23-139.nyc.ny.metconnect.net) 23.11.36 Nick adiamas is now known as adi|home (~adiamas@as5300-9.216-194-23-139.nyc.ny.metconnect.net) 23.11.36 Quit adi|home (Remote closed the connection) 23.11.44 Join adiamas [0] (~adiamas@as5300-9.216-194-23-139.nyc.ny.metconnect.net) 23.12.21 Nick adiamas is now known as adi|home (~adiamas@as5300-9.216-194-23-139.nyc.ny.metconnect.net) 23.13.28 Nick adi|home is now known as adi (~adiamas@as5300-9.216-194-23-139.nyc.ny.metconnect.net) 23.13.28 # hmmm oddd 23.13.28 # can't seem to change my nick 23.13.28 Nick adi is now known as adi|home (~adiamas@as5300-9.216-194-23-139.nyc.ny.metconnect.net) 23.58.43 Quit jedix (Remote closed the connection)