--- Log for 10.07.103 Server: sterling.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 6 days and 14 hours ago 00.00.14 Join paulheu [0] (~pvdh@node1e8c7.a2000.nl) 00.00.37 Quit paulheu (Client Quit) 00.20.24 Quit tpelliott (Read error: 54 (Connection reset by peer)) 00.35.39 Join diddystar5 [0] (Lee@AC8F65C7.ipt.aol.com) 00.35.55 # Zagor: hey 00.36.15 # hi 00.36.35 # Zagor: why is USE_GAMES in bounce.c never used? 00.37.05 # it's removed 00.37.31 # the USE_GAMES macro is deprecated since all games are moved to plugins and thus don't take up extra space 00.37.46 # Zagor: sorry i meant USE_CLOCK 00.38.15 # ok. that's because it talks to the rtc, which is not supported by the plugin api 00.38.31 # ok i see 00.39.33 Join tpelliott [0] (telliott@208.251.255.120) 00.39.58 # diddystar5: you'll be pleased to know ive finished my wormlet patch, its on the patch tracker and Zagor is going to try and add it to main source sometime this week hopefully 00.39.59 # ;p 00.40.30 # oooh thats cool MT 00.40.50 # i'm gonna give it a try now 00.41.58 Join BoD[] [0] (~BoD@ca-sqy-4-189.w80-8.abo.wanadoo.fr) 00.42.10 # hi! 00.42.23 # hey there BoD[] 00.44.28 # MT: have you tried to flash your box yet? 00.44.42 # i mean the other flash ;) 00.46.26 # no, and i doubt i will 00.46.32 # boots fast enough for me atm 00.46.41 # * Stevie-O tries flashing with his digital camera flash 00.47.24 # i gave it a try work very well and VERY fast 00.47.55 Quit mecraw ("Trillian (http://www.ceruleanstudios.com)") 00.48.04 # hmm 00.48.06 Part Dario 00.48.13 # now zagor has fixed that bug i may give it a try 00.49.34 # i got it to work without that bug fix 00.50.51 Quit diddystar5 ("Gotta Go!") 00.55.26 Join diddystar5 [0] (Lee@AC8F65C7.ipt.aol.com) 00.57.23 # MT: your patch does not work while running in flash, i had to do a normal boot 00.57.43 # sure it does 00.57.52 # you just havent flashed the correct image 00.57.58 # what is this flash thing 00.58.07 # as to accomodate those menus, the plugin api had to be changed 00.58.23 # so they wont work with default firmwares 00.58.38 # BoD[]: you can flash rockbox instead of the archos firmware 00.58.44 # oooo i see 00.58.53 # wow ... it works ? 00.59.03 # :) does it mean it boots faster ? 00.59.06 # 1 sec and ill change my flash ver 00.59.11 # a lot faster 00.59.18 # 4 secs for me bod 00.59.28 # how do you flash it ? 00.59.41 # diddystar5: it wont work unless you flash a compressed version of the firmware that has been compiled with my patch applied 00.59.49 # BoD[]: using a rockbox plugin 01.00.01 # check out Jörgs video to see the speed: http://joerg.hohensohn.bei.t-online.de/archos/rockbox_flash_boot.avi 01.00.11 # i know MT im making one right now 01.00.14 # ok I'll watch that 01.00.39 # I didn't try rockbox since there is the plugin system 01.01.16 # you've missed a bit then :) 01.01.20 # wow is it a divx 01.01.26 # I need to install divx codecs 01.01.44 # yes it is 01.01.50 # ok wait 01.02.46 Quit diddystar5 ("Gotta Go!") 01.02.55 # while it's downloading ... 01.03.16 # so is the "flash" plugin in the default rockbox download ? 01.03.36 # mmmmmm 01.03.37 # no, it's only experimental right now. it will be polished and released in the next few days 01.03.46 # ok 01.03.56 # well maybe I can wait till then :) 01.04.05 # :) 01.05.00 # wow :))))))))) 01.05.10 # ok I've seen the video 01.05.16 # and want to try it now :))) 01.05.20 # hehe 01.05.28 # id wait tbh 01.05.50 # i didnt like the look of http://rockbox.haxx.se/mail/archive/rockbox-archive-2003-07/0364.shtml 01.06.24 # heh, that's how it goes when you become too eager :) 01.06.26 # woops 01.06.40 # ok I'll wait then 01.06.54 # especially fi you have an FM :) 01.07.00 # I have a recorder 01.07.03 # 20 01.10.16 # anyway that's REALLY great 01.10.39 # the reasons i wont do it 01.10.49 # you've only got 100 flashes in that beast 01.10.59 # 100? 01.11.02 # no, you've got 100000 flashes 01.11.11 # mm? 01.11.13 # i thought it was 100k 01.11.20 # 100.000 01.11.28 # yes 01.11.29 # im sure Dragon said 100 on the mailing list 01.11.32 # well 01.11.36 # that changes my perspective 01.11.40 # flash me up 01.11.44 # hehe 01.11.48 # don't tell me you thought that that was a decimal separator 01.12.03 # I expect a comma there, but please, some common sense 01.12.06 # im british, shoot me now :/ 01.12.10 # haha 01.12.21 # i shall endeavour to hide furtively now 01.12.35 # :)) 01.12.39 # 100 scared me a lot 01.12.48 # i make about that many a week 01.12.49 # * Stevie-O makes a new flash chip that can be flashed exactly 100.001 times (that's 1.00001x10^2) 01.13.21 # lol, I'm used to flash chips that are about a million write cycles 01.13.23 # i still urge you all to be patient for another day or so until we make this more official 01.13.35 # i will wait 01.15.31 Quit tpelliott ("Trillian (http://www.ceruleanstudios.com)") 01.15.37 # would it be feasible &/| easy to write a plugin that just make the light blink ... in rithm with the music ? 01.16.04 # we can't extract the rythm, since we only see mp3 data 01.16.05 # have you been talking to tracktheripper? 01.16.39 # well when I say "in rhythm" I mean just something like the vumeters 01.17.10 # well yeah that would be possible. very strange-looking, but possible. 01.17.17 Join tracktheripper [0] (jirc@ACBBE91B.ipt.aol.com) 01.17.24 # * Stevie-O tries some mozilla extensions 01.17.27 # hey 01.18.04 # hi 01.18.11 # possible but easy ? :) I would like to write it but of course never wrote something for rockbox 01.18.35 # if it was easy someone would have done it 01.19.02 # stevie : maybe nobody has the need for something that would make the light blink ;) 01.19.11 # it would just blink apparently at random unless your music only contains very a loud bass drum 01.19.23 # I assume it would discharge the battery fast? 01.19.23 # hi zagor stevie and bod 01.19.28 # hi track! 01.19.32 # hello 01.19.35 # whats up? 01.19.40 # did I miss anything? 01.21.00 # what does ISO stand for? Ive seen ISO used a lot for computer and electronic terms 01.21.13 # i guess international standard organism 01.21.19 # or zation 01.21.46 # well i thought ISO meant international standards organisation but I wasn't sure if that was correct 01.21.58 # International Organization for Standardization 01.22.06 # == IOS :) so that's stupid 01.22.07 # ahhhhhhh 01.22.20 # its ISO not IOS :) 01.22.43 # I know but that's what they say on their site 01.22.47 # yea you are right 01.22.51 # ive just seen it myself :-) 01.23.29 # Because "International Organization for Standardization" would have different abbreviations in different languages ("IOS" in English, "OIN" in French for Organisation internationale de normalisation), it was decided at the outset to use a word derived from the Greek isos, meaning "equal". Therefore, whatever the country, whatever the language, the short form of the organization's name is always ISO. 01.23.49 # :-) 01.24.15 # BoD What do u think of simulating the Player's LCD on the Recorder? 01.24.35 # track : what for 01.24.53 # larger icons, larger font, slightly less cluttered 01.25.00 # lol 01.25.29 # you can just choose a larger font on the recorder ! 01.25.38 # oops! 01.25.48 # ((never thought of that!)) 01.25.56 # lmao 01.25.56 # I'm not sure about the icons though ? are they special characters in the font ? 01.26.06 # yea 01.26.12 # no, they are fixed 01.26.13 # they are hard-wired into the Player's LCD 01.26.42 # zagor : ok 01.26.52 # track: I was talking about the recorder 01.27.06 # oh ok 01.27.26 # Ive never used a Player so I cannot comment on its interface 01.27.32 # i'm off to bed. night all. 01.27.37 # bye 01.27.40 # Zagor how does the player's LCD compare to the Recorders? 01.27.48 Quit Zagor ("Client exiting") 01.28.07 # well I'm sure they are crap :) 01.28.43 # that feature request was cool "Invert the Player's LCD" :-) 01.29.02 # did they answer it's not feasible ? 01.29.26 # hi all 01.29.34 # hi guest 01.29.40 # OIs there some news about the Falshale firmware 01.30.24 # you mean flashable ? 01.30.48 # no, the falshale 01.30.52 # from Falshale, NJ 01.31.17 # :)))) 01.32.35 # no flashable , sorry 01.33.39 # I don't know if it's news but you can look at this : http://joerg.hohensohn.bei.t-online.de/archos/rockbox_flash_boot.avi 01.34.50 # night all 01.34.52 Quit tracktheripper ("Leaving") 01.39.01 Quit Schnueff (sterling.freenode.net irc.freenode.net) 01.39.01 NSplit sterling.freenode.net irc.freenode.net 01.39.01 Quit ricII|work (sterling.freenode.net irc.freenode.net) 01.41.47 Join Guest [0] (jirc@p50875C52.dip.t-dialin.net) 01.42.54 Quit Guest (Client Quit) 01.48.04 NHeal sterling.freenode.net irc.freenode.net 01.48.04 NJoin Schnueff [0] (mah@d096.stw.stud.uni-saarland.de) 01.50.45 # has someone a .ucl file for the recorder that I could flash to aqvoid the ATA:-11 problem and get it to boot into rockbox in 3-4 secs .... like the others luky guys ... thanks 01.52.47 NJoin ricII|work [0] (~ricv@sticsgr-7.dsl.vianetworks.nl) 01.56.30 *** Saving seen data "./dancer.seen" 02.03.25 Join tpelliott [0] (telliott@208.251.255.120) 02.16.14 # http://www.sco.com/company/feedback/thanks.html 02.23.53 Quit tpelliott ("Trillian (http://www.ceruleanstudios.com)") 02.27.17 Quit sobepmp (""Erection Reset by Beer"") 02.32.53 Join tpelliott [0] (telliott@208.251.255.120) 02.32.58 # * Stevie-O yawns 02.36.39 # I just HAD to see if my Archos would flash Rombox. It did and I got the expected result "ATA error: -11" but I do get the safe ON+F1 boot so I'm happy it works. 02.37.31 # what's this ON+F1 boot thing? 02.38.08 # It's safe mode. Boots to the original Archos firmware. 02.38.48 # * Stevie-O would hardly consider that 'safe'... ;) 02.39.10 # It's better than a doorstop :) 02.39.57 # only by a hair :D 02.40.03 # ata error -11 eh? 02.40.52 # Yes. The flashed version of Rockbox still has a bug. Read thye mailing list. 02.43.44 # this is strange 02.45.30 # is the source tree that spawned the rockbox-flash code available? 02.57.45 # wtf 03.00.42 # hey tpelliott 03.00.44 # you here? 03.01.24 # I'm here but I'm not a programmer. 03.01.33 # that's quite alright 03.01.38 # does it say 03.02.00 # ATA error: -11 03.02.06 # Press ON to debug 03.02.08 # ? 03.02.15 # Yes. 03.02.22 # something's not right 03.02.38 # see, -11 isn't a valid value for us to be getting 03.02.54 # i assume you have a plain old Recorder? 03.02.55 # You can still get it working by holding F1 when you turn it on. 03.03.16 Join earHurts [0] (~zic@pool-151-200-35-215.res.east.verizon.net) 03.03.42 # Yes. I don't want the FM since they took of the digital I/O 03.03.46 # one valid value IS -1 03.03.48 # off 03.03.52 # How are you gentlemen !! 03.04.24 # that and the battery, I'm beginning to regret getting the fm 03.04.25 # Somebody have set us up the bomb 03.04.30 # * Stevie-O thwaps td 03.04.37 # but it is smaller and lighter & better looking 03.04.38 # I'm ok. Most of the others must be off programming. 03.04.55 # Make your time 03.04.57 # has anybody here looked at the ata -11 issue? 03.05.09 # nope 03.05.20 # what I don't understand is that -11 isn't a valid value 03.05.22 # the issue with the rombox? 03.05.35 # Joerg is off working on that now. 03.05.37 # unless our snprintf is buggy 03.05.49 # joerg is probably asleep, it's 3am there 03.05.57 # is (unsigned) -11? 03.06.06 # earHurts: no 03.06.26 # ok. I wasn't sure. It would be best to wait for the all-clear from him. 03.06.29 # our printf rountines don't undeerstand shorts 03.06.40 # it's not a short 03.06.42 # or longs 03.06.48 # it's not a long 03.06.53 # wheres the snprintf definition? 03.07.01 # -11 == 245 right ? 03.07.02 # stdio.h 03.07.05 # ? 03.07.18 # that's the prototype 03.07.20 # if it's a char 03.07.20 # wheres the soruce? 03.07.23 # BoD[]: only for bytes 03.07.26 # this is an int 03.07.30 # oh firmware/something 03.07.39 # stdio.c? 03.07.51 # I'm not at my computer 03.07.55 # ah 03.08.02 # firmware/common/snprintf.c 03.08.09 # Actually, Joerg has some new files on his site. A couple of .ucl files yuou could burn as the secong copy. 03.08.15 # then it's 65525 ? :) 03.08.38 # no 03.08.40 # our ints are 32 bits 03.08.45 # arf 03.08.54 # so try 4294967285 03.08.59 # those .ucl are really britney spheres mpegs he's hiding from the riaa 03.09.01 # which is definitely not returned by ata_init 03.09.12 # haha 03.09.13 # 4294967285 03.09.16 # :))) 03.09.20 # ok 03.09.22 # val = sign = -1 03.09.28 # val = 1 03.09.45 # *--str = '1' 03.09.51 # val = 0 03.10.18 # hm 03.10.22 # Have you guys done the rombox flashing yet? 03.10.30 # not me 03.10.35 # I have an fm 03.10.55 # it's tremedous work, i can't wait to try 03.11.35 # did anybody watch that stupid reality show last night? 03.11.44 # I will probably try the .ucl files since my box is working in safe mode. Safe mode should still work. 03.11.48 # what channel? 03.11.48 # did she pick the guy or the money? 03.12.01 # uh, nbc? 03.12.07 # safe mode?? 03.12.39 # anyway I have to go to bed:) 03.12.42 # see you all! 03.12.45 # turn on your box holding F1 03.12.48 # night 03.13.01 Quit BoD[] ("dodozitude") 03.13.03 # oh rombox safe mode 03.14.43 # Yes. Another reason I'm glad I have the older recorder, plus, if the batteries go dead, I can put in a spare set. 03.15.15 # yeah. just taunt me ok? ;) 03.15.35 # I can't believe they took out the digital I/O on the FM 03.15.54 # they didn't take it out 03.16.07 # of the advertising & specs 03.16.07 # Someone told me they did. 03.16.33 # i might not have bought it if they had 03.16.54 # i remeber when i tried it 03.17.02 # and got nothing 03.17.11 # You can still play your FM recorder through your reciever's Toslink connection? Cool. 03.18.01 # hmmm 03.18.22 # I play mine through my Sound Blaster Extigy. It works even if the computer is turned off. 03.18.24 # tpelliott: you still have RB flashed? 03.18.56 # i just play my mp3s on my pc 03.19.08 # my laptop sound is broken :( 03.19.17 # Yes, but with the ATA error. 03.19.30 # tpelliott: but you can still boot the archos fw 03.20.00 # if you have the rockbox ajbrec.ajz on there does it load that? 03.20.11 # They have some nice bookshelf systems with USB input for sound from your computer. 03.20.27 # I can still boot Archos in safe mode. 03.20.40 # but that means no rolo 03.20.45 # that's what I mean 03.20.50 # when you boot the archos in this 'safe mode' 03.21.03 # does the archos fw do its automatic ROLO thing? 03.21.14 # Yes. Safe mode roro's Rockbox like normal. 03.21.18 # yeah, what stevie said 03.21.20 # excellent 03.21.25 # I need you to do me a favor :) 03.21.31 # in the debug menu 03.21.45 # there should be an option to 'dump roms' 03.21.45 # so it's still a quicker boot? 03.22.06 # Yes...I'm in the debug menu. 03.22.12 # select that option 03.22.18 # it will create two files on your thing 03.22.26 # I've done that, per instructions. 03.22.34 # wait 03.22.36 # per what instructions? 03.22.43 # Rombox. 03.22.48 # he he, he said 'thing' 03.22.56 # earHurts 03.23.04 # i'm about to make the rest of you hurt too 03.23.04 # yeah? 03.23.07 # http://joerg.hohensohn.bei.t-online.de/archos/ 03.23.50 # * Stevie-O teaches joerg to wrap his goddamn txt lines 03.24.11 # yeah, I had to d/l his instructions 03.24.16 # oh 03.24.17 # okay 03.24.30 # so you have backups of those internal rom files on your pc? 03.24.38 # I use Ultra Edit, which has a wrap icon. 03.24.51 # The large one. 03.24.57 # i use Opera 03.25.08 # which doesn't have such a button 03.25.08 # :D 03.25.19 # okay 03.25.33 # I need you to use the debug menu to generate a *new* set of rom files 03.26.02 # then I need you to zip both up and mail them to me 03.26.15 # It should be the same as in "release1.zip" 03.26.21 # no 03.26.38 # because those rom files are from your flash chip 03.27.02 # unless you know something I don't 03.27.04 # he means joerg's eelease 03.27.05 # Isn't that what I just put on my flash chip? 03.27.29 # isnt it a plugin and stuff? 03.27.53 # The plugin just loads the .bin. 03.27.53 # i need the actual contents of your flash rom, as-is 03.27.53 # I don't have a Recorder 03.28.29 # they're probably the same. but give stevie what's there 03.28.46 # earHurts: they can't be the same, if it can boot the original archos fw 03.29.18 # That's built in to Joerg's .bin file (Safe mode). 03.29.46 # but not everybody has the same archos fw 03.29.58 # I'm going to try one of the .ucl files first. 03.30.10 # So you want my original? 03.30.13 # no 03.30.19 # I need the current contents of your flash ROM 03.30.38 # as the dump command would generate them right now 03.31.23 # brb, i gotta find my laptop charger 03.31.39 # ok. 03.31.55 # I'll be back in a few minutes. 03.32.43 Quit Stevie-O (Read error: 54 (Connection reset by peer)) 03.32.49 Join Stevie-O [0] (whatsit2u@user-2ininsl.dialup.mindspring.com) 03.34.26 # who mythed me 03.34.59 # you're legendary, but I didn't myth you 03.35.12 # :P 03.36.17 # stevie, what do you hope to find in tpe's dumps? 03.36.57 # some information 03.37.27 # thqank you, mr. obvious 03.38.16 # happy to help 03.38.58 # i thought you might want to convert them to .bmps, print them out, and decorate your walls with them 03.39.05 # hmmm 03.39.07 # theres an idea 03.39.56 # * Stevie-O wonders what tpelliott is doing 03.47.31 # this would be a record amount of time for the dump_rom to complete? 03.48.22 # he's hand verifying each bit is 1 or 0 03.48.29 # uh huh 03.48.34 # how is he hand verifying it? 03.49.25 # you asked for it: 03.49.27 # he got a microscope? 03.49.28 # by hand 03.49.44 # an electron microscope 03.51.07 # whats special about his rom? 03.51.39 # it's flashed by rombox 03.53.31 # it's handcrafted by Donald Knuth from pure free-ranged bits 03.54.12 # lmao 03.54.25 # no, it's not 03.54.30 # the bits are kept in captivity 03.54.38 # it's the veal of flash sectors 03.54.57 # it's like free range chicken: they/were/ free ranging 03.55.46 # now they'ee on thrir way to the afterlife accompanied by an honor gaurd of l'orange 03.56.31 *** Saving seen data "./dancer.seen" 03.59.11 # I'm back 04.00.22 # I just tried "rockbox_master.ucl" and I naw have Rockbox working from ROM! I love it! 04.00.47 # on an fm? 04.01.02 # No, older recorder. 04.01.29 # I'm sure a version for FM will be comming shortly. 04.01.57 # The newer .ucl file fixed the ATA errr. 04.01.57 # yeah 04.03.03 # You can flash daily builds but you have to descramble the AJZ file, then compress it to a .ucl file. 04.06.24 # Do you ust the digital i/o on your FM? 04.07.35 # nope 04.07.58 # It's great if you have a home theater setup. 04.11.10 # digital out doesn't work 04.11.20 # i wanna know what this ucl file is 04.11.33 # I just connect my pc to my sony mini sterep 04.13.55 # Stevie-O: ucl is just the compression format that dragon is using for his roms 04.14.12 # i wanna know more about this format] 04.14.42 # Stevie-O: i believe there is a link in his text file 04.15.21 # yeah, http://www.oberhumer.com/opensource/ucl/ 04.17.06 # hmm 04.18.05 # I don't see any actual information on the algorithm 04.20.07 # Stevie-O: yeah, it's quite sparse. there is some notes in the README in the tarball 04.20.16 # I just tried the "rockbox_slave.ucl" file, just for the heck of it and it gave me another ATA error -41 04.21.25 Quit Stevie-O (Read error: 104 (Connection reset by peer)) 04.21.27 Join OliverKlozoff [0] (whatsit2u@user-2ininsl.dialup.mindspring.com) 04.21.48 # Works fine, going back to the "rockbox_master.ucl" file. 04.38.17 # good god 04.38.30 # i could ahve compiled a kernel in the time it takes ucl to ./configure 04.39.00 # You using Rombox? 04.39.15 # root@linux.woodhall.barn [03:36 AM] '~/ucl-1.01' 04.39.15 # > # ./configure 04.39.22 # config.status: creating config.h 04.39.22 # root@linux.woodhall.barn [03:40 AM] '~/ucl-1.01' 04.39.27 # ok, so slight exaggeration 04.39.32 # lol 04.39.34 # i could probably have made bzimage 04.39.45 # try: time ./configure 04.39.57 # im not going through it again! 04.39.58 # heh 04.40.07 # lol 04.40.49 # I'm not a programmer but I want a .ucl that dosen't check for firmware on the hard drive. 04.41.02 # why? 04.41.18 # SPEED!!! :) 04.41.29 # its got to do the equivalent anyway 04.41.36 # because it has to spin up to read the root directory 04.42.01 # ok. I thaught Jorg said it added a second to boot. 04.42.11 # Jourg 04.42.20 # if it does then it needs to be fixed :P 04.42.47 # it should be able to do the initial rolo check when it's reading the root dir 04.42.59 # Cool. 04.43.37 # I love the fact that we never have to see Archos firmware again! 04.43.45 # mm 04.43.52 # i find it incredibleyt scary actually 04.44.02 # thats what i really liked about rockbox 04.44.08 # i could fuck about with it 04.44.24 # and at the end of the day, i could fix all my mistakes just by plugging it into usb 04.44.41 # im confident about other peoples stuff, just my own changes that scare me 04.44.49 # lol 04.44.52 # then don't flash it :D 04.45.06 # fm anyways :) 04.45.09 # I used "rockbox_master.ucl" to get around the ATA error. Worked great! 04.45.21 # mmm 04.45.33 # Zagor fixed that in rockbox source 04.45.42 # you need new images 04.45.51 # ata-11 problem? 04.48.07 # I got the fixed version anyway from his site. 04.48.27 # Yes. ATA Error: -11 04.50.29 # I'm sure it will be released and we'll see a news flash on the main Rockbox page tomarrow. 04.51.08 # there is one already .. 04.51.18 # 2003-07-09 22:04 zagor firmware/drivers/ata.c 04.51.18 # Cold start fixes: master_slave_select() now checks for BSY as well as RDY (since disks are BSY during powerup). Also, wait_for_bsy() looks at ATA_STATUS instead of ATA_ALT_STATUS, since the address of ATA_ALT_STATUS is not determined until later. 04.52.12 Quit hardeep ("[BX] Silly wabbit, BitchX is for kids!") 04.52.40 # I'm not a programmer but I want to eventually understand the source code enough to make personal changes. 05.03.08 # what changes? 05.05.12 # Menu items, etc. 05.05.40 # I just flashed with the current daily build and all is well! 05.30.27 Part tpelliott 05.42.33 Join tpelliott [0] (telliott@208.251.255.120) 05.44.33 Join Stevie-O [0] (whatsit2u@user-2inil6r.dialup.mindspring.com) 05.48.05 # Stevie-O, I read your latest message on the list but I no longer have the ATA error, in fact, I burned the latest (fixed) daily build. 05.53.18 Quit OliverKlozoff (Read error: 60 (Operation timed out)) 05.56.34 *** Saving seen data "./dancer.seen" 05.58.03 Part tpelliott 06.12.25 # does anyone here know wtf a flyback transformer is? 06.13.45 Join f0xShot [0] (WinNT@142.103.17.77) 06.28.02 Nick thu_ is now known as thu (~thu@h24-87-64-169.vc.shawcable.net) 07.02.15 # a transformer that fits on the back of a fly 07.02.39 # they come in house, horse, and bluebottle sizes 07.02.46 # thu! 07.16.51 Join [IDC]Dragon [0] (~idc-drago@p508610DF.dip.t-dialin.net) 07.17.11 # <[IDC]Dragon> Good morning! 07.22.28 # <[IDC]Dragon> (everybody's sleeping) 07.48.02 # lol 07.48.10 # isnt it like 6am there? 07.48.21 # or hell, i bet its nearly 8am 07.48.58 # seeing as how it's nearly 2am here 07.49.03 # bedtime phor me 07.50.57 # Jorg? 07.52.12 # IDC, are you the rombox writer? 07.52.57 Quit adi|home (Read error: 60 (Operation timed out)) 07.56.35 *** Saving seen data "./dancer.seen" 08.06.15 # earHurts: ? 08.09.35 Quit Stevie-O (Read error: 110 (Connection timed out)) 08.25.18 Quit thu ("reboot") 08.30.57 # <[IDC]Dragon> Sorry for not reading, was away. Gotta go now. 08.33.51 # thu? 08.34.10 # <[IDC]Dragon> ? 08.34.18 # ? 08.34.26 # <[IDC]Dragon> echo 08.34.34 # just wanted to congratulate you on rombox 08.35.00 # <[IDC]Dragon> Just made a new release, hope the ATA is fixed now, thanks th Björn. 08.35.09 Join adi|home [0] (~adi|home@as5300-9.216-194-23-50.nyc.ny.metconnect.net) 08.35.17 # I'm waiting for fm 08.35.32 # looks like it's a power issue 08.35.40 # <[IDC]Dragon> OK, next week I'll get access to an FM from a friend. 08.35.53 # <[IDC]Dragon> Dont't try FM now! 08.36.04 # yeah, I know 08.36.23 # <[IDC]Dragon> The bootloader isn't made for it, the firmware contains a recorder image. 08.36.52 # but according to someone on the list it acts like recorder.ajzs did until changes were made for the different power 08.37.20 # I thought the bootloader /copied/ the existing rom image? 08.37.45 # <[IDC]Dragon> Yes, and it checks F1. That code has to be different. 08.38.11 # <[IDC]Dragon> Not the existing image, the one in my big file. 08.38.17 # ah, I didn't realize the button hardware differed too 08.38.27 # <[IDC]Dragon> So this has to be authored for FM. 08.38.33 # oh, wait, yes I recall the button thing 08.38.48 # first time I loaded a recorder ajz. scary 08.39.18 # I''m very anxious to try the rombox 08.39.42 # <[IDC]Dragon> REally gotta go now. 08.39.44 # it amazes me you wrote it without having a flashable rom in your archos 08.39.47 # bye 08.39.52 # thanks 08.39.52 Quit [IDC]Dragon () 09.25.26 Quit Guest57 ("Leaving") 09.47.02 Join thu [0] (~thu@h24-87-64-169.vc.shawcable.net) 09.56.40 *** Saving seen data "./dancer.seen" 09.59.13 Join bobTHC [0] (~bobTHC@AMarseille-206-2-1-9.w80-11.abo.wanadoo.fr) 09.59.20 # good morning 10.00.29 Quit Nibbler (sterling.freenode.net irc.freenode.net) 10.00.29 NSplit sterling.freenode.net irc.freenode.net 10.00.29 Quit mbr (sterling.freenode.net irc.freenode.net) 10.00.29 Quit PsycoXul (sterling.freenode.net irc.freenode.net) 10.00.48 NHeal sterling.freenode.net irc.freenode.net 10.00.48 NJoin Nibbler [0] (~Nibbler@port-212-202-193-217.reverse.qdsl-home.de) 10.00.48 NJoin mbr [0] (~mb@stlx01.stz-softwaretechnik.de) 10.00.48 NJoin PsycoXul [20] (psyco@adsl-63-205-41-164.dsl.lsan03.pacbell.net) 11.08.26 Join Lynx0 [0] (user@134.95.189.59) 11.35.16 Join TotMacher [0] (tot@ip67.rsidus.riege.de) 11.41.48 Join tracktheripper [0] (jirc@ACB95D50.ipt.aol.com) 11.44.42 Quit tracktheripper (Client Quit) 11.56.42 *** Saving seen data "./dancer.seen" 12.41.55 Join SillyFly [0] (~chatzilla@212.199.220.239.forward.012.net.il) 12.41.55 Quit bobTHC (Read error: 54 (Connection reset by peer)) 12.42.43 # anybody available? 12.46.25 # guess not..... 13.54.36 # hi... 13.56.43 *** Saving seen data "./dancer.seen" 13.56.47 Join choichoi [0] (~francoi@liifi-27-16.n.club-internet.fr) 13.56.57 # hello 13.57.06 # y a des francais ici ? 13.58.38 # can i change the battrey on my studio10 13.58.47 # to have a long power 14.01.03 # ? 14.02.53 Join langhaarrocker [200] (~Phil@31.15.204.212.sr1.DTM1.ip.versanet.de) 14.03.12 # argh! A wormlet patch! :) 14.03.46 # choichoi: yes, you can 14.04.01 # with 1800mah 14.04.02 # ? 14.04.29 # choichoi: i think so, even 2000mhA 14.04.35 # oky 14.04.58 # what is your archos ? 14.05.11 # thee model 14.05.18 # recorder 20 14.05.39 Quit SillyFly ("ChatZilla 0.8.31 [Mozilla rv:1.4/20030624]") 14.05.56 # do you speak french ? 14.06.05 # because i am 14.06.09 # choichoi: look in your manual for description of how to replace batteries 14.06.10 # french 14.06.11 # non 14.06.27 # a oui 14.06.45 # ouai je sais comment on le demonte 14.06.54 # c pas tre difficile !!! 14.07.20 # i know the manuel 14.07.33 # tchao 14.07.36 # bye 14.07.42 # au revoir 14.08.04 Quit choichoi (Read error: 104 (Connection reset by peer)) 14.08.34 Quit langhaarrocker (Remote closed the connection) 15.48.29 Join choichoi [0] (~francoi@liifi-27-63.n.club-internet.fr) 15.50.03 Join joshn [0] (joshn@204.251.225.88) 15.50.27 Quit joshn (Client Quit) 15.53.20 # how do you change the memory cach 15.53.22 # ? 15.53.30 # what do you mean? 15.53.32 # is it dificult ? 15.53.55 # of your juke box 15.53.58 # memory cach?? 15.54.03 # 2mb a 8 mb 15.54.04 # ? 15.54.11 # i am french 15.54.28 # ah, i think it's difficult. have you seen pictures? 15.54.47 # yes 15.54.49 # :) 15.55.13 # but the man change the memory chip ? 15.55.31 # or is it the same ? 15.56.47 *** Saving seen data "./dancer.seen" 15.56.48 # i don't know 15.57.43 # hum 15.58.05 # and the sound mod with the resistance ? 15.58.34 # haven't heard about that one 15.58.44 # what does it do? 15.59.08 # il debloque l ampli non ? 15.59.26 # the volume is higher 16.01.13 # ok 16.01.43 # I see that on www.rockbox...... 16.14.39 Join SillyFly [0] (~chatzilla@212.199.220.239.forward.012.net.il) 16.19.49 # * Stevie[FP] is back from [pewf] [gone 1day 17hrs 5mins 35secs] [KS] 16.20.46 Quit choichoi () 16.27.14 Quit SillyFly ("ChatZilla 0.8.31 [Mozilla rv:1.4/20030624]") 16.35.46 Quit earHurts (Read error: 60 (Operation timed out)) 16.50.35 Join hardeep [0] (1098@208.247.65.237) 17.23.55 # * Stevie[FP] is away [(Auto-Away after 1hr)] [KS-MsgLog Off] 17.26.59 Join Neo [0] (~Neo@209.187.167.213) 17.27.05 # hows rombox comming 17.32.10 # ? 17.32.13 Quit Neo ("Client exiting") 17.56.15 Join mecraw [0] (~mecraw@69.2.235.2) 17.56.22 Quit TotMacher () 17.56.52 *** Saving seen data "./dancer.seen" 18.34.28 Quit Lynx0 ("Client Exiting") 19.30.31 Quit MT (Read error: 110 (Connection timed out)) 19.31.27 Join MT [0] (mt@fido.impulsed.net) 19.31.32 Quit MT (Remote closed the connection) 19.37.04 Join _aLF [0] (~Alexandre@AGrenoble-203-1-20-125.w81-49.abo.wanadoo.fr) 19.50.00 Quit hardeep ("BitchX: it keeps going and going and going and going and...") 19.56.53 *** Saving seen data "./dancer.seen" 20.14.33 Join msoultan [0] (msoultan@dhcp202-057.csulb.edu) 20.17.22 Join Snorlax [0] (Snorlax@h234n2fls34o883.telia.com) 20.36.19 Join Neo [0] (~Neo@209.187.167.213) 20.36.30 # hows rombox commin 20.36.59 Join MT [0] (mt@fido.impulsed.net) 20.37.13 # hey 20.37.17 Nick MT is now known as MT` (mt@fido.impulsed.net) 20.37.25 # anyone here working on rombox? 20.37.31 Nick MT` is now known as MT (mt@fido.impulsed.net) 20.38.09 # ? 20.39.32 Quit MT (Client Quit) 20.39.34 # anyone here working on rombox? 20.40.17 Join MT [0] (mt@no.beer.for.beating.me.uk) 20.41.07 # hi 20.42.56 Join REBELinBLUE [0] (Stephen@modem-3871.aardvark.dialup.pol.co.uk) 20.43.00 # hey 20.45.09 # u workin on rombox or know how its goin? 20.45.29 # rombox? 20.45.47 # yeh 20.45.51 # the next rockbox 20.45.53 # its a rom 20.45.58 # Oh :-o 20.46.01 # flashes the rom to put the os in 20.46.06 # ah right 20.46.15 # sounds dangerous 20.46.23 # lol 20.46.25 # its not 20.46.27 # i odnt think 20.46.30 # does anyone know how easy it would be to modify the code so that playlists are shown first 20.46.43 # playlists the m3u? 20.46.58 # Well if the unit loses power/crashes etc whilst flashing the ROM you will have a blank ROM 20.47.09 # yeh 20.47.16 # i guess thats a chance ull have to take 20.47.18 # \:) 20.47.19 # Yes M3U files, as in so they show before MP3 files but after directories 20.47.39 # if your motherboard loses power during a flash, you also have a blank rom 20.47.40 # do u want directories m3u then mp3 20.47.48 # yeah 20.47.48 # yeh 20.47.52 # hmmm 20.47.58 # im not sure how u can do that 20.48.09 # the safety net with rockbox flash is that its running on batteries 20.48.10 # currently the directories are shown first then MP3 and M3U are just mixed in together 20.48.17 # so unless you try to flash with zero charge 20.48.23 # it does the files that u use more first then the other ones 20.48.29 # no 20.48.30 # try to sort them how u want on ur pc 20.48.32 # or mac 20.48.39 # it does them in alphanumeric order 20.48.46 # yeh exactly 20.48.56 # but directories appear first in the structure 20.49.01 # let me look at the code 20.49.04 # MT, u workin on rombox? 20.49.07 # I'll take a look at the rockbox source and try it, just wondered if anyone else had done it 20.49.15 # no, but im aware of the principles 20.49.25 # whens it comming out 20.49.35 # Yeh Folders before Files is a logical setup. I did that in my web file manager :D 20.50.00 # o~REBELinBLUE: if i get bored/distracted the file you should be looking at is apps/tree.c 20.50.30 # oh sure 20.50.37 # it shouldnt be too hard 20.50.44 # what model do you have? 20.50.50 # i shall try and do it now 20.50.53 # FM Recorder 20.51.13 # the reason I ask is because I have created a series of play lists 20.51.20 # i have a couple of patches applied to my source tree .. 20.51.39 # so i can either do you a patch for you to use to compile your own 20.51.45 # one in each album directory called "Play entire album" which basically plays the album in the correct order, but of course because it starts with P its half way down the list 20.51.57 # or use my firmware 20.52.00 # aha 20.52.39 # If you wouldn't mind giving me a patch I would be very greatful 20.52.46 # np 20.53.20 # if you ask me again in like 1hr 20.53.25 # i should ahve it done 20.53.33 # Spent a few hours sorting out my Archos today, transferring everything to it again, creating playlists etc cause I had to get a replacement yesterday 20.53.39 # im packing to go on holiday tomorrow as well you see :) 20.53.48 # ah right :D 20.53.59 # yeah, i know the feeling i spent virtually the entire weekend renaming, organising and tagging mp3s 20.54.03 # 17gb 20.54.31 # now everything is arranged by artist name and album, and has correct tags and everything has the same structure :) 20.54.47 # ouch! 17GB 20.56.35 # heh 20.56.40 # a subset of my mp3s :) 20.56.56 # 94 gb 20.57.49 # :-O 20.58.25 # Do you just rip every song you ever hear ;) 20.58.48 # i have a lot of cds :/ 20.58.59 # about 900 20.59.07 # :-o 20.59.14 # excuse me whilst I pass out 21.00.05 Quit thu (Connection timed out) 21.01.03 Join thu [0] (~thu@h24-87-64-169.vc.shawcable.net) 21.14.09 Quit Snorlax (Read error: 104 (Connection reset by peer)) 21.20.04 # am I doing something wrong cause I haven't been able to compile since plugin support was added 21.20.25 # make[2]: Leaving directory `/home/rockbox/apps/plugins' 21.20.25 # make[1]: *** [rocks] Error 2 21.20.25 # make[1]: Leaving directory `/home/rockbox/apps' 21.20.25 DBUG Enqueued KICK REBELinBLUE 21.20.25 # make: *** [apps] Error 2 21.22.40 # ha 21.22.49 # what firmware u use to play per cd 21.22.53 # or album 21.23.01 # ? 21.23.13 # nvm 21.23.26 # I just downloaded the latest daily build but can't compile :( 21.24.26 # why? 21.25.05 # wats the prob? 21.25.36 # http://ipfm.dyndns.org/error.txt 21.25.40 # thats what I get 21.25.59 # u have an fm recorder? 21.26.04 # yep 21.26.19 # i have recorder 21.26.27 # i have the latest daily build 21.26.38 # thats werid though 21.26.38 # REBELinBLUE: its not the prettiest, but it works 21.26.50 # whats not the prettiest 21.26.51 # have I missed something out, have the build instructions changed 21.27.09 # byew 21.27.15 Quit Neo ("Client exiting") 21.27.25 # what it does 21.27.31 # is it sorts by filetype 21.27.40 # K 21.30.47 # blah 21.30.54 # i need Z or Linus or somebody 21.30.56 # =/ 21.34.34 Join [IDC]Dragon [0] (~idc-drago@p50861FB8.dip.t-dialin.net) 21.34.53 # ah 21.34.54 # [iDC] 21.35.01 # you can ignore that mail I sent you, I found the problem 21.35.09 # <[IDC]Dragon> I just sent you email. 21.35.22 # <[IDC]Dragon> What was it? 21.35.31 # I had an instruction implemented wrong 21.35.44 # one that the Archos fw obviously doesn't use to its full potential 21.36.07 # I also was missing the implementation for 3 instructions, one of which is used by Rombox startup, zero of which are used by Archos startup 21.36.08 # :D 21.36.13 # <[IDC]Dragon> Compiles usually don't leave the beaten path. 21.36.19 # <[IDC]Dragon> Compilers 21.36.56 # <[IDC]Dragon> What exotic intructions are there? 21.37.16 # has anyone heard of anyone else who hasn't been able to compile from source since plugins were added? 21.37.22 # am I doing something wrong? 21.37.24 # uhm 21.37.28 # mov #imm:8, rn 21.37.42 # <[IDC]Dragon> where is that? 21.38.19 # loads a constant value into Rn (the value is the lower 8 bits of the instruction code) 21.38.41 # Archos actually used it, it just didn't use it to its full potential 21.38.51 # i failed to realize that the value is supposed to be sign-extended 21.38.58 # so when gcc did 21.39.03 # mov #0xFC, r5 21.39.18 # and used r5 (which should be 0xFFFFFFFC after that instruction) as a bitmask 21.39.34 # <[IDC]Dragon> Yes, I found that confusing in the disassemblies, too. 21.39.35 # i kinda lost the upper 24 bits 21.39.42 # Oh I'm a bloody idiot. I haven't reinstalled Perl thats why I can't compile! 21.39.49 # one of the instructions I didn't implement was 21.39.53 # lds @rm+, PR 21.39.59 # <[IDC]Dragon> I'ts quite often used for decrementing. 21.40.04 # which is used in thread switches 21.40.13 # [IDC]Dragon: yah, add #0xff, r1 21.40.30 # <[IDC]Dragon> I was using a Lauterbach emulator, it also had problems with it. 21.40.32 # I believe the archos fw doesn't use threads, at least not to the extent we do 21.41.04 # <[IDC]Dragon> I had to patch a certain piece of code to fix that. 21.41.15 # heh 21.41.18 # sounds like fun =/ 21.41.44 # <[IDC]Dragon> Patching the SH code, with something equivalent, I mean. 21.41.51 # oh 21.41.58 # i thought you meant you patched the emulator 21.42.03 # which reminds me 21.42.09 # GCC is producing some VERY strange code 21.42.27 # <[IDC]Dragon> But much better than the one Archos was using. 21.42.28 # in sleep() 21.42.41 # I dunno, this one's fscked up 21.42.46 # in sleep() 21.42.59 # after executing the SLEEP instruction 21.43.01 # it does this: 21.43.11 # if (++next >= num_threads) 21.43.12 # next = 0; 21.43.59 # the assembly used to implement this goes like this: 21.44.21 # r7 = &next 21.44.28 # r1 = &num_threads 21.44.40 # r2 = next [r2 = *r7] 21.44.56 # r1 = num_threads [r1 = *r1] 21.45.14 # r3 = next+1 [r2+1] 21.45.38 # cmp/hi r3, r1 [next+1 >= num_threads?] 21.45.57 # at this point, if next+1 >= num_threads, T=1; otherwise T=0 21.46.08 # this is where things get strange 21.46.26 # movt r1 [r1=T] 21.46.51 # <[IDC]Dragon> I'm too tired to follow this, if you don't mind. 21.47.00 # meh, ok 21.47.10 # it just generates some VERY bizarre code 21.47.36 # <[IDC]Dragon> As long as it works... 21.47.55 Quit REBELinBLUE () 21.48.24 # <[IDC]Dragon> Excuse me for a while 21.48.29 # mkay 21.48.34 Nick [IDC]Dragon is now known as [IDC]Dragon|away (~idc-drago@p50861FB8.dip.t-dialin.net) 21.55.50 Join matsl [0] (~matsl@as13-4-5.mal.s.bonet.se) 21.56.56 *** Saving seen data "./dancer.seen" 22.00.02 Part f0xShot 22.00.07 Join groovingandi [0] (~groovinga@proxy-out.lrz-muenchen.de) 22.02.05 Part groovingandi 22.08.00 # anyone here? 22.08.27 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 22.08.27 # * Stevie[FP] throws stuff at everyone 22.08.50 Join Guest57 [0] (~jirc@AMetz-101-1-4-188.w80-11.abo.wanadoo.fr) 22.08.54 # * MT ducks 22.09.02 # mt! 22.09.09 # do you have a Recorder? 22.09.14 # fm sorry :/ 22.09.17 # damn 22.14.26 # hi all 22.14.48 # is there some news about the flashable firmware for the FM Jukebox 22.16.04 # yeah 22.16.09 # the news is you can't do it yet 22.16.17 # ok 22.16.50 Join Zagor [242] (bjst@as9-5-6.k.s.bonet.se) 22.17.09 # hi guys 22.17.40 # it seems that the "crazy" people who try it report the same effect that did appears with the first FM firmware : the shutdown problem cause of the diffence in the voltage level .. so I think it will be resolve .... :) 22.17.58 # isnt it ? 22.18.02 # sup Z 22.19.15 # see u later . 22.19.18 Quit Guest57 ("Leaving") 22.22.53 # i'm pondering if we should rolo at all after flash start. i'm don't think we should. 22.23.53 # I'm in favor of it... 22.24.02 # <_aLF> and as a option ? 22.24.17 # mostly cuz I figure the best plan of attack is to have a simple boot-loader 22.24.44 # a known-working-version 22.25.10 # we have to spin the damn drive up anyway 22.25.25 # Hell, we even have to grab the contents of the root dir anyway 22.25.35 # we should be able to check for an ajz file for free 22.25.46 # my thinking is this: when you run flash, you most likely flash the version you want. thus rolo:ing is pointless and you tend to remove ajbrec.ajz to avoid it. but then you are out of luck if the flash version bugs, and you F1-boot into archos. no ajbrec.ajz means no rockbox and no chance to burn a new image without connecting to a pc. 22.26.29 # now 22.26.38 # right 22.26.55 Nick [IDC]Dragon|away is now known as [IDC]Dragon (~idc-drago@p50861FB8.dip.t-dialin.net) 22.27.03 # I would recommend that the flash plugin auto-rename any /ajbrec.ajz 22.27.37 # that still leaves us in the cold (as in archos firmware) on f1-boot 22.27.43 # to like ajbold-071003162600.ajz 22.27.52 # ooh 22.27.58 # how about this? 22.28.12 # put some sort of unique signature in the file 22.28.21 # <[IDC]Dragon> Hi Zagor, yes, I'm close to take that auto-startup out again. 22.28.24 # like, say, the current date/time in some form when the image is built 22.29.02 # Stevie[FP]: but my point is we only want to rolo-on-boot if we boot the archos firmware, and that firmware only looks for ajbrec.ajz 22.29.21 # <[IDC]Dragon> takes an extra second because it has to read the root dir or so 22.29.23 # dragon: ok. now you know I agree with it :-) 22.29.59 # I suppose it wouldn't be unreasonable to expect the atypical user to manually ROLO the ajz file 22.30.12 # precisely 22.30.13 # <[IDC]Dragon> Renaming to ajbrec.ajz_ resolves that both would rolo. 22.30.15 # [IDC]Dragon: we have to read the root dir anyway, for the directory tree 22.30.32 # <[IDC]Dragon> Even when resuming straight away? 22.30.42 # I thought so 22.30.53 # hell 22.30.57 # <[IDC]Dragon> I don't, why is is quicker without? 22.31.01 # yes we do 22.31.13 # because we need to scan the root dir for the damn playlist file 22.31.17 # <[IDC]Dragon> Zagor, please be our judge... 22.31.47 # we resume before loading root 22.31.54 # <[IDC]Dragon> Aha! 22.32.01 # the resume info is stored in the config block 22.32.03 # but don't we need to scan the root dir for the playlist file? 22.32.06 Join Neo [0] (~Neo@209.187.167.213) 22.32.11 # hey all 22.32.25 # Stevie[FP]: yes, to load the playlist file 22.32.34 # or even to find the mp3 we wish to play 22.32.42 # hows that rombox commin 22.32.46 # but resuming still means one less dir scan 22.33.07 # stil workin on it? 22.33.16 # <[IDC]Dragon> I think it doesn't store the filename and position, just a disk sector # or so. 22.33.17 # however the root dir scan is very fast. most of the rolo time is descrambling 22.33.34 # dragon: no actually it's filename and position 22.33.40 # <[IDC]Dragon> No, I menat just the check for a non-present file. 22.33.44 Quit Neo (Client Quit) 22.34.01 # <[IDC]Dragon> Maybe my root is too large, with hundreds of directories. 22.34.27 # yes, that will take some time. my root is ~30 entries 22.34.29 # which function scans a dir for a filename? 22.34.37 # Stevie[FP]: open() 22.35.00 # wheres that defined? 22.35.08 # firmware/common/file.c 22.35.33 # ah 22.35.40 # so actually opendir does... 22.35.44 # or readdir 22.36.16 # well, readdir returns one entry per call. open is the one that looks for a particular entry. 22.36.25 # ok 22.36.27 # fat_getnext 22.36.35 # yes 22.36.43 # actually scans for filenames... 22.36.50 # * Stevie[FP] thinks of a more optimized version 22.37.01 # we could scan faster with a specialized fat_search function 22.37.14 # not without caching a lot 22.37.25 # no, this is what i'm thinking of 22.37.53 # err, i can't find fat_getnext 22.38.07 # oh 22.38.10 # fat.c is under drivers 22.38.13 # yes 22.38.46 # what we do is 22.38.50 # read the whole damn dir 22.38.57 # entry by entry 22.39.03 # looking for the name we desire, correct? 22.39.34 # fat_getnext needs to do this: 22.39.34 # yes 22.39.37 # (1) fetch a directory entry 22.39.48 Join REBELinBLUE [0] (trilluser@modem-817.aardvark.dialup.pol.co.uk) 22.40.10 # (2) if this is an LFN entry, prepend this data to our LFN buffer 22.40.26 # (3) if this is not the last LFN entry, goto step 1 22.41.18 # this requires a huge cache. dirs can be Really Long 22.41.31 # i see the sectorcache thing 22.41.38 # that's what you're talkign about, right? 22.42.03 # no, i mean reading "the whole damn dir" 22.42.14 # maybe i'm misunderstanding? 22.42.18 # but we already do that 22.42.46 Join cst [0] (~jens@pD9E7F2B9.dip.t-dialin.net) 22.43.20 # file.c line 120, for the 7/09 daily 22.43.26 # no, we only cache max three sectors 22.43.50 # ok, apparently we are talking about different things :) 22.44.09 # ok, back to where I was 22.44.24 # <_aLF> when ajbrec.ajz is created ? only in usb mode ? 22.44.33 Join SillyFly [0] (~chatzilla@212.199.220.239.forward.012.net.il) 22.44.50 # (4) if it is the last LFN entry, we fetch the next FAT direntry for the file attributes and stuff 22.44.54 # _aLF: it's never created, you copy it to the disk 22.45.14 # <_aLF> why not store in cmos after usb mode, if .ajz is here 22.45.22 # cmos? 22.45.26 # wtf? 22.45.40 # <_aLF> sorry, where config block is store 22.45.40 # when did we become a motherboard? 22.45.44 # _aLF: what are you trying to achieve? 22.45.58 # anyway 22.46.00 # Stevie[FP]: well, the rtc ram is sort of cmos ram... 22.46.05 # (5) we stuff all the relevant data into a fat_direntry and return it to the user 22.46.08 # <_aLF> yes rtc ram 22.46.27 Quit msoultan () 22.46.29 # I believe that's how fat_getnext operates 22.46.41 # hi. I'm having trouble compiling gcc with target=sh-elf on linux. anybody care to try and help me? 22.46.41 # yes it is 22.46.44 # okay 22.46.46 # <_aLF> -> when we boot, rombox check if .ajz is here with rtc 22.46.50 # that's perfectly fine for browsing dirs 22.46.51 # <_aLF> not with fat 22.46.54 # <_aLF> access 22.46.57 # cuz we need to get all the filenames anyway 22.46.58 # SillyFly: are you using the versions we suggest? 22.47.12 # but for things like the auto-ROLO 22.47.25 # and when we're playing from a playlist 22.47.28 # _aLF: as I said, checking the disk is not the slow part. actually roloing the file is. 22.47.39 # we don't care about any files other than the one we want 22.47.56 # <_aLF> Zagor> ok 22.47.56 # Zagor: no. newer versions. I suspect I'm missing some header files, but dunno which.... 22.48.05 # in fact, we don't even care about the filename of the file we want, we just want to get the data for that file 22.48.16 # * Stevie[FP] ponders 22.48.49 # <[IDC]Dragon> Thats's how resume works, stores the disk position, right? 22.48.49 # SillyFly: there are problems with binutils in the newer versions. i recommend simply using the specified versions unless you feel like debugging the tools. 22.49.12 # dragon: no, resume stores the filename and byte offset 22.49.15 # oh. ok. 10x. 22.49.40 # [IDC]Dragon: it couldn't work -- what if the disk was defragged in usb mode? 22.49.49 # <[IDC]Dragon> Filename? Isn't that a bit wasteful? what size can it have? 22.49.58 # 260 bytes 22.50.08 # <[IDC]Dragon> In rtc ram? 22.50.09 # it's large, but it's The Right Way 22.50.17 # no, config block on disk 22.50.24 # <[IDC]Dragon> Ah. 22.50.57 # <[IDC]Dragon> Then we ave no space problenm. 22.50.58 # 13 22.51.48 # 17 22.53.49 Quit cst ("Wechsle Server") 22.54.23 Join cst [0] (~jens@pD9E7F2B9.dip.t-dialin.net) 22.59.08 # <[IDC]Dragon> Zagor: thanks again for fixing ata::init(), that really did it for the people. 23.00.45 # <[IDC]Dragon> (not listening to take credits) 23.03.32 Join tpelliott [0] (telliott@208.251.255.120) 23.05.33 Join joshn [0] (joshn@204.251.225.99) 23.06.18 # dragon: the pleasure was all mine. (it did it for me too... :-) 23.06.22 # what's this dir->entrycount thing? 23.06.51 # <[IDC]Dragon> Zagor: are you using Rockbox in flash now? 23.07.06 # i thought it was a cached copy of the # of files in the dir, but it gets reset to 0 when we get the end-of-dir 23.07.34 # dragon: yes 23.07.48 # Stevie[FP]: it's how many entries this file is using 23.07.56 # oh 23.07.59 # who uses that? 23.08.13 # well 23.08.15 # <[IDC]Dragon> Zagor: Then it's not exactly a reference platform for Rockbox development any more. 23.08.19 # fat_open references it 23.08.23 # but I don't understand what it uses it for 23.08.54 Join hardeep [0] (1098@208.247.65.237) 23.08.58 # Stevie[FP]: write_long_name uses it 23.09.08 # I'm successfully running Rombox also. I wouldn't mind a version that dosen't check for firmware on hard drive. 23.09.30 # dragon: true, but that's where the beauty of F1-ON comes in 23.09.33 # err 23.09.38 # where? 23.09.44 # <[IDC]Dragon> tp: I will do that. 23.10.11 # oic 23.10.16 # <[IDC]Dragon> YOu can rename it for the time being, so that only Archos finds it. 23.10.46 # or is that the 'numentries' thing? 23.11.02 # Stevie[FP]: a simpler example is fat_remove() 23.11.15 # oh i see 23.11.23 Quit cst ("Demo-Zeitüberschreitung") 23.11.42 # <[IDC]Dragon> tpelliott, you read that? 23.12.09 # When will Rombox make a splash on the Rockbox home page? It's one of the coolest features yet. 23.12.15 Join cst [0] (~jens@pD9E7F2B9.dip.t-dialin.net) 23.12.30 # does this include the shortname? so a filename with 1 LFN entry (usually happens when changing the case of a name) has an entrycount of 2? 23.13.04 # Stevie[FP]: yes, if my memory is correct 23.13.42 # <[IDC]Dragon> Zagor: how about F3-On starting gdb right away? 23.13.59 # <[IDC]Dragon> (Or F2-On) 23.14.32 # dragon: nah, too few people have the serial mod to make it worthwile 23.15.10 # we'd probably just get bug reports from confused users trying it :) 23.15.43 # <[IDC]Dragon> My autoring tool is prepared for n images, but not yet the bootloader and the update plugin. 23.16.52 # <[IDC]Dragon> When I get my 512k flash chip, I wouldn't know how to fill it. 23.17.07 # <[IDC]Dragon> (Compression did work too well) 23.17.32 # hehe 23.17.43 # we can have a boot animation :) 23.18.03 # <[IDC]Dragon> Yeah, while waiting for the disk. 23.18.26 # <[IDC]Dragon> And we could play a jingle. 23.18.30 # haha 23.18.42 # that would probably get boring fast... 23.18.50 # <[IDC]Dragon> How about resuming from flash? 23.19.11 # storing resume info in flash? 23.19.25 # <[IDC]Dragon> No, storing the MPEG buffer. 23.19.37 # <[IDC]Dragon> ;-) 23.19.42 # ouch 23.20.25 # <[IDC]Dragon> On another subjject: I'd like to check in my sources. 23.20.47 # <[IDC]Dragon> How do you like that organized? 23.20.52 # anyone know why I can't compile, ever since plugin support was added I get this output http://ipfm.dyndns.org/error.txtt 23.20.58 # *http://ipfm.dyndns.org/error.txt 23.21.32 # dragon: could you send me a tarball so I can have a look? 23.22.03 # <[IDC]Dragon> For me Windows user, this would be a zip file. 23.22.05 # REBELinBLUE: we need more from the build log 23.22.12 # dragon: sure, no problem 23.22.36 # OK Lets me try again and I'll post the whole thing 23.24.06 # <[IDC]Dragon> Generally peaking, I have the 2 plugins, the bootloader, an authoring tool, my "minimon" (getting injected for UART boot), RockFlash being the PC application that talkes to it (and so can flash, dump. upload, execute, etc.) 23.26.27 # <[IDC]Dragon> Probably you don't want all that in the standard source tarball. 23.27.13 # windows start sound :) 23.27.52 # <[IDC]Dragon> For the plugins, I don't know if both should be in the standard set, and then there's the question on where/how to keep that firmware image being used by the first. 23.27.54 # dragon: actually, i probably do. i just need to come up with a good way to integrate it 23.28.20 # <[IDC]Dragon> You do what? 23.28.31 # want it all in the standard source 23.28.54 # <[IDC]Dragon> UART boot is rather exotic, like gdb. 23.29.07 # <[IDC]Dragon> Authoring probably too. 23.29.22 # yes, but gdb is in the standard source 23.29.34 # <[IDC]Dragon> Ah, i see. 23.29.42 # it's much simpler, maintenance wise, to have it all in one package 23.29.57 # <[IDC]Dragon> Dangerous, powerful toys. 23.30.38 # yes. we'll simply write big notes saying "don't play with things you don't understand" 23.31.06 # <[IDC]Dragon> As long as there's people out there who force recorder images into an FM... 23.31.18 # http://ipfm.dyndns.org/error.txt there you go, the complete log 23.31.42 # <[IDC]Dragon> I was pretty upset about that. 23.31.57 # dragon: yes, but we will never be able to stop those kinds of people. 23.32.20 # <[IDC]Dragon> Is there a way to tell recorder/FM apart at runtime? 23.32.34 # <[IDC]Dragon> (Have asked that before, I know) 23.32.43 # what we can do is provide enough warnings to avoid mistakes. people who actually want to ruin their box cannot be prevented. 23.32.56 # um, we could easily add that 23.33.02 # <[IDC]Dragon> How? 23.33.20 # err 23.33.23 # * Stevie[FP] doesn't get this 23.33.28 # well the binary is compiled for the specific target, so we could just do it with #ifdefs 23.33.36 # i have the root directory cluster in the fat 'superblock' 23.33.42 # anyone? it seems to build the firmware fine, its then when it gets on to the plugins 23.33.45 # but 23.34.02 # after the first cluster 23.34.08 # <[IDC]Dragon> I don't want 3 targets for the bootloader, maintanance-wise as you say 23.34.10 # how do I know what the next cluster is? 23.34.34 # the only page i could find on fat32 only talks about the directory entries 23.34.37 # and other structures 23.34.54 # dragon: oh, you want to know in the boot loader 23.35.04 # bah, i disconnected just as dragon answered my question :/ 23.35.16 # MT: check the log 23.35.25 # <[IDC]Dragon> what question? 23.35.42 # cunning 23.35.56 # REBELinBLUE: i can't see what that error is about. everything seems to be going fine. 23.36.13 # hmm 23.36.21 # [IDC]Dragon: you want to prevent people from flashing the wrong thing, right? 23.36.24 # REBELinBLUE: you do get an ajbrec.ajz and all the .rocks, right? 23.36.30 # :| It doesn't really matter, because as I said the firmware compiles fine, its the plugins which don't 23.36.42 # how many .rock files should there be/ 23.36.55 # <[IDC]Dragon> That, and I want the bootloader to know how to check for F1. 23.37.01 # oh, i actually disconnected before i asked the question, you just happened to be talking about the same subject when i reconnected :) 23.37.03 # I have 14, totaling 57.1k 23.37.11 # dragon: just so i understand, to develop/fix problems with rom flash for fm recorders, i would require serial mod and UART boot yes? 23.37.26 # [IDC]Dragon: just have 3 diff versions 23.37.43 # REBELinBLUE: yup, that's all 23.37.51 # I did notice one thing just now. If I turn on my Archos with the USB plugged in, it hangs at "loading". It starts USB fine if I turn it on before plugging in the USB. 23.37.52 # <[IDC]Dragon> MT: No, you don't. I maybe will. 23.37.55 # we do it for rockbox, it won't be all that terrible for the bootloader 23.38.19 # weird :| It compiles fine I just get an error :D 23.38.24 # REBELinBLUE: i did your patch, but its crappy, and im not happy with it, if you check http://mt.staff.impulsed.net/rockbox/ tomorrow, ill hopefully have done a version im happy with by then 23.38.27 # REBELinBLUE: yes, very strange 23.38.32 # otherwise i'll upload the crappy one 23.38.35 # ah well as long as the firmware compiles :D 23.38.37 # REBELinBLUE: have you tried it? everything works? 23.38.44 # <[IDC]Dragon> Stevie: It's just an overkill, and when authoring the firmware file I have to be very careful to pick the right one. 23.38.54 # cool thanks :D I was just about to try and make it myself 23.39.04 # [IDC]Dragon: what do you mean by 'authoring the firmware file'? 23.39.28 # ah, actually 23.39.35 # i think if i change a -1 to 1 23.39.35 # dragon: we need to make a new plugin that creates the initial firmware file from the existing rom 23.39.38 # REBELinBLUE: have you tried it? everything works? -- seems to work fine 23.40.05 # [IDC]Dragon: that was something I didn't understand, why not use the image in ROM 23.40.09 # <[IDC]Dragon> Well, I composed that large firmware_rec.bin file from the bootloader and the 2 images. 23.40.16 # that's the only way I can think of to avoid voilating archos' copyright 23.40.24 # yes 23.40.27 # thats got it :) 23.40.28 # besides, we know for sure that the image in ROM works with the given HW 23.40.38 # <[IDC]Dragon> Stevie: I need to compress it to make room for Rockbox. 23.40.45 # otherwise it wouldn't have passed Archos's stringent QA...err 23.41.04 # <[IDC]Dragon> Zagor: well, we can do that. 23.41.17 # sounds like i need to fix that bigmem api... :-) 23.41.26 # hey Zagor... 23.41.27 # <[IDC]Dragon> Is it broken? 23.41.47 # no, it just doesn't exist yet :) 23.41.51 # lol 23.42.03 # <[IDC]Dragon> We don't necessarily need to do all that on the box. 23.42.04 Join CS1 [0] (~jirc@adsl-64-160-22-54.dsl.lsan03.pacbell.net) 23.42.09 # while you're at it, I think we oughta throw in a new plugin API routine to determine what we're running on - player, recorder, or fm 23.42.27 # <[IDC]Dragon> I thought that's the first check. 23.42.37 # Stevie[FP]: i though about that too, but... why? 23.42.55 # then the rombox plugin that flashes the board can make sure that the image they're flashing is correct 23.42.58 # <[IDC]Dragon> But then I wonder how that guy ran the plugin on an FM. 23.43.01 # aaaaaaaand 23.43.02 # oooh 23.43.04 # [IDC]Dragon: here it comes 23.43.09 # here it comes >:) 23.43.16 # when flashing the bootloader 23.43.17 # dragon: good question indeed 23.43.23 # have a special reserved byte 23.43.25 Quit cst ("Demo-Zeitüberschreitung") 23.43.38 # i thought recorder and fm recorder were considered the same for plugins 23.43.39 # and set that byte value to indicate the firmware type 23.43.51 # so recorder plugins would work fine on fm and vice versa 23.43.52 # err hardawre type (fm/recorder) 23.44.13 # then your bootloader doesn't need to detect -- it knows 23.44.14 # hardeep: ah, yes they are 23.44.25 # <[IDC]Dragon> Stevie: OK, but this requires a correct run in the first place. 23.44.37 Quit _aLF ("bye") 23.44.45 # [IDC]Dragon: you mean a correct copy of rockbox (fm or rec)? 23.45.15 # <[IDC]Dragon> Yes, or runnig the correct plugin. 23.45.18 # o~REBELinBLUE: http://mt.staff.impulsed.net/rockbox/rebelinblue.m3u-first.patch.diff 23.45.22 # what do you mean, correct plugin? 23.45.28 # its very ugly, very inefficient, but it does what you wanted 23.45.38 # why do you need multiple plugins? 23.46.13 # ah thanks :D 23.46.16 # <[IDC]Dragon> One for each platform. 23.46.29 # I figured that was what you meant by multiple plugins 23.46.32 # but that doesn't answer why 23.46.35 # <[IDC]Dragon> I thought they don't ru cross-platform. 23.46.42 # <[IDC]Dragon> don't run 23.46.47 # I really don't see any reason why they couldn't 23.46.50 # they all have the same cpu 23.47.04 # <[IDC]Dragon> The "mandatory" first call is a check 23.47.18 # hm? 23.47.27 # <[IDC]Dragon> But not the the same hardware. 23.47.43 # who makes this first call? [keep in mind: I know almost zilch about the plugin system] 23.47.59 # yes but I don't think Sokaban cares which ADC register your F1 key is on 23.48.11 # <[IDC]Dragon> The plugin calls TEST_PLUGIN_API(api); 23.48.26 # looks like a macro 23.48.37 # mm, excuse me for being dense, but surely just stick a is_fm() function into the api 23.48.47 # or define FM when compiling 23.49.12 # MT: the latter would not work for separately compiled .rocks 23.49.22 # <[IDC]Dragon> Compiling so won't keep people from running it on another platform. 23.49.55 # huh? 23.50.14 # [IDC]Dragon: I would imagine most plugins to be games 23.50.36 # in which case the HW really is the same on both FM and recorder 23.50.49 # they have the same buttons and the same display 23.51.18 # likewise, they [usually] have the same ROM chip 23.51.30 # Batteries and voltage is different. 23.51.30 # MT thanks it works :D 23.51.37 # <[IDC]Dragon> the macro expands to a function which compares API version and model. 23.51.48 # tpelliott: why the hell would a game care about the battery type? 23.52.05 # where did Z go 23.52.13 # this doesn't sound right 23.52.20 # <[IDC]Dragon> maybe there will be a radio plugin ;-) 23.52.23 # i did it this way because the api for fm and recorder is identical 23.52.24 # True. I thaught you were talking about Rombox. 23.52.33 # [IDC]Dragon: so? 23.52.36 # thus I saw no reason to keep them separated 23.52.38 # [IDC]Dragon: who cares? 23.53.14 # Zagor: is it true that a .rocks, once built, can only be run on a certain model (fm or recorder)? 23.53.48 # <[IDC]Dragon> Well, at least I use the build config to make a suffix for the hard coded filename. The"_rec" of firmware_rec.bin". 23.55.49 # ok... 23.56.01 # imho, the Right Way To Do It is this: 23.56.16 # Stevie[FP]: there is no difference btwn fm and rec. only btwn recorders and players. 23.56.28 # Zagor: as IDC points out, FM has a radio 23.56.34 # yes, but the api doesn't 23.56.53 # and i'm not sure it ever will 23.56.58 # Zagor: here's the idea 23.57.00 *** Saving seen data "./dancer.seen" 23.57.12 # rombox bootloader needs a way to determine which model it's on 23.57.23 # so it knows which key is ON, and which key is F1 23.57.27 # (they have different ADCs) 23.57.44 # now, afaik there's no trivial way to detect this 23.57.55 # other than by flashing the Recorder image and seeing if it doesn't boot 23.57.55 # Does the digital; i/o still work the same on the FM? Can it send digital to a reciever's Toslink connection? I've heard conflicting reports. 23.58.40 # the proper way, imho, is to tell users "don't flash the wrong image". this works for all hardware makers, i don't see why it can't work for us.