--- Log for 27.05.103 Server: calvino.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 13 days and 2 hours ago 00.21.59 Join [IDC]Dragon [0] (jirc@p50861DD8.dip.t-dialin.net) 00.27.24 Quit _aLF ("bye") 00.33.58 Quit [IDC]Dragon ("Leaving") 00.39.44 Quit dw|gone (Read error: 110 (Connection timed out)) 01.14.20 Join tracktheripper [0] (jirc@ACB9A4AB.ipt.aol.com) 01.16.07 # heya 01.49.49 *** Saving seen data "./dancer.seen" 02.34.06 Join dw|gone [0] (dwihno@193.180.246.67) 02.34.07 Quit tracktheripper (Read error: 104 (Connection reset by peer)) 03.17.18 Join jzoss [0] (~jzoss@cs6711159-222.satx.rr.com) 03.37.25 Quit jzoss (Remote closed the connection) 03.49.53 *** Saving seen data "./dancer.seen" 03.53.39 Quit earHurts (Remote closed the connection) 04.58.58 Join earHurts [0] (~zic@pool-138-88-176-29.res.east.verizon.net) 05.00.27 # somebody refresh nmy memory - should a recorder .ajz boot and run on an fm archos? 05.11.38 Join Stevie-O [0] (whatsit2u@user-2inilsg.dialup.mindspring.com) 05.21.03 # earHurts: no, the scramble code is a little different 05.22.43 # actually, i take that back, the scramble is the same... there are other differences though which will result in it not booting 05.24.24 # I've got a user telling me my recorder build doesn't work, but I can't load it on my fm. 05.24.45 # i can try it, what's the url? 05.25.14 # www.diffenbach.org/rockbox/builds.html 05.25.55 # Has anyonne managed to run the simulator under cygwin? 05.26.14 # earHurts: yeah, it works pretty well in fact 05.26.34 # although i prefer the win32 simulator because of the msvc debugger 05.26.34 # does it require X? 05.27.02 # fie on ms! 05.27.12 # earHurts: yeah, but you can use xfree86 provided with cygwin 05.27.24 # hmm. 05.28.48 # hardeep, on the build, see what menu->general settings->file view->chop file prefix gives you. 05.29.32 # i get the tree menus you mention in your docs 05.29.36 # s/tree/three 05.30.20 # does the at/after work? 05.30.48 # the options are there... let me see if they work as expected 05.31.56 # yeah, looks like they're working 05.32.32 # you were able to select at or after? 05.32.44 # yeah, and they worked as documented 05.32.51 Join OneCluedCoder [0] (whatsit2u@user-2inimnf.dialup.mindspring.com) 05.33.21 # ok, if you now set chop to no, do your file manes dispaly normally? 05.33.34 # yep 05.33.52 # hnmmn. Thanks. 05.34.20 # This is contrary to Michael O'Quinn's report 05.34.42 # only thing to note is that my settings had just been reset so the config block was fresh 05.34.57 # maybe he had some bad settings laying around due to other patches 05.35.19 # perhaps. 05.35.40 # bnut he was using my build, which only has nmy patches. 05.36.09 # yeah, but he may have used a patched version before that updated the same config block areas 05.36.33 # which would've lingered around when he booted into yours 05.36.51 # possibly. 05.37.12 # again, thanks. 05.48.56 Quit Stevie-O (Read error: 110 (Connection timed out)) 05.49.54 *** Saving seen data "./dancer.seen" 06.18.58 # hardeep: you here? 06.29.36 # elinenbe: yep 06.44.39 # hardeep: any new news on the queue/insert function? 06.47.38 # just a couple of minor bugs and cleanup left to do 06.49.12 # you can try the latest at http://hardeeps.freeshell.org/dynamic.ajz 06.49.49 # diff: http://hardeeps.freeshell.org/patches/dynamic_playlist_13.diff 06.50.01 # I will... nice. 06.52.33 # hardeep? 06.57.37 # yes? 06.59.24 Quit earHurts (Remote closed the connection) 07.25.29 Join ken0_ [0] (marklar2@80.178.32.252.forward.012.net.il) 07.31.50 Quit hardeep ("[BX] Silly faggot! mIRC is for kids!") 07.49.58 *** Saving seen data "./dancer.seen" 08.22.07 Join sime [0] (~sime@modemcable032.39-131-66.nowhere.mc.videotron.ca) 08.22.13 # hi 08.22.54 # how can i create a playlist with a linux machin without music match? 08.25.07 Join matsl [0] (~matsl@as13-4-5.mal.s.bonet.se) 08.27.42 # sime... 08.28.20 # easiest way: find "target directory" -name *.mp3 > "playlistname.m3u" 08.28.54 # example, i have a Rock directory on my archos 08.28.59 # so i go to the root on the archos 08.29.00 # and 08.29.12 # find Rock/ -name *.mp3 > Rock.m3u 08.33.39 # adiamas: thx 08.40.19 Nick dw|gone is now known as dwihno (dwihno@193.180.246.67) 08.47.03 # np 08.48.28 # is there a 12 volt car adapter avalaible cheaper than the one that archos.com sells? 08.56.01 # anyone? 08.57.23 # the room tends to be a bit inactive around this time of night.. give it an hour or so 08.57.39 Quit dwihno ("rehash") 08.57.47 # ok then 08.58.15 Join dwihno [20] (dwihno@h193180246067.kommunicera.umea.se) 08.58.16 Quit dwihno (Client Quit) 08.58.29 Join dwihno [20] (dwihno@h193180246067.kommunicera.umea.se) 09.27.33 Join kuji [0] (~kuji@cuji.gotadsl.co.uk) 09.27.53 # logbot: seen linusn 09.28.03 # ogbot seen linusn 09.28.08 # logbot seen linusn 09.36.53 Join tracktheripper [0] (jirc@ACBF1F49.ipt.aol.com) 09.37.11 Part kuji 09.49.59 *** Saving seen data "./dancer.seen" 10.00.03 Quit tracktheripper ("Leaving") 10.26.22 Join Quelsaruk [20] (swordmaste@faerun.ugr.es) 10.33.19 Join pyvasene [0] (~pyvasene@62.4.7.1) 10.33.33 Quit pyvasene (Client Quit) 10.37.13 Join pyvasene [0] (~pyvasene@62.4.7.1) 10.38.20 Quit zamez ("Client exiting") 10.43.42 # is there a 12 volt car adapter avalaible cheaper than the one that archos.com sells? 10.44.31 # Check your local radio shack store :-) 10.47.42 # mornign dwihno :) 10.48.04 # *morning 10.48.51 # Hej hej 10.50.59 Quit ken0_ (Read error: 54 (Connection reset by peer)) 10.54.16 # rebooting 10.54.55 Quit Quelsaruk ("KVIrc 3.0.0-beta1 "Eve's Avatar"") 11.03.41 Join Quelsaruk [20] (~swordmast@faerun.ugr.es) 11.03.55 # re-hi 11.04.41 Nick Quelsaruk is now known as quel|out (~swordmast@faerun.ugr.es) 11.43.33 Join earHurts [0] (~zic@pool-138-88-72-98.res.east.verizon.net) 11.43.49 # anybody awake? 11.45.05 # heh 11.45.08 # unfortunately, me ;) 11.46.01 # know if anybnody's gotten the sim to build under cygwin? 11.50.00 *** Saving seen data "./dancer.seen" 12.01.43 # i tried before 12.02.00 # but i got an error 12.03.21 # rebooting 12.03.29 Quit quel|out ("Cerrando la cliente") 12.07.43 Join Quelsaruk [20] (swordmaste@faerun.ugr.es) 12.07.46 # re 12.17.17 #>> "seen" used by Quelsaruk (swordmaste@faerun.ugr.es) [snoop prevented] 12.17.34 # umm 12.17.42 # how was that nick 12.17.43 # :( 12.17.56 # heh 12.18.07 # logbot: seen lanhardrocker 12.18.25 # heh maybe not...:) 12.18.37 # is haar (hair in german or something like that 12.18.42 # is long haired rocker 12.18.53 # :) 12.18.55 # heh 12.20.05 Quit earHurts (Remote closed the connection) 12.28.31 Join zamez [0] (~james@jbursa.oriel.ox.ac.uk) 12.41.58 Join DJBaz [0] (~baz@modem-855.lion.dialup.pol.co.uk) 12.44.39 Quit DJBaz (Client Quit) 12.50.49 Join kuji [0] (~kuji@cuji.gotadsl.co.uk) 12.50.58 Part kuji 12.56.53 Quit elinenbe (" HydraIRC -> http://hydrairc.sf.net <- s0 d4Mn l33t |t'z 5c4rY!") 13.02.59 #>> "seen" used by Quelsaruk (swordmaste@faerun.ugr.es) [snoop prevented] 13.03.11 # :) 13.08.31 Join Snorlax [0] (Snorlax@h202n2fls34o883.telia.com) 13.17.26 Quit Snorlax () 13.23.29 Join Bagder [241] (~dast@neptunus.contactor.se) 13.23.43 # howdy ho 13.25.16 # hej Bagder :) 13.25.23 # ummm... 13.25.52 # mor da bra? (i have a really bad memory and even worse swedish) 13.26.08 # "mår du bra?" 13.26.10 Quit Jet8810 (Read error: 104 (Connection reset by peer)) 13.26.15 # yessir! 13.26.38 # mar du bra 13.26.39 # :) 13.26.42 # more or less... 13.26.47 # yeps 13.28.46 # btw, i've found doom for my mobile ;) 13.29.05 # hehe 13.29.09 # is it good? 13.29.29 Join DJBaz [0] (~baz@modem-855.lion.dialup.pol.co.uk) 13.29.43 # i haven't tested it yet 13.30.13 # (i have to create the bin file yet) 13.50.03 *** Saving seen data "./dancer.seen" 14.00.00 Quit Schnueff (calvino.freenode.net irc.freenode.net) 14.00.00 NSplit calvino.freenode.net irc.freenode.net 14.00.55 NHeal calvino.freenode.net irc.freenode.net 14.00.55 NJoin Schnueff [0] (mah@d096.stw.stud.uni-saarland.de) 14.09.28 Quit DJBaz ("Client exiting") 14.21.27 Join Quelsaruk_ [20] (swordmaste@faerun.ugr.es) 14.21.28 Quit Quelsaruk (Read error: 104 (Connection reset by peer)) 14.25.28 Nick Quelsaruk_ is now known as quel|out (swordmaste@faerun.ugr.es) 14.55.28 Join Zagor [242] (bjst@as9-5-6.k.s.bonet.se) 14.55.40 # welcome dr Z 14.55.42 # howdy 14.57.14 # Zagor: I got an URL for you... Sony has released some N.U.D.E (hah, NUDE!) headphones ;-) 14.57.20 # Zagor: http://se.pricerunner.com/sound-and-vision/sound/headphones/153212/details 14.58.00 # ex71? i wonder what's changed. 14.58.33 # Me too. 14.58.39 # Perhaps a better magnet? 14.59.24 # maybe we should slap kjell 14.59.31 # Bagder: ? 14.59.34 # look at his fd+fe usage 14.59.49 # in settings.c 14.59.57 # line 417 15.01.32 # gosh! 15.01.51 # I'll mail 15.01.55 # good 15.03.07 # before AA is free, isn't it? 15.03.54 # * dwihno warns Kjell of the upcoming spanking 15.04.04 # while looking in there, check line 689 15.04.07 # Public spanking humiliation att the next Snaxx ;D 15.04.11 # YES! 15.04.13 # hehe 15.05.20 # that conditional operator on line 689 is linus' idea. i don't like it, i prefer shifting and anding. 15.05.34 # yeah, but [0x29] must be wrong 15.05.47 # within the block it uses [0xae] 15.06.11 # if (config_block[0x29] != 0xae) { 15.06.11 # global_settings.fade_on_stop = config_block[0xae] & 1; 15.06.15 # global_settings.caption_backlight = (config_block[0xae] >> 1) & 1; 15.06.15 # } 15.08.16 # bug report 742131 pointed me on this 15.08.23 # looks very strange indeed 15.09.35 # the bug reports seems very accurate, I'll correct this 15.09.44 # Zagor: just to remind you. have you looked at the patch yet ;-) 15.09.58 # matsl: no :-) 15.10.08 # so many patches 15.10.23 # I talked to linus earlier today, he felt a bit overloaded with patches too 15.10.27 # yes 15.11.11 # I know. But on this one i have been handcuffed. not allowed to check it in. But I want to get rid of it. 15.11.41 # matsl: I know. i'm sorry for the delay, i'll look at it Real Soon Now 15.12.51 # Zagor: thanks. 15.14.04 Quit OneCluedCoder (Read error: 110 (Connection timed out)) 15.14.05 # we should organise a patch party some day 15.14.13 # yes 15.14.22 # bandaid! 15.14.36 # :-) 15.16.16 Join Stevie[FreedomPa [0] (~whatsit2u@65.114.136.196) 15.17.54 # Zagor: are you familiar how the idle powerdown stuff works? 15.18.11 # roughly 15.18.18 # does changing the time affect it? 15.18.32 # no 15.18.40 # ok 15.21.09 # howdy guys 15.22.08 # hi 15.24.24 # what's up 15.24.24 # ? 15.25.17 # we're complaining, mostly :) 15.25.26 # hehe 15.25.42 # hehe 15.26.53 # well does anyone know why the 8MB patch caps the buffer reads to 1mb? 15.27.26 Nick Stevie[FreedomPa is now known as Stevie[FP] (~whatsit2u@65.114.136.196) 15.27.27 # beats me 15.27.44 # it seems to limit the usefulness of having 8mb 15.27.51 # unless you're seeking backwards a lot 15.28.07 # that 1mb limit is not an absolute stop 15.28.14 # huh? 15.28.18 # it only means it'll start playing before swapping all the buffer 15.28.29 # iirc 15.28.30 # the code says 15.28.43 # amount_to_read = MIN(mp3buflen - mp3buf_write, amount_to_read) 15.28.46 # then, if MEM == 8 15.28.51 # i.e. 8mb 15.30.22 # I know 15.30.23 # amount_to_read = MIN(0x100000, amount_to_read) 15.30.31 # but it doesn't stop reading after that 15.30.39 # it is just a limit for this particular read 15.31.04 # since filling the whole buffer at once takes too long time on 8mb units 15.31.07 # btw 15.31.13 # * Stevie[FP] writes a patch for this 15.31.48 # further down you'll see that it'll post another message to itself and then it'll read again 15.32.47 # ok, i c 15.39.43 # our set date function is a bit silly 15.40.04 # I believe it get crazy when we read a very weird year 15.40.40 # I'll fix 15.41.18 # lol 15.41.40 # Bagder: is it possible to do a %02in in a custom WPS? :) 15.41.51 # I doubt it 15.42.06 # Boo! ;) 15.43.56 Join |nsomniac [0] (pussy@81-29-33-222.tau.hesby-radio.no) 15.46.39 # I got an idea regarding the module loader today. How about enabling runtime modules for different remote controller interfaces? 15.46.56 # hey bagder 15.47.02 # ? 15.47.06 # yes? 15.47.09 # New patch 15.47.24 # I noticed 15.47.31 # how'd you notice that fast? 15.47.38 # I subscribe to the list 15.47.48 # I get all changes to all trackers 15.47.50 # there's a list that gets emails when someone submits a patch? 15.47.53 # yes 15.47.55 # ah, ok 15.47.58 # actually I plan to patch it more effectively, but for now I think this will suffice 15.48.19 # hi 15.48.25 # hi mbr 15.48.26 # what I think would be best is to remember the USB attachment 15.48.41 # Bagder: seen my patch for time/date setting? 15.49.19 # and if we're still attached by the time we read another key, we return SYS_USB_CONNECTED again 15.49.22 # it fixes the messed rtc ram after power loss, also 15.49.55 # does it? do we always get 0xff then? 15.50.05 *** Saving seen data "./dancer.seen" 15.50.19 # I think so .. 15.50.19 # Any news about running Rockbox from ROM? 15.51.23 # dalnet needs a new routing team 15.51.32 # day and month is also beyond the valid range 15.52.02 # mbr: you could make the check if(timedate[3] > 30) {} 15.52.05 # just in case 15.52.20 # I think the registers are set to 0xff as the ram used for settings 15.52.51 # but the clock surely gets updated 15.53.17 # Thats why I used the year 15.53.25 # But yes, this may be a problem 15.54.25 # mbr: I think you should apply and commit that fix and now allow any year that is beyond 2030 15.54.31 # not allow 15.54.49 # OK 15.55.02 # oh, and then you can remove my silly fix for >2030 15.55.09 # And include a range check for all other values? 15.55.55 # I guess so, as otherwise the code won't be happy, like when we get 3-digit seconds or minutes 15.56.11 # Zagor: here? 15.57.21 # hey 15.57.59 # I reserve the right to experience life to the fullest, and that only happens at 137:254:80 PM 15.58.07 # ;) 15.59.05 # ah, that's why my life is so boring ;-) 15.59.16 # my clock bugs 15.59.25 # it wraps before the fun starts! 15.59.52 # ;) 16.00.03 # arent most RTC clocks BCD? 16.00.05 # gotta go home and clean my appartment 16.00.17 # another "showing" tonight 16.00.27 # * Bagder is about to sell it 16.00.32 # see, if the dorks at Hitachi had replaced some of their more useless CPU instructions with likes like AAA and AAS 16.00.37 # Bagder: I send another patch befor commit 16.01.04 # I think you can go ahead and commit, I have faith in you 16.01.08 # see ya 16.01.12 Quit Bagder ("Client Exiting") 16.08.58 # What's the jump scroll btw? 16.09.31 # i think it's something like setting 'scroll length' to the width of the screen 16.09.39 # not exactly, but close 16.09.50 # okay 16.10.07 # then I'm with ya' :) 16.10.14 # with me on what? 16.10.25 # I'm pretty sure it was written for players 16.10.40 # :-) 16.11.33 # dwihno: the jump scroll *jumps to the next 11 chars 16.11.35 # :) 16.11.46 # a player display has 11 chars AFAIK 16.11.56 # so, you see the first 11, then the next 11, and so on 16.11.59 # :) 16.12.03 # exactly 16.12.04 Nick quel|out is now known as quelsaruk (swordmaste@faerun.ugr.es) 16.12.22 # neato :-) 16.12.23 # muy bien 16.13.05 # something bugs me 16.13.14 # * quelsaruk is a docs guru :D 16.13.31 # my supposed '8mb autodetection' build crashes when loading a new .ajz file 16.14.07 # and I have no real way of finding out what exactly it's diong =/ 16.31.41 Nick dwihno is now known as dw|gone (dwihno@h193180246067.kommunicera.umea.se) 16.36.44 Join elinenbe [0] (~elinenbe@114.mujb.phil.philapaaz.dsl.att.net) 16.42.54 # who did the ROM dump? 16.47.45 Quit zamez ("Client exiting") 17.14.53 Nick Zagor is now known as Zagor|out (bjst@as9-5-6.k.s.bonet.se) 17.19.32 Join mecraw [0] (~mecraw@69.2.235.2) 17.33.37 Quit elinenbe (" HydraIRC -> http://hydrairc.sourceforge.net <- \o/") 17.50.09 *** Saving seen data "./dancer.seen" 17.54.40 Join hardeep [0] (1098@208.247.65.237) 17.55.23 Quit pyvasene ("Client exiting") 18.02.48 Join elinenbe [0] (~elinenbe@114.mujb.phil.philapaaz.dsl.att.net) 18.28.57 Quit sime ("miow") 18.29.22 Join Snorlax [0] (Snorlax@h202n2fls34o883.telia.com) 18.31.52 Join kuji [0] (~kuji@cuji.gotadsl.co.uk) 18.31.58 Part kuji 18.34.43 Quit elinenbe (" HydraIRC -> http://hydrairc.sf.net <- s0 d4Mn l33t |t'z 5c4rY!") 18.36.43 Quit Snorlax (Read error: 104 (Connection reset by peer)) 19.04.32 Join _aLF [0] (~Alexandre@AGrenoble-203-1-5-136.w80-14.abo.wanadoo.fr) 19.04.59 # <_aLF> hi 19.07.15 # anyone here with the red light dead issue? 19.07.35 # I had it the other day 19.08.04 # though not on a very recent build 19.08.28 # it's curious... 19.08.54 # i changed the HD on a friend's recorder 19.09.03 # and he's now experimenting that bug 19.09.22 # experiencing? 19.09.32 # umm 19.09.33 # yes 19.09.35 # :) 19.09.38 # he has it now 19.09.39 # btw 19.09.40 # :P 19.09.45 # do you know anyone with an 8mb rec? 19.09.54 # thebreaker 19.10.02 #>> "seen" used by quelsaruk (swordmaste@faerun.ugr.es) [snoop prevented] 19.10.18 # ok, forget about him ;) 19.10.23 # hahaha 19.11.06 # AFAIK he made the first mod, and those strange changes on source code to make that mod work :) 19.11.16 # ah ok :) 19.12.20 Quit matsl ("Client Exiting") 19.12.33 # did you see my mail to the list? 19.21.17 # which one? 19.21.18 # :) 19.22.49 # i made a patch to autodetect the RAM size 19.22.57 # instead of having to preconfigure it 19.25.35 # yupos 19.25.39 # i read that 19.25.45 # well the first one failed miserably 19.25.50 # now it works 19.25.50 # but I found the bug and made a new one 19.25.56 # i know 19.25.58 # ;) 19.26.09 # but I still need Joern to try it again 19.26.22 # since I don't have an 8MB on hand to test it myself :P 19.29.02 # too bad Archos doesn't have an offer where we can send them a Jukebox and some money, and they can replace the chips themselves 19.38.10 # * Stevie[FP] dreams of producing a feature so cool that it makes the 'News' list on the main page 19.38.55 # * Stevie[FP] is away [Ingesting sustenance (or at least going to eat some food)] [KS-MsgLog Off] 19.50.10 *** Saving seen data "./dancer.seen" 19.53.50 Join alexandre [0] (~alexandre@AGrenoble-203-1-3-5.w80-14.abo.wanadoo.fr) 19.54.20 Quit hardeep ("BitchX: Little. Yellow. Better.") 20.02.21 Join Jet8810 [0] (~Jet8810@adsl-80-9-55.mia.bellsouth.net) 20.07.40 Nick Zagor|out is now known as Zagor (bjst@as9-5-6.k.s.bonet.se) 20.13.07 Quit _aLF (Read error: 110 (Connection timed out)) 20.23.40 Join hardeep [0] (1098@208.247.65.237) 20.37.59 # * Stevie[FP] is back from [Ingesting sustenance (or at least going to eat some food)] [gone 59mins 4secs] [KS] 20.47.57 # hardeep: how's that dinamic queue going? 20.56.51 # who wrote the rtc alarm stuff? 20.57.05 # uwe 20.57.09 # uwe? 20.57.45 # uwe freese. he made an rtc mod for the old recorders, and thus wrote code for it. 20.58.00 # then it turned out the fm units come with his "mod" premade :-) 20.58.58 # the rtc alarm? 21.00.05 # yes. the old recorders don't have the electrical connection to wake up from rtc. 21.00.13 # so he made a mod for it 21.00.47 # oh, ok 21.01.33 # ok, get_sleep_timer() is in seconds 21.08.14 Join tracktheripper [0] (jirc@ACBB9180.ipt.aol.com) 21.08.30 # evening all 21.08.41 # uwe is thebreaker no? 21.08.43 # :) 21.08.49 # yes 21.09.04 # hi zaggor and quels 21.09.18 # hi track 21.09.27 # wots up? 21.09.27 # :D 21.10.40 # sorry Zagor 21.10.40 # :) 21.11.04 # ah, well thebreaker has apparently not been here for a while 21.11.09 # he also has the 8mb mod 21.11.23 # zag, did you see my email to the list? 21.12.09 # Stevie[FP]: yes 21.12.14 # watcha think? 21.12.20 # didn't look at the code though :-) 21.12.59 # adiamas: are you here? 21.13.03 # it's actually a simple concept that I discovered (but didn't quite understand) back in the 8088 real-mode days, before I understood how the memory addressing worked 21.14.01 # address pins that aren't connected to anything useful are effectively ignored 21.14.06 # so if you have a 2MB chip 21.14.31 # address P, 2MB+P, 4MB+P, 6MB+P, 8MB+P, 10MB+P, etc. are all equivalent 21.15.29 # so I pick a memory address P, write a known value to it, then write a different value at address P+2MB 21.15.39 # if the value at P changes, we have a 2MB chip 21.15.48 # if it doesn't change, we must have an 8MB chip 21.16.17 # i'd have expected a machine check exception... 21.16.47 # no, because the bus controller doesn't know 21.17.15 # if I remember right, the DRAM starts at 0x09000000 21.17.34 # yes 21.17.49 # anything from 0x09000000-0x09FFFFFF accesses the DRAM chip 21.18.52 # right, but what happens when there is no DTACK? 21.19.14 # I don't know what a DTACK is 21.19.30 # all I know is that, at least on the 2MB model, it works 21.19.57 # DTACK is Data Transfer Acknowledge 21.20.13 # I'm assuming that it works in a manner similar to the 128K chips on our old boards here (which, I'll grant you, are SRAM, not DRAM) 21.20.31 # i haven't read those parts of the data sheets much, maybe it doesn't apply to the sh7034 21.20.32 # the upper address pins are not connected 21.20.55 # ah, of course. i'm being silly. 21.21.13 # did you get someone to verify it on a 8MB yet? 21.21.14 # so the DRAM chip effectively access address modulo 2MB 21.21.17 # not yet 21.21.20 # the first version had a bug 21.21.54 # temporary brain failure 21.22.55 # I fixed it and uploaded a new version 21.24.58 # are there two rom chips? 21.25.50 # Zagor what does the grid of 0's mean in one debug menu option? 21.27.55 # which menu option? 21.28.02 # Stevie[FP]: no, just one 21.28.13 # tea time, brb 21.28.31 # ok 21.28.49 # then I do not understand why there are two ROM regions 21.28.58 # hang on zagor 21.29.05 # plus, there's something called v5.03, I don't know what that is either 21.30.42 # Zagor its Debug, View MAS regs and View MAS codecs 21.30.57 # I just wondered what the grid of 0s mean 21.32.25 # cu tomorrow 21.32.26 Quit quelsaruk ("KVIrc 3.0.0-beta1 "Eve's Avatar"") 21.33.58 # and what does Dump ROM contends do in the Debug menu? 21.34.44 # it creates 2 .bin files 21.34.51 # yea? 21.34.52 # I don't understand how this CPU even boots 21.34.55 # what do they do? 21.35.20 # they don't do anything 21.35.23 # they're .bin files 21.35.30 # i can open them in UltraEdit for a nice hex dump 21.35.46 # ohhh 21.36.01 # and what does the grid of 0's do in view MAS codecs 21.36.10 # damned if I know 21.36.17 # I think it's just that most of the values are 0 21.36.25 # I think it should display more than 4 lines at a time 21.36.31 # since my FM can show twice that 21.36.47 # i thought they switch between 1 and 0 to indicate the MAS is working during MP3 playback 21.37.40 # dunno 21.38.00 # well im sure Bjorn and co knoiw 21.47.25 # tracktheripper: those are just the current values in the specified registers. You can see what each register refers to in the MAS datasheets (http://rockbox.haxx.se/docs/datasheets.html) 21.48.20 # i don't get this 21.48.25 # wtf does the damn cpu do when it starts? 21.49.36 # the schematics don't match the HW manual 21.50.13 *** Saving seen data "./dancer.seen" 21.56.17 # cheers hardeep 21.57.52 Join ken0_ [0] (marklar2@80.178.37.138.forward.012.net.il) 22.02.22 # mehhh 22.02.23 # wtf 22.04.34 # wahts up stevie 22.05.23 # trying to understand what this stupid ROM thing is supposed to do 22.05.30 # it doesn't seem to do anything useful 22.05.36 # well try asking Micronas very nicely 22.05.39 # they make the ROM chip 22.05.48 # ... no, Micronas makes the MAS chip 22.06.04 # ohh right. Im sure the frogs who work for Archos can tell you 22.06.32 # mmmh 22.08.23 # archos is a french company :-) 22.08.33 # or im sure Bjorn and co can tell u 22.10.03 # anyone here know if usb2 is backwards compatible ? 22.10.15 # USB2 is backwards compatible with USB 1.1 22.10.29 # webmind: pretty much all USB 2.0 devices can run as USB.11 22.10.31 # 1.1 even 22.10.42 # i like the CPU's branch instruction mnemonic 22.10.47 # k good 22.12.23 # Would the Archos work if u got a USP to parallel or serial lead? 22.13.05 # tracktheripper, how do u mean ? 22.13.36 # those cables that have a type A USB plug at one end and a parallel or serial plug at the other end 22.14.10 # "just in case all of your USB ports are being used...." 22.15.03 # Zagor can I ask u something plz? 22.16.09 # I would love to see the option to reshuffle the playlist when it repeats. I use my Archos all day on random mode and its a pain manually reshuffling the list from time to time 22.20.53 Join [IDC]Dragon [0] (jirc@p50861C39.dip.t-dialin.net) 22.20.56 # tracktheripper, that's to be connected to a usb controller i think ? 22.24.48 # back 22.24.52 # wb Z 22.25.21 # tracktheripper: you can have up to 127 USB devices on one root hub... 22.29.40 # cook 22.30.34 # cool even :-) 22.38.45 # <[IDC]Dragon> I have disassembled and commented the Archos ROM bootcode, interesting things inside. Does anybody know if it's legal to publish that? 22.46.06 # hey IDC 22.46.28 # I found the glitch in my 8MB autodetection routine 22.46.39 # it should actually detect 8MB chips now 22.48.02 # <[IDC]Dragon> Hi Steve, I already saw that and repied. Yes, it works (and crashes). 22.48.20 # <[IDC]Dragon> replied, I mean 22.48.34 # cool! 22.48.57 # thats a bit different from what it did before (which was incorrectly determine 2mb) 22.49.00 # [IDC]Dragon: no it's not legal to publish the code. but you can publish discussion about it, and instructions how to extract/disassemble etc it 22.49.31 # [IDC]Dragon: when does it crash? 22.50.07 # <[IDC]Dragon> Hello Björn! So I can tell what it does, and have to email it around? 22.50.22 # <[IDC]Dragon> Steve: Whe roloing, as you said. 22.50.34 # it crashes when it ROLOs another build 22.50.45 # but when it's running itself it shouldn't crash 22.50.58 # treat the code as a book, then you'll know what I mean. you are allowed to publish excerpts and of course as much of your own comments as you like. you simply are not allowed to publish the entire code verbatim. 22.50.58 # (actually it crashes when it ROLOs anything, even itself :-o) 22.52.46 # ok, it works! 22.52.47 # woo 22.52.50 # I did something right 22.52.55 # * Stevie[FP] marks his calendar 22.53.12 # hah 22.53.31 # <[IDC]Dragon> Congratulations!# 22.53.34 # ty :) 22.53.42 # if only I knew why it crashed when ROLOing 22.54.15 # <[IDC]Dragon> Didn't went into the right code, I'd say. 22.54.36 # probably 22.54.38 # <[IDC]Dragon> Björn, are you into ROLO? 22.54.52 # yup 22.55.09 # <[IDC]Dragon> So, how does it work? 22.55.20 # do we read from the LCD status register at all? 22.55.35 # <[IDC]Dragon> I always wondered how you exchange the code under your feet. 22.55.59 # <[IDC]Dragon> LCD status register??? 22.56.17 # yeah, if you do an i2c read instead of i2c write, it seems you get a status result 22.56.46 # <[IDC]Dragon> Is that any good for 8MB? ;-) 22.57.07 # lol 22.57.38 # [IDC]Dragon: it's pretty simple, since the code only uses the first 200k. we simply copy the rolo code into a higher memory address and run it there. 22.57.47 # well, i'm glad the autodetection works 22.58.20 # Stevie[FP]: um, i don't remember if we ever read the status 22.58.25 # <[IDC]Dragon> Björn: Then you have the other 200 k wasted? Is is all position independent? 22.58.27 # it doesn't look it 22.58.58 # [IDC]Dragon: I think he means he copies the bootstrapping code into a higher memory address and loads the new image at the base address 22.59.15 # [IDC]Dragon: no, we link the rolo code for the high address. the we load the new .ajz into ~1MB, copy it back down to 0 and execute it 22.59.42 # <[IDC]Dragon> Ah, the rolo code, I see. 23.00.15 # Stevie[FP]: actually we need to load to a temporary hi-ram buffer, since the disk code is in low ram 23.01.41 # look in the linker control file (app.lds), you will see a section called .topram which is at the very top of the memory. that's where rolo is. 23.01.52 # ok 23.02.06 # from there a simple memcmp is in order? 23.02.07 # er 23.02.08 # memcpy 23.02.14 # yes 23.03.20 # ok 23.05.26 # okay 23.05.31 # when we write to the display 23.05.34 # we write 8 bits at a time 23.05.47 # yup 23.06.00 # each 'page' is 8 pixels high 23.06.14 # yes 23.06.18 # so effectively we write 8 rows, then the thing wraps to the next column 23.06.43 # <[IDC]Dragon> That's all software bitbanging, right? I wonder why the display isn't a crawl. 23.06.51 # Stevie[FP]: yes 23.07.04 # [IDC]Dragon: yup, all software. and all over a serial link! 23.07.27 # * Stevie[FP] notes that a freaky look would result from setting the base column address to '4' 23.07.38 # and it *is* a crawl, comparatively speaking... with a better link we could probably have done grayscales 23.07.49 # indeed =/ 23.08.19 # <[IDC]Dragon> No SPI feature on those ports? 23.09.16 # SPI? 23.09.24 # <[IDC]Dragon> How about som optimizes assembler for that, running from IRAM? 23.09.43 # <[IDC]Dragon> SPI it that serial link, I think. 23.09.45 Join LinusN [200] (~linus@labb.contactor.se) 23.09.58 # <[IDC]Dragon> Hi Linus! 23.10.01 # you can't read the LCD status register in serial mode 23.10.09 # only in parallel 23.10.14 # well that rules that out 23.10.15 # and 23.10.19 # somebody's been reading the logs :P 23.10.32 # no, i'm psychic 23.10.37 # ok 23.10.39 # somebody's psychic 23.10.42 # [IDC]Dragon: it already is assembler. feel free to optimise it :-) 23.10.44 # oh, guess what, Linus? 23.10.58 # ? 23.10.58 # <[IDC]Dragon> How about IRAM? 23.10.58 # I wrote something that actually works! 23.11.08 # Stevie[FP]: you fixed ROLO? 23.11.10 # [IDC]Dragon: worth trying 23.11.11 # no 23.11.17 # but the detection part works 23.11.35 # I don't have the tools and/or skills and/or knowledge necessary to debug the problem =/ 23.11.52 # actually, it's already in iram :-) 23.12.00 # * Zagor checked the code 23.12.11 # <[IDC]Dragon> Björn: And that write function seems to get called very often, for every byte. 23.12.17 # yes 23.12.41 # <[IDC]Dragon> Maybe it could take some more. 23.12.42 # [IDC]Dragon: there is room for optimization in the LCD code, but last time i tried, the LCD couldn't cope 23.13.02 # <[IDC]Dragon> Oh, that's another limit, agreed. 23.13.18 # might have been a bug in my code of course 23.13.45 # <[IDC]Dragon> How fast can you clock it, are we close to that? 23.14.04 # i don't remember 23.14.32 # <[IDC]Dragon> Maybe I'll measure it when it's open next time. 23.14.47 # do so 23.15.26 # <[IDC]Dragon> May I change the subject on booting? 23.17.08 # [IDC]Dragon: ? 23.17.12 # <[IDC]Dragon> I haven't done the real test (because it requires to pull the 3 LCD input lines low), but with a simulator I managed to "boot" from UART. 23.17.53 # <[IDC]Dragon> Meaning, we could execute something without anything useful in flash. 23.18.08 # i see where you are heading 23.18.19 # <[IDC]Dragon> Haaa... 23.18.54 # <[IDC]Dragon> 1st stage we can only load into IRAM, the DRAM is not initialized yet. 23.19.33 # <[IDC]Dragon> A bit crammy in there. Do we have the 7032 with 8K or the 7034 with 4 K? 23.19.40 # 7034 23.20.05 # <[IDC]Dragon> As I guessed, the other one has no ROM. 23.20.16 # right 23.20.43 # <[IDC]Dragon> The ROM code is prepared for multi-boot, the LCD lines decide. 23.21.38 # <[IDC]Dragon> It grabs image "n" from a list. In the available firmwares these entries all point to the same block. 23.21.50 # cool 23.22.18 # <[IDC]Dragon> Scrambling is mandatory for such a block. 23.22.29 # we need to find a way to do this without the LCD trick... 23.22.48 # <[IDC]Dragon> Change the ROM, I'm afraid... 23.23.01 # what does it do if there is no valid image in flash? 23.23.22 # <[IDC]Dragon> it checks for the "ARCH" ID right at the start. 23.23.45 # <[IDC]Dragon> If that's present, it will blindly use whatever values it finds. 23.23.55 # what LCD trick? 23.24.19 # has anyone compared the flashed version with the same file version? 23.24.20 # [IDC]Dragon: and what if it is no ARCH? 23.24.27 # <[IDC]Dragon> If there is no "ARCH", it will flash the red LED a couple of times and the sleep in coma. 23.24.33 # Stevie[FP]: pulling the three LCD lines low 23.24.59 # <[IDC]Dragon> Port B, bit 1-3 (not 0) 23.25.10 # ok 23.25.14 # and what does this do exactly? 23.25.33 # if you do this, the cpu will boot into a special debug monitor 23.25.35 # <[IDC]Dragon> It goes to a UART boot mode, expecting code from there. 23.25.50 # okay 23.26.00 # <[IDC]Dragon> It's not a monitor, just a very simple code. 23.26.52 # <[IDC]Dragon> But you can use it to trasfer "something" into the box and execute it. In my example, a flash programmer. 23.27.42 # <[IDC]Dragon> Linus, the suspense goes on: 23.28.20 # <[IDC]Dragon> The image being descrambled from flash is quite small, about 9k. 23.28.50 # <[IDC]Dragon> It's not the final firmware. 23.29.02 # that's at 0x2000000 or whatever? 23.29.38 # <[IDC]Dragon> Instead, this is your "debugger", in fact it seems to be a flash tool. 23.30.04 # nice 23.30.35 # <[IDC]Dragon> I don't know how to operate it, just saw the strings in there. 23.31.20 # cool 23.31.30 # <[IDC]Dragon> Remember the box "talking" with 115200 baud on power up? That's this tool. You can hold it with any char from a terminal. 23.31.48 # 115200, now that's MY kinda serial speed 23.32.05 # <[IDC]Dragon> But then it wasn't responsive. 23.33.58 # do we have a quick reference table somewhere of what contraptions are mapped at what addresses? 23.34.29 # <[IDC]Dragon> ??? 23.34.39 # example: external DRAM at 0x09000000 23.34.44 # internal RAM at 0x00000000 23.34.52 # external ROM at 0x02000000 23.35.03 # <[IDC]Dragon> Linus, please check your mail, I've sent you the files. 23.35.56 # <[IDC]Dragon> internal RAM is 0x0FFFF000-0x0FFFFFFF 23.36.23 # <[IDC]Dragon> You can get all that from the SH CPU datasheets. 23.37.14 # err 23.37.17 # sorry 23.37.20 # internal ROM at 0x00000000 23.37.42 # <[IDC]Dragon> Yes, 64k from there. 23.37.56 # <[IDC]Dragon> Archos is only using about 1.7k. 23.37.58 # but what's at 0x01 or 0x03? 23.38.10 # and, for example, where is the RTC chip, where is the FM chip 23.38.34 # <[IDC]Dragon> Check the code ;-) 23.38.34 # we've got 16 possible values 23.39.19 # * Stevie[FP] rather dislikes values written as 0x100000 or 0x2000000 23.39.38 # 0x200000 and 0x2000000 look the same damnit 23.40.21 # after about 5, all strings of 0s look the same =/ 23.41.21 Join matsl [0] (~chatzilla@as13-4-5.mal.s.bonet.se) 23.42.57 Quit matsl (Client Quit) 23.43.47 Join Bagder [241] (~daniel@as3-3-2.ras.s.bonet.se) 23.44.02 # hi Bagder 23.44.02 # <[IDC]Dragon> (I guess Linus is gone reading) 23.44.07 # hi 23.44.30 # Bagder could u do me a favour plz? 23.44.42 # it depends 23.44.55 # what do you want? 23.45.25 # could u fix the "Reshuffle when playlist repeats" request for me plz? 23.46.43 # u there? 23.46.44 # that one is not first on my list 23.46.55 # awwwwwwwww :-( 23.47.37 # wtf 23.48.21 # wtf is a K4E151612D 23.48.46 # oic 23.49.16 # Stevie[FP]: the RTC and the FM chip are not address coded 23.49.42 # oh 23.49.44 # what are they? 23.49.51 # i2c? 23.49.56 # RTC is on the I2C bus 23.50.05 # I2C is on a separate bus 23.50.11 # sorry, FM 23.50.15 *** Saving seen data "./dancer.seen" 23.50.18 # so is ths LCD 23.50.28 # the MAS is on I2C too 23.50.46 # oh 23.50.48 # theres another bus? 23.50.58 # we have the standard address/data bus 23.51.00 # we have an i2c bus 23.51.04 # u wait ages for a bus then all 3 come at once! 23.51.26 # for once I must agree with tracktheripper 23.51.37 # yay!! 23.51.41 # <[IDC]Dragon> Is that why the FM has no remote control? 23.52.09 Quit mecraw (Read error: 110 (Connection timed out)) 23.52.10 # [IDC]Dragon: that has nothing to do with it 23.52.35 # <[IDC]Dragon> I thought they "bent" that pin for new use. 23.52.57 # what is at 0x04000000? 23.53.10 # only two references to it, and it's used as a magic number 23.53.27 # they did have a use for the RX pin on the FM 23.53.45 # but they scrapped that ides 23.53.48 # idea 23.54.02 # linus? 23.54.06 # there is an empty socket for an RDS decoder on the PCB 23.54.26 # <[IDC]Dragon> cool! 23.54.54 # ((buys LinusN a guniess)) 23.55.14 # tracktheripper: you really should try the /me command ;-) 23.55.15 # i think they discovered that the CPU couldn't keep up with the RDS data rate 23.55.46 # * tracktheripper twists LinusN's arm into fixing the "reshuffle" request 23.55.46 # <[IDC]Dragon> What a pity. 23.56.01 # indeed 23.56.29 # <[IDC]Dragon> BTW, do you know that "warp" feature of the CPU? Are you using it? 23.56.39 # the source says so 23.57.48 # we use it 23.58.02 # warp? 23.58.05 # yes 23.58.10 # <[IDC]Dragon> Any side effects to be aware of? 23.58.12 # simultaneous internal/external bus access 23.58.17 # ah, right 23.58.19 # does that make leaps in time? :-] 23.58.24 # * tracktheripper grabs Zagor and dances around the room 23.58.26 Join tchan [0] (~tchan@12-247-188-25.client.attbi.com) 23.58.49 # * LinusN thinks that tracktheripper bought himself one Guinness too many 23.58.52 # oh! Linus, did you do the rec_main.pdf schematic drawing?