--- Log for 05.02.105 Server: zelazny.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 1 day and 15 hours ago 00.00.41 Quit Remo ("ChatZilla 0.9.61 [Mozilla rv:1.7.3/20040910]") 00.07.35 Quit Nibbler (Read error: 110 (Connection timed out)) 00.08.42 # Bagder: you should change your nick for simplicity 00.10.05 # :-) 00.10.16 # I've used this nick for almost 20 years now 00.10.24 # Cassandra_: My comments on your patch: (1) I have to agree with Bagder, this mixes firmware and app level (started_from_rtc variable) 00.10.31 # so you agree it's time for change? :P 00.10.57 # (2) The alarm flag is read only, you can't reset it by writing the data back with the flag reset. 00.12.51 # The first I fixed by making rtc_init return the value. 00.13.04 # I'll take out the redundant code in that case. 00.13.05 # -rw-r--r-- 1 daniel daniel 104064 Feb 5 00:12 libmad.a 00.13.09 # woot 00.13.12 # built with m68k 00.13.15 # would you care to share the procedure? 00.13.36 # hang on 00.13.55 # (I haven't linked with it yet) 00.14.07 # nono, but just building a lib is more than i managed, hehe 00.14.47 # http://daniel.haxx.se/mad-rockbox.txt 00.15.34 # Right, suppose I'd better test this again, just to make sure it still works. 00.16.05 # Cassandra_: If you return the value from rtc_init(), how do you store it? It is needed later, and in another place than the rtc_init() call takes place. 00.16.25 # In a global bool. 00.16.31 # I checked the datasheet, the alarm flag resets itself as soon as the flags register is read. 00.16.45 # That's good. 00.17.11 # but yes, now for supporting the emac stuff, which will be more than enough fun, since gcc almost certainly doesn't know about the four accumulator registers 00.17.34 # no it doesn't 00.17.51 # I think a separate function for checking the flag would be more straightforward than a global bool. Plus, since the flag resets itself after being read once, there's no need to reset a separate variable. 00.18.30 Join Nibbler [0] (~sven@port-212-202-78-188.dynamic.qsc.de) 00.18.40 # Cassandra_: Btw, your work is the first step towards a recording timer... 00.19.08 # True - cool 00.20.29 # Actually I think that's fairly trivially implementable in combination with the "start in recording screen" option. 00.21.10 # :) 00.21.35 # The function to check for powerup from alarm can be written as a one-liner: 00.21.50 # bool started_from_alarm(void) 00.21.50 # { 00.21.50 # return (rtc_read(0x0f) & 0x40) != 0; 00.21.50 DBUG Enqueued KICK amiconn 00.21.50 # } 00.22.44 # You're allowed to call rtc_ functions from the app, right. 00.22.51 # Well, of course you are, doh. 00.22.59 # yup. 00.23.10 # OK. Means you don't need the global var either. 00.23.32 # Excuse me while I go implement starting recording from RTC alarm. 00.24.11 # preglow: I tried 'make install' too after that command and it runs fine, making it easier to build rockbox with it later 00.24.29 # indeed 00.28.17 # Cassandra_: "Start in recording screen" + "wakeup alarm" => timer recording 00.28.25 # ? 00.30.17 # Exactly 00.30.38 # Just need to add a little patch to the recording screen code. 00.34.43 # Bagder: What means: "make[2]: *** No rule to make target `<<<<<<<', needed by `/home/Administrator/rb-patched/build/fmrecorder/dep-plugins'. Stop." ? 00.35.11 # This happens when I "make clean" 00.35.21 # haha 00.35.26 # remove the dep-plugins file 00.35.43 # Damn - I need the state twice. Better to use a static in rtc_check_alarm_started to remember state, or use a global to hold it once it's been read? 00.36.10 # Why do you need it twice? 00.36.27 # Once to make sure I don't resume, once to start recording. 00.36.44 # ??? 00.37.09 # Sorry, 00.37.37 # Once to make sure I don't ask the user whether to resume , once to start recording without user intervention. 00.37.42 # I thought your start-in-recording-screen first checks whether recording screen should be started or normal browser+resume check 00.38.23 # Yes, but you only need either one or the other check per each boot, never both 00.38.25 # Nope, resume can override start in recording screen. 00.38.33 # That seemed like the right way round to do it. 00.39.17 # Really? That way, the "start in recording screen" wouldn't do anything good for me in >90% of all cases. 00.39.40 # You have resume = yes? 00.40.07 # No, I have resume = ask, but I practically always have a stored resume position. 00.40.36 # If you say "no" to resume, it drops into the recording screen. 00.41.37 # Ah ok. Still, for timer recording, this wouldn't do anything useful, because with you resume-from-alarm patch it would always resume playback without asking you 00.41.52 # I thought it best not to have "start in recording screen" disable resume functionality. 00.42.43 # It would have to if started from alarm and "start in recording screen" is on. 00.43.33 # Well yes, resume functionality is overriden when starting from alarm. 00.43.48 # Yes, that's exactly what I mean. 00.43.53 # But in order to do that, you have to check to see whether you're starting from alarm. 00.44.22 # So you need two checks - once to avoid the resume code, and once to start recording. 00.44.23 # You can still do it the other way round. 00.45.05 # On boot, first check whether "start in recording screen" is enabled 00.45.06 # I don't see how that would help. 00.45.49 # Oh, I see, yes. Good plan. 00.45.54 # If yes, then check for startup-from alarm, and if again yes, start the recording screen with a parameter that tells it to start recording immediately 00.46.45 # If the latter says no, then continue with normal resume, and if no resume, then call recording screen 00.47.14 # Ah, that'd involve calling the recording screen from two different points in the code. 00.47.33 # I could just be being dense, but I think it'd screw up the execution flow. 00.48.46 # If you do it the other way, i.e. first call the resume check, the resume check would need to take the start-in-recording-screen setting into account, which is also not very logical 00.49.47 *** Saving seen data "./dancer.seen" 00.49.56 # Sorry, I really am lost now. I don't think so, but I'm too confused to work it out. Sorry. 00.50.25 # The program flow around startup is pretty nightmarish. 00.51.03 # That's because the resume check would need to differentiate 4 conditions 00.51.25 # (1) Not started from alarm, and not start-in-rec-screen: Normal resume request. 00.51.33 # At the moment, the only logic I need in the resume check is whether or not it's started from rtc. 00.51.53 # Oh, hold on. I think I'm getting ther. 00.52.01 # (2) Started from alarm, not start-in-rec-screen: Resume unconditionally. 00.52.36 # (3) Not started from alarm, start-in-rec-screen: Normal resume request, if not resumed, drop to recording screen 00.52.39 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 00.52.39 # * Cassandra_ nods. 00.53.01 # (4) Start from alarm, start-in-rec-screen: Start recording screen & recording immediately. 00.53.19 # So you'd suggest changing the logic so that "start in record" overrides resume? 00.53.19 # if i can give my opinion, i'm with amiconn 00.53.36 # Yeah, he's right. I was just being dense. 00.53.37 # You see, you'll always have two places from where to call the recording screen 00.54.11 # ANd you'll always have to check started-from alarm only once. 00.54.40 # (using a 4-way if-else construct for the 4 possibilities mentioned above) 00.55.08 # There are different ways to implement this though 00.55.22 # Yeah. I think I'll leave it for tonight. 00.55.35 # I need to think more about it. 00.56.36 # And: I have to agree, the startup is nightmarish. 00.56.57 # i suppose you have to check first of all a *start from alarm* and later on *start in rec screen* 00.57.15 # just my opinion 00.57.16 # :) 00.57.22 # The order of these checks doesn't matter 00.57.52 # of course 00.58.03 # but i like it that way :D 00.58.05 # If you do it the other way round, you'll have 2 places where the check function is called, but only one would get executed per boot 00.59.18 # which jukeboxes have a built in micro again? 00.59.44 # cYmen: All recorders have that 01.00.09 # (Recorder v1, v2, FM recorder, and Ondio FM) 01.00.21 # \o/ 01.00.54 # i only used it to listen to music and as portable disk but rockbox has a nice dictation function hasnt it? 01.01.24 # dictation function? 01.02.03 # so i can use it as dictating machine 01.02.53 # Right - bed. 01.02.55 # Night all 01.03.03 # night 01.03.04 # i think i don't understand that in english... you mean recording your voice for a later use? or what? 01.03.06 # night. 01.03.07 # :/ 01.03.09 Part jyp ("poof!") 01.03.09 Quit Cassandra_ ("Client Exiting") 01.03.12 # Quel|away: yes 01.03.18 # oh 01.03.20 # then, it has 01.03.21 # :) 01.03.38 # Quel|away: what is your mother tongue? 01.04.00 # spanish 01.04.12 # ah 01.04.41 # voy aprendo espanol 01.04.55 # more or less :) 01.04.55 # soy el diablo 01.05.05 # bed for me too 01.05.06 # nite 01.05.11 # nite preglow 01.05.16 Quit preglow ("arf") 01.05.28 # prefiero espanol, pero no sabe mucho :-P 01.05.46 # i'm going to propose spanish as second language for rockbox. Everyone here seems to know some spanish :) 01.06.07 # muy bien! 01.06.54 # * rasher hides under a rock 01.09.15 # why? 01.09.39 # por que el no habla el espanol? 01.10.00 # * lolo-laptop causes trouble 01.10.15 # * rasher explodes 01.10.21 # :) 01.11.50 Join bagawk [0] (~Lee@bagawk.user) 01.14.58 Quit bagawk (Client Quit) 01.21.53 # lolo-laptop: prefiera el espanol a que? (correct me when i make mistakes!) 01.23.47 # a ingles, por que ingles es muy loco. Yo no se bastante espanol a hace coreciones... (not sure on some of that) 01.26.50 # well... let s stick to english ;P 01.27.17 # good idea 01.34.19 Quit lolo-laptop ("Client exiting") 01.35.05 # hmm 01.35.14 # i think i have to correct both of you 01.35.33 # ;) 01.35.43 # go ahead :) 01.35.53 # you just made a small mistake 01.36.23 # its "Prefiere" or "Prefieres", first one is Polite and the second one is coloquial 01.37.03 # and the answer... well..i don't know what did he want to say :) sounded more or less ok, but... not spanish ;) 01.37.33 # well i know what he wanted to say :) 01.38.10 # did he wanted to say that english is too crazy? 01.38.49 # yes and that he doesn t know spanish well enough to correct me :) 01.39.23 # then that was ok 01.39.42 # the second part is "No se bastante español para hacer correcciones" 01.39.44 # :) 01.39.49 # but was ok 01.40.00 # everyone could understand him 01.40.10 # (as you do when i speak english) 01.40.25 # english is pretty simple and pretty variable 01.40.33 # whatever you say seems to be right in some way :) 01.40.37 # :) 01.50.03 Join sdbarker [0] (~sdbarker@pcp02689678pcs.roylok01.mi.comcast.net) 01.50.37 # Hey. 01.51.53 # hi 01.52.23 # I just got my new xs200 as an upgrade from recorder15. 01.52.23 # Yay! 01.57.40 # Alright, so, anyway, who do I talk to about getting on the dev team to work on porting rockbox to this thing? 02.00.19 # first you talk to the docs then to some tutorials and when you ve become part of the dev team - to yourself :) 02.00.42 # I should have worded that differently... 02.00.58 # I read in one of the email list threads, which I can't find now, that somebody had already started on it. 02.01.06 # yeah it sounded a bit demanding ;) 02.01.10 # Instead of duplicate efforts, I'd rather contribute. 02.01.34 # So, does anybody know off hand who that is? 02.01.45 # hmmm 02.01.51 # dunno 02.07.40 # anyone got the iriver display width/height handy? 02.07.53 # Nope. 02.08.56 # hi dwihno! 02.09.06 # nice to see you awake 02.09.07 # :) 02.09.14 # bueno quel 02.09.34 # mur da bra? 02.10.17 # dwihno: 160x128 02.11.27 Join lostlogic [0] (~lostlogic@node-4024215a.mdw.onnet.us.uu.net) 02.11.30 # rasher: thanks 02.11.52 # I'll prep some stuff for the target. 02.14.30 # If nothing else, I'll sit and answer questions by learning where stuff hides in the wiki :) 02.14.48 # I guess that'll be my contribution for now 02.15.06 Part sdbarker 02.15.57 Join edx_ [0] (edx@p54879843.dip.t-dialin.net) 02.16.33 # ^ 02.16.35 # ^^ 02.21.12 # * lostlogic cvs co's rockbox, time to see what people are talking about. 02.23.25 # hehe 02.26.20 Quit edx (Read error: 110 (Connection timed out)) 02.27.09 Nick edx_ is now known as edx (edx@p54879843.dip.t-dialin.net) 02.27.47 Join Patr3ck [0] (~patr3ck@pD95F736F.dip.t-dialin.net) 02.28.29 Part amiconn 02.40.04 # bah, just took me 3 tries to get my change in the wiki adding more info about the Vorbis codec right. why is it vorbis.com and not org? 02.43.12 # why is it oggenc and not vorbisenc and vorbiscomment and not oggcomment 02.43.48 # ze: to give you something to ask questions about. 02.43.57 # them vorbis folk seem to make some odd choices 02.43.58 # heh 02.44.20 # ze: hehe, it makes little sense to me, because supposedly ogg is a container (has comments and streams) and vorbis is a stream (needs encoding) 02.44.21 # blah. 02.44.33 # vorbis is the actual audio codec 02.44.39 # right 02.44.49 # ogg can contain any kind of media, whatever audio or video codec 02.44.56 # sorta like avi can 02.44.56 Join ashridah [0] (ashridah@220-253-119-126.VIC.netspace.net.au) 02.44.59 # but better 02.44.59 # heh 02.45.05 # or so they say 02.45.06 # :) 02.45.33 # there's divx rips out there in ogg 02.45.42 # ooh, I'd like to see that :) 02.45.55 # although a bunch of misguided people have been naming video oggs .ogm 02.46.15 # to distinguish them from audio .ogg's 02.46.22 # *rolleyes* 02.46.24 # which does make some sense but *shrug* 02.46.29 # ze: .ogm is a container formate similar to .avi last i heard 02.46.35 # .ogg is an audio codec 02.46.39 # no 02.46.40 # ashridah: no. 02.46.41 # you are wrong 02.46.42 # vorbis is the audio codec 02.46.45 # you missed the discussion above 02.46.57 # * ashridah colours himself corrected 02.47.00 # heh 02.47.02 # :-D 02.47.26 # but yeah are the comments held by the ogg file? i would imagine 02.47.36 # or are they part of the codec (would be strange) 02.47.36 # heh 02.47.39 # that's why the codec as listed on the rockbox wiki is 'OGG/Vorbis' to indicate ogg files containing vorbis streams... kinda like GNU/Linux or something of the sort but different 02.47.46 # heh 02.47.52 # ze: hmm, lemme take a look 02.48.22 # cause ya know if the ogg container held the comments, then 'oggenc' and 'vorbiscomment' are really exactly backwards 02.48.25 # heh 02.48.53 # which, i dunno, maybe there's something intentional to that 02.49.48 *** Saving seen data "./dancer.seen" 02.50.19 # afaics, the ogg container holds a comment section and then a vorbis stream section (which is prefixed amazingly by the ascii characters v o r b i s :-D 02.50.29 # heh 02.50.46 # so maybe the whole vorbis.com thing is a part of a greater backwards theme 02.51.08 # bye! 02.51.09 # xiph.org is the parent 'company' and vorbis.com is the opensource portion? 02.51.11 # later 02.51.12 # interestingly, vorbis.org seems to actually be registered by the same owners of vorbis.com and has the same name servers listed 02.51.15 Quit Quel|away ("KVIrc 3.0.1.99 'Realia'") 02.51.35 # and yet vorbis.org has nome A record 02.51.39 # s/nome/no/ 02.51.39 # heh 02.51.49 # dunno where that me came from 02.51.49 # heh 02.51.49 # yeah, which is why I had to change it when I initially had it wrong on the wiki 02.51.52 # probably to protect against domain squatters 02.51.58 # nod 02.52.05 # yeah but why not use vorbis.org at all? 02.52.13 # i mean not even point it to the same place as vorbis.com 02.52.26 # ya know google's got google.org and google.com and they both go the same place 02.52.31 # and theres several others like that 02.52.39 # good question. maybe to distance themselves from the idea that they're an organisation, not a company? 02.52.55 # but xiph.org 02.52.55 # heh 02.53.00 # yeah 02.54.05 # i think maybe lostlogic is right about .org parent company and .com opensource 02.54.19 # I just think they're nuts. 02.54.20 # and that going along with some sorta backwards theme 02.54.21 # heh 02.55.30 # speaking of xiph 02.55.57 # whatever happened to the cdparanoia that could extract audio from those horribly mutilated CD's that they had a gallery of 02.56.46 # ze: was this a special version of cdparanoia? because I've had no problems with my pretty ugly CDs with cdparanoia as it is 02.57.13 Quit mecraw () 02.58.05 # well i'm more disappointed with that impressive gallery being no more 02.58.08 # at least as far as i can find 02.58.38 # it seemed like the more recent versions had more trouble with some of my cd's than the older one that accompanied those pics did, but that could be entirely unfounded 02.59.03 # all the docs seem to imply that the newer is better 03.05.52 # * lostlogic is loving the tech docs for rockbox 03.07.04 Join piratePenguin [0] (~piratepen@dialup1020.ts005.bmt.esat.net) 03.12.12 # hmm... now I hafta figure out how to build a couple cross-compilers on Gentoo 03.17.15 # grr, the style documentation says "no tab characters" but the source is full of the gawdamn things 03.22.34 # tr? 03.22.35 # heh 03.22.43 # tr? 03.22.53 # tr '\t' ' ' 03.22.54 # heh 03.23.12 # *shrug* 03.23.36 # chuckle - in vim - :set tabstop=4 OR :%s/\t/ /g 03.23.48 # heh 03.23.59 # i was gonna suggest that 2nd one too 03.24.08 # but i didn't really think you'd be complaining about tabs if you were using vim 03.24.12 # heh 03.24.14 # hehe 03.24.35 # I default tabstop to 100 so that vim autoindents with spaces... because I'm too dumb to figure out the right way to do that 03.24.48 # heh 03.25.02 # i never do anything with tabstop at all 03.25.07 # i just let tabs do what they do by default 03.25.08 # heh 03.31.31 Quit Patr3ck ("User pushed the X - because it's Xtra, baby") 03.43.31 Quit Stryke` ("Friends don't let friends listen to Anti-Flag") 03.44.07 # ack, bloody brackets on their own lines coding style :-P 03.55.43 Part piratePenguin 04.01.30 # * ashridah huggles inflated linecounts ;) 04.01.59 # I use a pretty little sed line to strip such bs when I do LOC counts 04.06.18 # I lied, it isn't pretty at all. 04.08.35 # lostlogic@lost ~/rockbox $ ./loc_counter.sh 04.08.35 # 64341 04.10.03 Quit QT (Read error: 60 (Operation timed out)) 04.11.21 # hmm... that would leave in multiline cstyle comments that start on a line with real code, but continue on non-code lines... I'll have to fix that at some point. 04.26.06 # or you could use sloccount :) 04.28.22 # hmm... I suppose 04.28.33 # sed and grep are fun though 04.28.37 # and it's good to practice REs 04.33.58 # I think sloccount overcounts 04.34.04 # by about 5k on rockbox 04.34.24 # hmm... maybe it's just counting files I was ignoring like makefiles 04.34.26 # shrug 04.34.27 # fun times 04.34.29 # SPAM 04.36.46 # SLEEP 04.36.54 # * rasher wanders off 04.44.32 # sweet, there is a gentoo cross compiling howto, m68k-elf here I go. 04.49.49 *** Saving seen data "./dancer.seen" 05.05.56 Quit cYmen ("leaving") 06.48.13 Join piratePenguin [0] (~piratepen@dialup363.ts527.cwt.esat.net) 06.49.50 *** Saving seen data "./dancer.seen" 07.06.19 Quit MooMaunder (Read error: 110 (Connection timed out)) 07.13.33 Part piratePenguin 07.14.52 Join midk [0] (~midk@c-67-161-124-8.client.comcast.net) 07.18.10 Join Trevmar [0] (~trevor@ca-agoura-cuda2h-53.ventca.adelphia.net) 07.18.19 Quit XShocK (" HydraIRC -> http://www.hydrairc.com <- Go on, try it!") 08.29.51 Quit midk (Read error: 60 (Operation timed out)) 08.47.17 Quit Trevmar (Read error: 110 (Connection timed out)) 08.49.53 *** Saving seen data "./dancer.seen" 09.00.16 Join SoulEata [0] (~937c5499@labb.contactor.se) 09.00.27 # wow this is amazing. 09.00.48 # for some reason my college firewall lets me connect to dalnet but here I am on another IRC network. this is exciting. 09.00.55 # only dalnet* 09.03.54 Join methangas [0] (methangas@0x50a43276.virnxx10.adsl-dhcp.tele.dk) 09.36.35 Join amiconn [0] (~jens@pD95D1342.dip.t-dialin.net) 09.52.02 Nick hile__ is now known as hile (hile@hack.fi) 09.53.15 Join QT [0] (as@dsl-082-082-233-246.arcor-ip.net) 10.49.56 *** No seen item changed, no save performed. 12.00.27 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 12.18.49 Quit edx (Read error: 110 (Connection timed out)) 12.49.57 *** Saving seen data "./dancer.seen" 12.56.03 Join jyp [0] (~jp@40-127.240.81.adsl.skynet.be) 14.10.01 Quit amiconn (" updating client...") 14.12.22 Join Quelsaruk [0] (~kvirc@80.103.128.128) 14.12.29 # hi 14.14.07 Join amiconn [0] (~jens@pD95D1342.dip.t-dialin.net) 14.24.31 Quit Nibbler (Read error: 60 (Operation timed out)) 14.29.54 Join Nibbler [0] (~sven@port-212-202-78-188.dynamic.qsc.de) 14.43.00 Join preglow [0] (thomj@s183a.studby.ntnu.no) 14.49.59 *** Saving seen data "./dancer.seen" 15.11.11 Quit methangas (" HydraIRC -> http://www.hydrairc.com <- The future of IRC") 15.22.54 Part amiconn 15.34.07 Join cYmen_ [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 15.35.21 Quit cYmen (Read error: 104 (Connection reset by peer)) 15.56.07 # has audiomulch-ross been around lately? 15.56.12 # wrong channel 16.04.02 Join lImbus [0] (lImbus@5-174.243.81.adsl.skynet.be) 16.04.11 # uh. hi all 16.06.57 # hi 16.07.15 # buenos dias :) 16.08.10 # :) 16.08.15 # buenas tardes 16.08.19 # at least here 16.08.45 # oh well. tardes must mean something like "late" 16.09.28 # and afternoon 16.09.51 # i see 16.10.01 # tarde is late, but also is how we say to evening and afternoon. 16.10.30 # thats different from french 16.13.11 # i think so 16.13.14 # are you french? 16.13.31 Quit Nibbler (Remote closed the connection) 16.13.57 # I am belgian, so implicit french speaking, working in germany, so implicit german speaking, english speaking by business 16.14.31 Join DMJC-L [0] (~DMJC-L@220-245-162-47-sa-nt.tpgi.com.au) 16.14.39 # hmm 16.14.59 # Maye you could help with French language file... 16.15.10 # our french expert is missing :( 16.15.37 # I can try 16.15.46 # (dcc does not work for me) 16.16.03 # you can submit to sourceforge :) 16.16.21 # kk 16.17.56 # what do you expect for me to do now ? 16.18.19 # do you have a special problem, or should I just go and check for todo in the file ? 16.20.00 Join Nibbler [0] (~sven@port-212-202-78-188.dynamic.qsc.de) 16.21.11 Quit Nibbler (Client Quit) 16.23.04 Join Nibbler [0] (~sven@port-212-202-78-188.dynamic.qsc.de) 16.23.09 Quit Nibbler (Read error: 104 (Connection reset by peer)) 16.23.46 Join Nibbler [0] (~sven@port-212-202-78-188.dynamic.qsc.de) 16.24.42 Join R3nTiL [0] (~zorroz@217.30.249.33) 16.24.58 # Quelsaruk, are you there ? I see a lot of diff between english.lang and francais.lang, but I'm not sure with all of those 16.25.08 # furthermore, I can't submit to cvs 16.25.11 # hmmm 16.25.21 # so I need you to commit 16.25.55 # i can submit, don't worry 16.26.06 # 1. Question: in english.lang there are a few string around line 430 marked deprecated 16.28.13 # yups 16.31.22 Quit ashridah ("sleep") 16.33.06 Quit Nibbler ("blubber") 16.33.41 Join Nibbler [0] (~sven@port-212-202-78-188.dynamic.qsc.de) 16.45.16 Quit R3nTiL () 16.50.02 *** Saving seen data "./dancer.seen" 17.07.20 Quit lImbus (" client restart") 17.07.27 Join lImbus [0] (lImbus@5-174.243.81.adsl.skynet.be) 17.12.23 Join XShocK [0] (~XShocK@pcp09492659pcs.nrockv01.md.comcast.net) 17.14.13 Quit XShocK (Client Quit) 17.17.11 Join Cassandra [0] (~christi@213.78.163.94) 17.17.51 Join XShocK [0] (~XShocK@pcp09492659pcs.nrockv01.md.comcast.net) 17.27.18 Nick gromit` is now known as maison`de`retrai (~gromit`@ras75-5-82-234-244-69.fbx.proxad.net) 17.27.25 Nick maison`de`retrai is now known as maison2retraite (~gromit`@ras75-5-82-234-244-69.fbx.proxad.net) 17.28.39 Nick maison2retraite is now known as gromit` (~gromit`@ras75-5-82-234-244-69.fbx.proxad.net) 17.39.36 Quit XShocK (Read error: 104 (Connection reset by peer)) 17.41.24 # When compiling locally, compilation stops on 'lang.h: No such file or directory' 17.41.45 # I guess this is a misconfiguration 17.41.55 # can anyone tell me how to fix this ? 17.44.33 Quit DMJC-L (Read error: 110 (Connection timed out)) 17.44.37 # hmmm 17.44.51 # the fast way is to use Genlang 17.45.03 # that script will create a lang.c and lang.h 17.45.15 # but when compiling that is done automatically 17.47.25 # I guess I did something stupid when hacking the Makefiles in my early days ;) 17.47.45 # I'll give it a fresh start 17.47.58 # probably 17.48.02 # :) 17.49.39 # bingo 17.49.40 # ;) 17.59.35 Join Eodun [0] (~Eodun@80-29-30-95.adsl.nuria.telefonica-data.net) 17.59.42 # hi Eodun 17.59.50 # hi quel / all 18.00.03 # I've seen the new langs 18.00.17 # do you like the translation? 18.00.27 # haven't dl yet 18.00.30 # :) 18.00.31 # my exams... 18.00.32 # only a new string 18.00.35 # i know... 18.00.38 # univ is hard 18.00.40 # :P 18.00.55 # oh... did you modify LANG_DIR string? 18.01.16 # it was still untranslated 18.01.34 # I noticed when I put new music in my box 18.02.40 # did i? 18.02.42 # dunno 18.02.45 # i can't remember 18.03.39 # let me check 18.04.21 # not sure if it was LANG or VOICE_dir, really 18.06.55 # :) 18.07.24 # i'll check when i have a spare moment (bit busy right now) 18.08.33 Join XShocK [0] (~XShocK@pcp09492659pcs.nrockv01.md.comcast.net) 18.08.48 # np 18.13.20 Quit Eodun () 18.50.06 *** Saving seen data "./dancer.seen" 19.07.00 Nick Quelsaruk is now known as quel|out (~kvirc@80.103.128.128) 19.13.28 # did somebody test the bootloader besides Linus? 19.13.34 # dunno 19.17.55 Join Stryke` [0] (~Chairman8@resnet-241-86.resnet.umbc.edu) 19.50.19 Join Marder [0] (~MArder@lsn-boi-catv-c124-p218.vtx.ch) 19.55.33 Join El_Barto2 [0] (~adsa@p5082EA27.dip0.t-ipconnect.de) 19.58.18 # hi 19.59.40 # do you know how i could see if my player is charging the batteriesß 19.59.46 # jukebox recorder.. 19.59.52 # is there a led? 20.11.13 # hmm 20.11.20 # if the recorder is charging? 20.11.25 # using rockbox? 20.11.39 # check the batt graphic in the top of the screen 20.11.47 # you should see it animated 20.11.57 Join Bluechip [0] (~BlueChip@cpc3-colc1-3-0-cust61.colc.cable.ntl.com) 20.12.11 # or, you can go to Main Menu (F1)--> Info -->rockbox Info 20.12.29 # and check wheter the batt: show a level, or Charging 20.16.30 Part Bluechip 20.17.06 Join Eodun [0] (~Eodun@80-29-30-95.adsl.nuria.telefonica-data.net) 20.17.35 # hi again 20.27.20 Join quelsaruk [0] (~kvirc@80.103.129.59) 20.27.23 # re 20.28.41 # the problem is... 20.28.53 # the soft hangs 20.28.59 # and i can do nothing 20.35.07 # ¿? 20.35.12 # i lost the conversation 20.35.13 # :) 20.35.37 Join jorbond [0] (~jorbond@dhcp024-209-026-138.cinci.rr.com) 20.44.45 Join thegeek [0] (thegeek@ti521110a080-3006.bb.online.no) 20.45.50 Quit quel|out (Read error: 110 (Connection timed out)) 20.46.10 # no prob 20.48.49 Join lImbus924 [0] (lImbus@5-174.243.81.adsl.skynet.be) 20.50.07 *** Saving seen data "./dancer.seen" 20.50.47 Quit lImbus (" I love my HydraIRC -> http://www.hydrairc.com <-") 20.51.01 Nick lImbus924 is now known as lImbus (lImbus@5-174.243.81.adsl.skynet.be) 20.51.28 Part Marder 20.58.06 # lImbus: do you see it? 21.00.28 Quit cYmen_ ("leaving") 21.00.52 Join cYmen [0] (~cymen@nat-ph3-wh.rz.uni-karlsruhe.de) 21.09.47 # must go 21.09.50 # cu! 21.09.56 Quit quelsaruk ("KVIrc 3.0.1.99 'Realia'") 21.11.03 Quit Eodun () 21.26.34 Quit jorbond (Read error: 110 (Connection timed out)) 21.26.34 Quit thegeek (Read error: 104 (Connection reset by peer)) 22.09.31 Quit El_Barto2 () 22.47.47 Join Patr3ck [0] (~patr3ck@pD9548C9A.dip.t-dialin.net) 22.50.10 *** Saving seen data "./dancer.seen" 22.52.14 # it feels like a good evening for some good commits! ;-) 22.52.40 # yay 22.53.29 # it seems Rockbox is almost starting the dir browser fine on the iriver 23.02.31 # how is the bootloader testing coming along, btw? still only linus and his h120, no? 23.02.40 # yes 23.03.16 # but I hope for some progress in his end 23.03.36 # what still needs progress? 23.04.17 # Linus said he tried booting (the real) rockbox 23.04.32 # and it showed the logo, the disk spun and 23.04.35 # yeah, and it crashed, but this shouldn't depend on linus anymore? 23.04.36 # then hung 23.04.47 # or might this be a bootloader thing? 23.04.48 # it is probably an init issue 23.04.52 # ahh 23.05.11 # yes, it might of course be that 23.05.18 # is all device init put in the bootloader? 23.05.32 # no, it is re-inited by rockbox itself 23.05.44 # then why init in the first place? 23.05.47 # both do the same init I think 23.06.22 # the bootloader needs to init all hw to be able to function properly 23.06.46 # rockbox could be made to depend on that, but it currently doesn't 23.07.09 # small problem anyway, yes, just an ifdef should do 23.07.47 # but this is extremely cool 23.07.54 # we're probably not far away from things starting to function 23.08.03 # nope 23.08.27 # damn, i'm looking forward to having rockbox boot on my player 23.09.07 # only depressing thing is that putting proper emac support in mad is probably going to be a bit hairy 23.09.26 # yes 23.09.33 # without having hack the code to pieces, that is 23.10.18 # the best thing would be to just have another set of defines in fixed.h, but that won't use the unit optimally 23.11.58 Join webguest00 [0] (~d4b63f66@labb.contactor.se) 23.12.37 Join webguest19 [0] (~d4b63f66@labb.contactor.se) 23.12.37 Quit webguest00 (Client Quit) 23.13.36 Join amiconn [0] (~jens@pD95D1342.dip.t-dialin.net) 23.13.46 Part webguest19 23.14.20 # hi all 23.16.15 # good evening 23.17.05 # Cassandra: are you there? 23.22.04 Join [IDC]Dragon [0] (~Joerg@pD9512627.dip.t-dialin.net) 23.22.46 # <[IDC]Dragon> hi there 23.22.55 # hi 23.22.58 # hi Jörg 23.23.47 # <[IDC]Dragon> Gerd's charging patch looks promising (without looking into it) 23.24.39 # good to see work happen in that area 23.24.47 # Hmm, I dunno. 23.25.28 # <[IDC]Dragon> it's on my list since a long time, but below "threshold" 23.25.48 # I had some ideas for the power management too, but going into a different direction 23.26.03 # <[IDC]Dragon> I was close to start a wiki document today 23.26.15 # <[IDC]Dragon> to collect proposals 23.26.32 # <[IDC]Dragon> but no time, and then came Gerd 23.26.40 # - Check power much more frequently than now, at least once per second 23.26.47 # <[IDC]Dragon> yes 23.27.12 # <[IDC]Dragon> at least in USB mode 23.27.27 # <[IDC]Dragon> to detect a spinning disk, if it wasn't us 23.27.30 # amiconn: I'm here, yes. 23.27.31 # - Let the power management gather more info about power states, e.g. whether the hd is spinning, whether the backlight is on 23.28.02 # <[IDC]Dragon> that would have been my 2nd stage: try to model the power situation 23.28.09 # - The external voltage is also available, so the charging algo could estimate the charging current 23.28.32 # Cassandra: I know what that "something" in rtc_init() is that resets the alarm flag. 23.28.40 # <[IDC]Dragon> 1st I would get rid of the startup charging gap, deep discharge, no trickle 23.28.56 # yeah, those options don't make much good 23.28.58 # Oh, right. I hope it made sense to program around it in the way I did. 23.29.02 # What is it? 23.29.43 # <[IDC]Dragon> we should always start charging, unless we find later it's not necessary 23.29.47 # rtc_init() calls rtc_enable_alarm(false); in the end, and this in turn reads the alarm flag, thereby resetting it 23.30.01 # Oh, right. Of course it does. 23.30.54 # [IDC]Dragon: This could be tricky, because charging right away leaves no chance to get the unbiased (by charging current) battery voltage 23.31.20 # I couldn't figure out how to do record on power on like we were discussing last night. Feel free to leap in if you can see an obvious way to do it. 23.31.37 # <[IDC]Dragon> amiconn, maybe we don't need this 23.32.21 # [IDC]Dragon: My idea for the startup is to check voltage first, and enable charging for a short time first (a minute perhaps) only if the voltage is low. 23.32.35 # <[IDC]Dragon> we should calculate the charging current from the DC and battery voltage 23.33.08 # <[IDC]Dragon> then we know how strong we're pulling 23.33.18 # Yes, but you need the battery voltage without charging current to estimate the battery percentage. 23.33.23 # btw, speaking of matters power management related, do I misunderstand the code, or could a short idle timeout cause you to lose settings that haven't been flushed to disk (since the idle detection is in firmware and doesn't use the safe shutdown code). 23.33.26 # <[IDC]Dragon> I'd like to prevent the flat battery problem 23.33.57 # <[IDC]Dragon> rather enable charging already in the bootloader 23.34.18 # [IDC]Dragon: Yes, that's why I would charge right from the start for a minute or so if the batteries are low, then stop & check voltage. 23.35.09 # <[IDC]Dragon> ah, ok, but then you've perhaps pulled the cells "above the worst" already 23.35.09 # If battery voltage is high enough, don't enable charging at startup, but immediately calculate battery state, then start charging if needed 23.36.17 # <[IDC]Dragon> measuring while the HD is spinning may give a good estimation 23.36.25 # The battery voltage with charging current applied doesn't tell you much even when you know the current (by also measuring the input voltage), because you don't know the inner resistance of the cells 23.37.03 # <[IDC]Dragon> do you think it greatly varies 23.37.06 # <[IDC]Dragon> ? 23.37.46 # Yes,definitely. It's highly dependent on charging state. Furthermore it varies across manufacturers, depending on temperature etc. 23.39.16 # <[IDC]Dragon> tricky subject 23.39.23 # In fact, I also thought about improving the battery state estimation by also calculating the inner resistance (measuring the delta v caused by a certain delta i) 23.40.12 # <[IDC]Dragon> I'm not too worried about the gauge 23.40.38 # <[IDC]Dragon> that's 2nd, first I'd like to have a reliable charging 23.41.35 # <[IDC]Dragon> our charge current is rather low, we don't need too fancy algorithms like if we'd be a high speed charger 23.41.39 # It's not about the gauge, that's a side effect. It's about the charging algo, since, as Gerd pointed out, the usual delta-v algorithm doesn't work well, because of the variable load 23.42.11 # <[IDC]Dragon> if in doubt, charge ;-) 23.42.37 # Our charging current is certainly higher than what cell manufacturers would allow as permanent charging current 23.43.20 # <[IDC]Dragon> go to trickle after a time/voltage limit or if the filtered voltage doesn't raise any more 23.43.50 # How do you calculate the time? 23.44.23 # You'd need the (net) charging current, the battery capacity, and the current charging state of the cells. 23.44.27 # <[IDC]Dragon> got me, most simple by capacity and current 23.44.56 # <[IDC]Dragon> apart from the start charge, the got me part 23.45.11 # If the cells are about 80% full, and you feed it another 100%, you definitely overcharge 23.45.36 # <[IDC]Dragon> that's where the no-raise detect comes into play 23.46.08 # <[IDC]Dragon> or a cutoff voltage 23.46.17 # Yes, and that's very problematic in the jukebox environment with its highly variable load, as Gerd pointed out 23.46.53 # Cutoff voltage doesn't help at all, because the chage-end voltage also varies with temperature 23.47.18 # (Much more than it varies with charging state, that's the badness with NiCd/NiMH charging) 23.47.48 # <[IDC]Dragon> ok, so we need a reliable no-raise detector 23.48.09 # Believe me, I once built a charger that only relied on cutoff voltage, and it charged with 1/5 C only 23.48.40 # I almost instantly fried 2 sets of almost-new NiCd cells with it.... 23.49.00 # <[IDC]Dragon> bad cells 23.49.45 # No, these were branded cells 23.50.00 # <[IDC]Dragon> actually, I don't understand why 1/10 C should still be allowed for unlimited time 23.50.19 # <[IDC]Dragon> with the capacity rising to 2500 mAh 23.50.20 # No, it shouldn't, it's too much 23.50.34 # <[IDC]Dragon> make it 1/20 C then 23.50.49 # And for our charging current to be <= 1/10 C, we would need 3500 mAh cells... 23.51.08 # <[IDC]Dragon> my point is, this goes up with capacity, but the AA size is the same 23.51.23 # <[IDC]Dragon> it all has to be dissipated as heat 23.51.59 # <[IDC]Dragon> and AA cells started at 500 mAh 23.52.37 # <[IDC]Dragon> (long time ago, when I was playing with motorized toys ;-) 23.52.46 Join amiconn_ [0] (~jens@pD95D115B.dip.t-dialin.net) 23.53.07 Quit amiconn (Nick collision from services.) 23.53.08 Nick amiconn_ is now known as amiconn (~jens@pD95D115B.dip.t-dialin.net) 23.53.47 # (1) AA cells started even lower than 500 mAh, I have seen 450 mAh cells (still working btw!) 23.53.58 # (2) The heat is only part of the problem 23.54.10 # btw I sort of figured out two ways to implement concurrent sleep timer and wakeup alarm. 23.54.20 # The problem is they both have drawbacks. 23.54.51 Join Trevmar [0] (~trevor@ca-agoura-cuda2h-53.ventca.adelphia.net) 23.55.03 # (1) Defer actually setting the rtc until you power off (eg in safe_shutdown) 23.55.17 # Joerg, did you see the pictures I posted on the Ondio forum today? 23.55.35 # (2) Set immediately but have a watch thread that switches it off if we ever get closer to it than a minute. 23.55.52 # <[IDC]Dragon> hi Trevor, yes, nice 23.56.04 # setting the rtc *alarm*, I mean. 23.56.57 # the hole in front of the mike makes a big difference :) 23.56.58 # [IDC]Dragon: When the cells are full, and you still apply charging current, electrolysis takes place, producing hydrogen and oxygen. This has to be absorbed again by the "charging reserve", otherwise the cell looses electrolyte. 23.57.23 # If the current is too high, this doesn't work fast enough. 23.58.09 # <[IDC]Dragon> we could start to trickle when approaching 23.58.14 # Cassandra: I would prefer option (1) - much more straight forward 23.58.14 Join Digital007 [0] (~acd416ad@labb.contactor.se) 23.58.22 # hi 23.58.24 # <[IDC]Dragon> so, "high" current to empty cells, less while they fill 23.58.45 # Cassandra: And, yes, you're right, idle poweroff should also use safe_shutdown() (imho)