--- Log for 07.10.104 Server: burroughs.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 2 days and 23 hours ago 00.00.56 Quit marc77 (Read error: 110 (Connection timed out)) 00.00.59 # I'll retry with latest cvs code (had a testing directory which is no direct checkout) 00.02.24 # <[IDC]Dragon> what a comprehensive MMC info you've got 00.02.50 # It's still not everything that is contained in the MMC registers ... 00.03.13 # <[IDC]Dragon> the year has only 4 bits, how short-sighted 00.03.31 # Did you notice: You can get info for both internal and external 00.03.56 # <[IDC]Dragon> I didn't 00.04.21 # Ah, I remember that you have no working external card :( 00.07.13 # Argh, my const'ing causes that dreaded "initialization discards..." warning if PREFER_C_WRITING is defined 00.07.25 # Hidden bug :/ 00.09.30 # No panic with my latest build! :) 00.10.30 # Windows chkdsk does find no filesystem error either 00.13.57 # <[IDC]Dragon> hooray! 00.14.33 # <[IDC]Dragon> \o/ Jens \o/ 00.15.30 # <[IDC]Dragon> this will make Ondio hacking interesting! 00.19.10 # FAT32 still working as well. 00.19.29 # <[IDC]Dragon> beautiful 00.19.30 # Of course I didn't do extensive tests 00.19.55 # <[IDC]Dragon> the test suite doesn't help us here, of course 00.21.22 # I could adapt my filesystem stress test plugin (which I originally wrote for checking FAT32 whether it fails when saving recorded data) 00.21.37 # This has to be adapted to the player lcd 00.21.58 # <[IDC]Dragon> what does it do? 00.23.01 # It writes lots of data (pseudo-random sequence) to disk with a behaviour as close as possible to how the recording code does it 00.23.26 # (writing 2 large blocks with a pseudo-random split point) 00.23.45 # <[IDC]Dragon> linear write, not terribly interesting 00.23.47 # Then it reads back all data and compares with the pseudo-random sequence 00.24.19 # <[IDC]Dragon> honestly, I don't expect trouble from the unsigned 00.24.30 # Well, it's not completely linear, because the FAT is accessed in between 00.24.53 # <[IDC]Dragon> if some code only worked because it was signed, it must have been strangely wrong 00.25.14 # Okay, perhaps I should simply commit 00.25.46 # <[IDC]Dragon> how much work is it to port your test? 00.26.33 # I would have to cut down the output to 2 lines. Shouldn't be that hard, since I use a roll function (restart at top line if bottom one was used last) 00.28.15 # But running it can take a loong time. When I did the test with the recorder (using a little less than 2 GB in total) it ran ~9 hours 00.28.28 # Of course I wouldn't test with 2 GB here 00.28.39 # <[IDC]Dragon> I was about to ask 00.29.45 # It's a nice little stress test anyway. Perhaps I'll run it on the Ondio too, stressing the MMC driver 00.29.54 # <[IDC]Dragon> I'm building with unsigned ,too 00.30.11 # <[IDC]Dragon> don't stress writing too hard 00.30.46 # I think it's no problem, since it doesn't write the same sector everytime 00.31.06 # <[IDC]Dragon> except for the fat 00.31.43 # This is written to more than once, yes, but not that often too. 00.32.24 # Of course we'd need plugin support to do the test 00.33.27 # <[IDC]Dragon> ah, I remember 00.34.21 # My test plugin needs a patch to plugin.[ch]. fsync() is not in the plugin api by default 00.34.45 # <[IDC]Dragon> OK, forget it 00.35.59 # I've still got the .patch file, so it's easy 00.37.22 # <[IDC]Dragon> I'm starting it on my box now 00.37.37 # <[IDC]Dragon> (the build) 00.38.57 Quit PRVSaosn ("( www.nnscript.de :: NoNameScript 3.81 :: www.XLhost.de )") 00.39.18 Join ripnetUK [0] (~mirc@82-70-100-230.dsl.in-addr.zen.co.uk) 00.46.26 # [IDC]Dragon: Testing on FAT32 with ~100 MB of data... 00.47.18 # <[IDC]Dragon> I did a manual test session, no problems. 00.47.56 # <[IDC]Dragon> recording, deleting files, bookmarking,... 00.48.30 # Both fat16 and fat32? 00.49.24 # <[IDC]Dragon> no, just FAT32 00.49.45 # <[IDC]Dragon> I'm not worried about a broken FAT16 in cvs 00.50.17 # <[IDC]Dragon> (well, no more than we have that now) 00.50.39 # You're right. So when my fat32 test completes without error, I'll commit, then I'll do the fat16 test. 00.51.07 # <[IDC]Dragon> but killing peoples HD file systems would be very embarrassing 00.53.02 Quit plok ("I'm outta here!") 00.53.06 *** Saving seen data "./dancer.seen" 01.02.42 # [IDC]Dragon: You just saved one config bit ;) 01.03.11 # ANd I have to rebuild the .voice files 01.04.21 # <[IDC]Dragon> not urgently 01.05.25 # <[IDC]Dragon> Ondio can write, hooray! 01.05.34 # <[IDC]Dragon> just dumped the ROMs 01.06.26 Quit _aLF ("Leaving") 01.07.16 # Rebuilding the .voice files should be easy, but I wonder how out "Klara" will pronounce ".talk" (without a hint, that is) 01.08.11 # <[IDC]Dragon> Im not sure how to name that entry, in general 01.08.21 # <[IDC]Dragon> feel free to improve 01.09.28 # Just found that the german voice: entry is just "Sprachdatei". This should work of course, but it may confuse users 01.09.59 # <[IDC]Dragon> I think it's fine 01.10.18 # I would associate "Sprachdatei" with a .voice file 01.10.26 # Unfortunately there is no simple german equivalent to "clip" 01.11.37 # <[IDC]Dragon> I'll sleep well now 01.11.43 # <[IDC]Dragon> cu 01.11.50 # <[IDC]Dragon> and thanks! 01.11.53 # Goodnight 01.11.58 Quit [IDC]Dragon () 01.24.58 Quit mecraw ("Trillian (http://www.ceruleanstudios.com)") 01.53.10 Quit AciD (Remote closed the connection) 01.53.40 Join iRiverMan [0] (~acbf1317@labb.contactor.se) 01.56.43 # hi# 02.02.02 Join ashridah [0] (ashridah@220.253.118.206) 02.24.13 Quit iRiverMan ("CGI:IRC (EOF)") 02.37.00 Quit amiconn (" Peer didn't reset this connection") 02.53.07 *** Saving seen data "./dancer.seen" 03.01.23 Quit midk (Read error: 104 (Connection reset by peer)) 03.22.50 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 04.09.05 Join scott666_ [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 04.10.29 Quit scott666 (burroughs.freenode.net irc.freenode.net) 04.10.29 NSplit burroughs.freenode.net irc.freenode.net 04.10.29 Quit gromit``` (burroughs.freenode.net irc.freenode.net) 04.10.29 Quit Professor (burroughs.freenode.net irc.freenode.net) 04.18.24 NHeal burroughs.freenode.net irc.freenode.net 04.18.24 NJoin gromit``` [0] (~gromit@ALagny-151-2-10-68.w82-121.abo.wanadoo.fr) 04.53.11 *** Saving seen data "./dancer.seen" 05.26.09 Quit ashridah ("gone") 06.20.23 Quit scott666_ ("i'll be back...eventually...") 06.52.21 Join LinusN [0] (~linus@labb.contactor.se) 06.53.15 *** Saving seen data "./dancer.seen" 07.26.34 Join methangas [0] (methangas@0x50a461b8.virnxx10.adsl-dhcp.tele.dk) 07.27.41 Join [IDC]Dragon [0] (~idc-drago@pD9FF80B1.dip.t-dialin.net) 07.30.57 # <[IDC]Dragon> good morning 07.31.35 # <[IDC]Dragon> what a nice one, with FAT16 working :-) 07.32.05 Quit midk ("just STOP it arspy") 07.32.10 Join midk [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 07.40.05 # wonderful 07.45.01 # * [IDC]Dragon has the Ondio back together for the first time, before it was "just" a PCB on the bench 07.45.22 # <[IDC]Dragon> I stripped the wires off 07.47.09 # what wires? 07.47.40 # <[IDC]Dragon> debug wires ;-) 07.49.27 # ah 07.56.31 Join Chronic007 [0] (~Miranda@24.30.163.142) 08.11.18 Join plok [0] (s336156@student.uq.edu.au) 08.15.31 # <[IDC]Dragon> Bagder: r u there? 08.17.04 # * plok is away - Automatically set away. - messages will be saved. 08.28.27 # [IDC]Dragon: http://forums.rockbox.org/index.php?topic=30.from1097128134;topicseen#msg94 08.30.18 # <[IDC]Dragon> dunno what he did wrong 08.45.30 # <[IDC]Dragon> hey, the OndioFM build fits as rombox! 08.46.27 # nice 08.46.53 # <[IDC]Dragon> another 0.3 sec boot time gained 08.47.18 Join amiconn [0] (~jens@pD95D194F.dip.t-dialin.net) 08.47.18 # wooooo 08.47.54 # boot time on the iRiver is very long :( (H340 at least) 08.52.11 # i heard it takes ages if you use the id3 database 08.53.17 *** Saving seen data "./dancer.seen" 08.53.35 Join webguest84 [0] (~0c68cc30@labb.contactor.se) 08.53.47 Quit webguest84 (Client Quit) 08.55.22 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 08.55.35 # I don't use the database but it still takes roughly 10 seconds to boot up I'd guess 08.57.31 # the H120 takes quite a while too 09.11.24 Join Zagor [242] (~bjst@labb.contactor.se) 09.11.48 # Zagor: welcome 09.12.16 # my ribs hurt :) 09.12.33 # Zagor: i'm having problems deciding how to handle the iriver #ifdefs in for example backlight.c 09.13.01 # i'm opting for #ifdef IRIVER_H100 09.14.10 # yes, i agree. i think when the conditional is "which circuit board is this", the general player define is suitable 09.14.22 # good 09.14.47 # we can always refine it later if we find the need 09.15.08 # we could have a PLATFORM define with several values 09.15.22 # #if PLATFORM == IRIVER_H100 09.15.46 # sure, no problem 09.16.06 # i'll go for #ifdef IRIVER_H100 for now 09.19.19 # <[IDC]Dragon> we already have PLATFORM_ID, but it's use was discouraged 09.19.39 # <[IDC]Dragon> because we should check for features instead 09.20.16 # <[IDC]Dragon> oh, forget that 09.20.30 # <[IDC]Dragon> utter bullshit, I did that locally 09.20.41 # :) 09.20.49 # you had me confused for a while... 09.21.06 # <[IDC]Dragon> we have ARCHOS_xxx, which are flags 09.21.11 # imho, feature checks are platform specific 09.21.33 # <[IDC]Dragon> yes, but you check for the feature,not the platform 09.21.38 # but we should go from ARCHOS_xxx to PLATFORM= instead 09.22.01 # <[IDC]Dragon> recently; ilike multi-valued items, since the # of platforms is growing 09.22.09 # <[IDC]Dragon> agreed 09.22.27 # <[IDC]Dragon> because this is another bunch of flags 09.22.49 # my view of this is: 09.23.06 # HAVE_xxx are for general features, like HAVE_BACKLIGHT 09.23.32 # <[IDC]Dragon> for the backlight, I'd say CONFIG_BACKLIGHT = aaa|bbb|ccc for different hookups 09.23.34 # PLATFORM_xxx is the platform, eg IRIVER_H100 or ARCHOS_RECORDER 09.24.25 # [IDC]Dragon: agreed 09.24.42 # but the CONFIG_BACKLIGHT values may differ between platforms 09.24.52 Join uski [0] (~uski@ALagny-151-2-6-37.w82-121.abo.wanadoo.fr) 09.25.07 # <[IDC]Dragon> yes, or not exist if no backlight 09.25.14 # then we agree 09.25.17 # uski: hi 09.25.41 # hi LinusN :) 09.25.46 # received my package ? 09.25.57 # uski: I got your stuff 09.26.02 # ok 09.26.04 # :-) 09.26.07 Join Tron|Uni [0] (~tron@hobbit.chemie.uni-hamburg.de) 09.26.15 # what's up ? long time no see 09.26.32 # hi1 09.26.40 # err, "hi!" 09.27.40 # uski: not much, i'm working a lot on the iriver port 09.32.36 # * Bagder crawls in 09.33.31 # nice warning flood yday LinusN ! :-) 09.33.42 # 1254 ought to be some kind of record! 09.34.48 # :) 09.37.19 # Bagder: :-) 09.39.30 Join pillo [0] (~trillian@navlab03.dei.unipd.it) 09.41.01 # does Dave Hooper pop into this channel? 09.47.38 # does the H300 have a real time clock? 09.58.05 # Bagder: u there? 09.58.10 Join amiconn_ [0] (~jens@pD9E7FC12.dip.t-dialin.net) 09.58.23 # he does sometimes 09.58.58 # i want to add his scrambling code to our scrambler 09.59.21 # I'm here 10.00.18 # can we change the config/make system so we can build a target without scrambling? 10.01.17 # currently it requires a $tool 10.01.48 # * Bagder looks 10.01.51 Join iRiverMan [0] (~acbcd005@labb.contactor.se) 10.02.02 # hi 10.02.06 # hi 10.03.34 # LinusN: make the tool named cp for now 10.03.52 # can't do that 10.04.09 # it is prefixed with the path to the rockbox tools dir 10.04.40 # want me to fix? 10.04.54 # please 10.05.02 # * Bagder dives 10.05.37 # i'd like to add the iriver scrambling algorithm, but the source is currently unavailabe 10.05.49 Quit ripnetUK () 10.06.12 # the link is dead? 10.06.20 # i have it downloaded 10.06.28 # DNS doesn't resolve 10.06.38 # do we have his permission btw? 10.07.28 Quit amiconn (Nick collision from services.) 10.07.28 Nick amiconn_ is now known as amiconn (~jens@pD9E7FC12.dip.t-dialin.net) 10.08.12 # LinusN: try this 10.08.28 # or 'try now' rather 10.08.34 # ok 10.08.43 # LinusN: the license allows it, with a bsd-style banner clause. we can ask him for an exception to the clause. 10.08.54 Quit [IDC]Dragon () 10.09.43 # hi all 10.09.50 # hi Jens 10.10.25 # Bagder: works, but now it UCL-packs..... 10.11.11 # I didn't change that 10.11.29 # that's a different problem 10.11.33 # i know, i didn't get that far before 10.12.05 # lemme think a while on how to correct that 10.12.15 # unless you have an idea 10.12.17 # Zagor: Next button issue: If you enter a sub-browser (plugins/ langs etc) from the menu, the first entry gets selected immediately. This seems to be a player-only issue 10.13.27 # it shouldn't uclpack targets that don't support flashing 10.13.37 # like the player for instance 10.13.50 # the question is how it is nicest done in the makefile 10.14.19 # probably the target shouldn't be included in the all: line 10.14.32 # Zagor: I wonder how this happens. I thought the button code does only send *one* button event for button down, then waits until repeat kicks in, then send button|BUTTON_REPEAT events continiuously until release, then sends one single release event. 10.14.42 # like how the ROMTARGET already works 10.14.55 # exactly 10.15.12 # I'll work on a fix 10.15.13 # amiconn: yes, that's how it works 10.15.55 # So I wonder what causes the sub-browser issue on the player. The button down event gets "eaten" by the menu code entering the sub-browser... 10.16.38 # looking... 10.17.37 # aha. "run" is now play+release, since play+repeat is context menu... 10.17.47 # the puzzle keeps growing :) 10.18.20 # (i.e. you see the same problem on recorder if you use PLAY to select the "browse plugins" menu entry) 10.20.32 # LinusN: ... and update! 10.22.07 # Bagder: how do i make it not to build plugins? 10.22.24 # ifdef them in SOURCES 10.22.45 # what is the plugins="yes" for in configure? 10.22.52 # ah, right 10.22.56 # that's how I made it 10.22.58 # set it to "" 10.23.05 # plugins="" 10.23.13 # i have tried not to set it, but it doesn't work 10.23.17 # Zagor: Ah, yes. I did not get that since I usually use Right to enter the browsers. Strangely, it works for Ondio, which has no separate Play... 10.24.08 # that's because the ondio context menu is broken :) (I just noticed) 10.24.28 # LinusN: odd, it worked for the ondios before 10.24.32 # plugins="" doesn't help 10.24.51 # it still tries to build the plugins library 10.25.10 # hmm, tricky one 10.26.52 # ENABLEDPLUGINS isn't used anywhere 10.29.02 # LinusN: When plugins were disabled for Ondio, it did also still build the plugin lib. Seems that the Makefile for the plugin lib needs a fix 10.32.48 # LinusN: ENABLEDPLUGINS is used in plugins/Makefile 10.33.03 # Bagder: check my commit 10.33.04 # use it in lib/Makefile as well, and I think it should work 10.33.23 # i think it should be done in apps/Makefile 10.33.51 # right, that's probably nicer 10.34.01 # then you can remove it from plugins/Makefile 10.34.32 # doing it now 10.35.15 # done 10.35.36 # ok, now the iriver target builds ok 10.36.43 # cool 10.36.47 # gotta run off 10.37.34 # cu 10.40.34 # * LinusN has a fairly safe lead the wiki statistics :-) 10.48.07 # I was noticing that earlier....thanks for all your hard work Linus 10.53.18 *** Saving seen data "./dancer.seen" 10.53.51 Join PaulS [0] (~437e19f6@labb.contactor.se) 10.55.21 # oh-yes, the good iriver port conversation is about to begin 11.04.46 Join hima [0] (~hima_mhmd@62.139.64.184) 11.05.27 Join MooMaunder [0] (~me@194.152.87.150) 11.10.29 Join ashridah [0] (ashridah@220.253.119.48) 11.12.11 Quit iRiverMan ("CGI:IRC (EOF)") 11.26.17 Part hima 11.48.07 # PaulS: u there? 11.59.35 # Yep.. 12.01.30 # any luck with the jtag? 12.01.37 # Thanks for the tip about pulling up the power supply line. When I hold the system reset, it doesn't power off. 12.02.09 # i have added valuable info for you in the schematics 12.02.29 # cd .. 12.03.10 # I didn't try JTAG again. I did try the BDM interface again, but BKPT still didn't seem to do anything, so I imagine I'm using the wrong pads. 12.03.37 # LinusN: Valuable info? Hmm! 12.03.51 # check the "connectors" schematic 12.04.16 # now you can trace the correct pads from the debug connector 12.04.50 Quit PaulS ("CGI:IRC (EOF)") 12.08.26 Join PaulS_ [0] (~437e19f6@labb.contactor.se) 12.09.29 # LinusN: Thanks a lot. This will take the guesswork out of it. So far I only know I had the CPU reset correct. 12.14.26 # i hope it helps 12.15.00 # I'm downloading the naked pics as I speak to see how far off I was. 12.15.13 Nick PaulS_ is now known as PaulS (~437e19f6@labb.contactor.se) 12.17.16 # Congrats on the blinkenleds, BTW, as well as the (presumably not actually functional) rockbox build. 12.17.45 # does the H300 have a real time clock? 12.17.46 # Were you using the drive access light, or the charging LED? 12.19.43 # the backlight 12.20.01 # Ah! Those are LEDs too... 12.25.58 # LinusN: sneaky :) 12.30.42 # It appears that my guesses about the debug pads seem to agree with the connector schematic. 12.30.44 # * LinusN sends his second coldfire patch to the binutils project 12.32.56 # LinusN: How many of those patches has been sent without any response? 12.33.42 # my very first patch (the windows resource compiler) still hasn't received a response 12.34.04 # but the first coldfire patch has been accepted 12.34.09 Join R3nTiL [0] (~zorroz@164-250-30-217.kgts.ru) 12.36.17 # neato! 12.36.26 # It's about giving stuff back! :) 12.39.17 # yup 12.42.10 # Good night, folks. 12.42.39 Part PaulS ("Z") 12.44.16 # lunch 12.52.12 Join HuwSy [0] (~na@213-232-83-64.dsl.prodigynet.co.uk) 12.53.11 # lil help, im looking to flash my recorder10 back to the original firmware, whats the easiest way 12.53.20 *** Saving seen data "./dancer.seen" 12.56.35 # rename the original firmware file to firmware_rec.bin and run the firmware_flash.rock plugin again 12.56.57 # assuming you did back up the original firmware when you flashed rockbox the first time 12.57.02 # iv lost the original file be the problem 12.57.17 # which version was it? 12.57.27 # 1.27c 12.57.52 Join [IDC]Dragon [0] (~d90a3255@labb.contactor.se) 12.58.03 Quit plok (Ping timeout: 14400 seconds) 12.58.30 # you can find the original firmware here: http://homepage.ntlworld.com/cyborgsystems/CS_Main/RockBox/Archos/jbrv1_bin_128.zip 12.58.52 # thank you 12.59.09 # it's the "internal_rom_20000...." file 12.59.31 # rename it to firmware_rec.bin and put it in the root of your archos, then run firmware_flash.rock 12.59.39 # and pray.... 12.59.45 # :-) 12.59.57 # <[IDC]Dragon> he's exaggerating... 13.00.09 # seriously, i don't know if 1.28 works on the rec10, but i assume that it does 13.00.46 # the only prob would be the hw mask, but i assume that firmware_flash.rock preserves it 13.00.58 # <[IDC]Dragon> yes, it does 13.02.39 # than all is fine. 13.06.46 # hum... its not letting me load up into rockbox to even attempt a flash. i think its overly flat 13.07.10 # oh well ill hopefully get it sorted later, thanx for the help 13.08.59 Quit HuwSy () 13.11.32 # <[IDC]Dragon> everybody wants a flashback... 13.12.09 # <[IDC]Dragon> amiconn: do you read? 13.31.18 Quit R3nTiL () 13.34.15 # [IDC]Dragon: Now I'm here 13.40.16 # <[IDC]Dragon> hi 13.40.30 # <[IDC]Dragon> I have the flash plugin working now 13.41.50 # <[IDC]Dragon> so you could flash yours tonight 13.42.08 # <[IDC]Dragon> even RomBox works for me :-) 13.45.33 # So it should work on the SP for sure 13.46.01 # Did you already look into the RoLo issues with the archos fw? 13.47.13 # <[IDC]Dragon> no, not yet 13.47.52 # <[IDC]Dragon> I actually forgot about that issue 13.48.32 # That reminds me that we wanted to add a table of issues to the wiki topic, together with status 13.48.55 # <[IDC]Dragon> yes please 14.06.52 Part Chronic007 14.40.44 # <[IDC]Dragon> Bagder: reading? 14.49.51 Join zoevi [0] (~d9f69ab4@labb.contactor.se) 14.53.24 *** Saving seen data "./dancer.seen" 14.58.10 # reading now 14.58.23 Join webguest46 [0] (~d96ee3e8@labb.contactor.se) 14.59.51 Quit zoevi ("CGI:IRC") 15.01.42 # LinusN: time to add iriver to the cvs build table? 15.01.51 # <[IDC]Dragon> Bagder: how about enabling the Ondio daily build? 15.02.09 # me fix! 15.02.33 # <[IDC]Dragon> the download, I mean, with the pretty picture and stuff 15.02.41 # yes 15.02.48 # <[IDC]Dragon> ok 15.02.49 # the whole package 15.03.16 # <[IDC]Dragon> did Jens send you a picture? 15.03.21 # yes 15.03.31 # ah, no 15.03.33 # No I didn't. Have to close the Ondio first. 15.03.34 # only your pics 15.03.40 # http://www.rockbox.org/ondio/ 15.04.05 # <[IDC]Dragon> those are my FM pictures 15.04.28 Join elinenbe [0] (~elinenbe_@65.115.46.225) 15.04.56 # <[IDC]Dragon> then use it for both, for the time being 15.05.02 # yes 15.05.26 # LinusN: a huge congrats! Great work... everything starts somewhere! 15.06.01 # [IDC]Dragon: How did you take the pictures? With the scanner? 15.06.26 # <[IDC]Dragon> amiconn: digicam. mine was also not closed for the pic, just placed 15.07.01 # <[IDC]Dragon> scanner is even better, if you have one of those thick flatbeds 15.07.42 # <[IDC]Dragon> I have a thin one with a LED bar, has no depth focus at all 15.08.07 # reload daily build page 15.08.41 # <[IDC]Dragon> that was quick 15.08.43 # i think adding iriver to the daily builds page is a bit premature 15.08.52 # elinenbe: thanks 15.09.04 # LinusN: it would help us not break it when we modify things 15.09.12 # and vice versa 15.09.22 # it still needs a patched version of the compiler 15.09.37 # and it only compiles crt0.S and backlight.c :-) 15.09.46 # atm, yes 15.10.04 # oh well, I won't push it 15.10.09 # LinusN: if I have an iriver, can I flash the rockbox firmware? 15.10.11 # what the heck, add it then 15.10.25 # just to see the backlight flash? 15.10.29 # LinusN: do we have the patch compiler on the host? 15.10.32 # patched 15.10.40 # but, how would I flash it back to the iriver firmware? 15.10.41 # elinenbe: yes, but you won't be able to restore the original firmware 15.10.54 # [IDC]Dragon: My digicam doesn't make such nice pics as yours. First it's only 2 Mpixel, second it has no macro feature, closest range is ~60 cm 15.10.57 # so your player will be a paperweight 15.11.14 # I'll try to do it with the scanner @work tomorrow 15.11.17 # elinenbe: you'd be fairly screwed without being able to take it apart and plug in a bdm to restore the original firmware 15.11.24 # Bagder: i sent my second patch to the binutils project today 15.12.06 # you will be the coldfire binutils king! ;-) 15.12.12 # hehe 15.12.23 # LinusN: is the gcc/binutils installed/working on labb? 15.12.23 # LinusN: I wouldn't put it up on the daily builds page yet then... that is just asking for trouble. 15.12.40 # no daily builds, no 15.12.45 # you will be cold fire binutils helpdesk ;) 15.12.46 # but the cvs build table 15.12.49 # elinenbe: only the build status, not any downloads 15.12.55 Quit gromit``` (Read error: 110 (Connection timed out)) 15.13.17 # <[IDC]Dragon> amiconn: we only need the medium and small size pic, 2 MP from 60 cm should be enough for that 15.13.25 # Bagder: no m68k compiler on labb, only on my computer 15.13.32 # Zagor: check the daily build log careful tomorrow, the ondios should get built now 15.13.38 # yup 15.13.49 # what does BDM stand for anyway? 15.13.59 # breakout debugging module ? 15.14.00 # LinusN: aha, care you install it on labb so that we can get it cvs-built? 15.14.01 # ashridah: Background Debug Mode 15.14.04 # ah. 15.14.07 # that was my second guess 15.14.10 # s/you/to 15.14.12 # Bagder: ok 15.14.22 # <[IDC]Dragon> amiconn: the big one wast just my raw data, before scaling it to about the size I found on the build page 15.16.18 # [IDC]Dragon: Another problem with digicam is to get the lighting right, and the neutral gray background 15.22.15 # <[IDC]Dragon> amconn: I went on the balcony, placed it on the white backside of a calendar 15.22.31 # <[IDC]Dragon> s/amconn/amiconn (sorry) 15.22.57 # [IDC]Dragon: Use TAB completion ;) 15.23.05 # <[IDC]Dragon> the white balance was still way off, but that can be corrected 15.23.28 # <[IDC]Dragon> tab doesn't work if there's more people with A 15.23.29 # The balcony approach does only work if you are at home when there is daylight 15.23.38 # 15.24.20 # <[IDC]Dragon> just make a picture with any light, I'll try to fix it 15.24.40 # <[IDC]Dragon> diffuse light preferred 15.24.56 Join gromit` [0] (~gromit@ALagny-151-2-10-250.w82-121.abo.wanadoo.fr) 15.26.17 # [IDC]Dragon: Does your Ondio really have such a strong blue colour? Mine does look more violet... 15.28.44 # <[IDC]Dragon> it's a bit more violet than it appears 15.32.38 Quit uski (Read error: 110 (Connection timed out)) 15.43.04 # Bagder: /usr/local/m68k-gcc 15.43.14 # neato 15.43.18 # patched with my latest addition 15.47.27 # <[IDC]Dragon> Bagder: I guess tomorrow there will automagically appear something for the download link? 15.47.35 # yes 15.47.39 # if everything works 15.47.44 # <[IDC]Dragon> ;-) 15.48.39 # iriver h100 added to cvs build table 15.48.47 # nice 15.49.19 # <[IDC]Dragon> I don't see it, mabe after the next commit? 15.49.27 # yes 15.50.02 # I just added it to the script that builds stuff after each commit 15.51.53 # and you added the compiler to the PATH? 15.51.56 # yes 15.52.12 # time to add the ondios to http://www.rockbox.org/docs/devicechart.html ? 15.52.39 # <[IDC]Dragon> why not? 15.53.00 # don't look at me! ;-) 15.53.05 # [IDC]Dragon: your job 15.53.16 # <[IDC]Dragon> ok, not now (no cvs) 15.53.28 # I'm off 15.53.37 # cu 15.56.02 # <[IDC]Dragon> who did the mp3ClipGen.vbs script? 15.56.14 # <[IDC]Dragon> I fail to remember 15.59.37 # * [IDC]Dragon googles like crazy 16.07.41 # [IDC]Dragon: Search the ml 16.11.23 # time to go 16.11.25 # bye all 16.11.40 Part LinusN 16.13.09 # <[IDC]Dragon> I tried. Brian Wolven is a candidate, but I haven't found a proof 16.16.49 # <[IDC]Dragon> he is, now I found it 16.17.19 # <[IDC]Dragon> or? no, this was playlist scripts 16.19.33 # * amiconn is looking into the script 16.20.29 # Hmm, no hint in there :( 16.20.30 # <[IDC]Dragon> seems to be Brian: http://www.rockbox.org/mail/archive/rockbox-archive-2004-03/1332.shtml 16.23.03 # It does look like that, yes 16.23.22 # <[IDC]Dragon> the voice UI is olter than I thought 16.23.28 # <[IDC]Dragon> older 16.23.56 # <[IDC]Dragon> and v2.2 even more 16.38.28 Join mecraw [0] (~lmarlow@69.2.235.2) 16.53.26 *** Saving seen data "./dancer.seen" 17.16.59 Quit webguest46 ("CGI:IRC (EOF)") 17.19.54 Join ripnetUK [0] (~mirc@82-70-100-230.dsl.in-addr.zen.co.uk) 17.20.16 # * ripnetUK builds a 68000 cross compiler 17.20.49 # Im trying to cook a m68k cross compiler - do I need to use the cvs to get LinusN's patches in, or does that only apply if im using gdb? 17.27.29 # i'm not sure what his latest patch was 17.35.48 # the onbe im talking about was assembling the 68k equivelent of sse instructions 17.36.10 # i guess its a bit academic until we have working code anyway :) 17.36.21 # the EMAC, yes. for that you need his patch. 17.42.56 Quit ashridah ("sleep") 17.43.15 Part Zagor 18.14.23 Join marc77 [0] (~marc@pub212004076150.hfc.datazug.ch) 18.19.32 Join bagawk [0] (~a78001db@labb.contactor.se) 18.20.04 # hey 18.20.24 Part bagawk 18.23.14 Join uski [0] (~uski@lns-th2-5f-81-56-234-40.adsl.proxad.net) 18.25.57 Quit [IDC]Dragon ("CGI:IRC") 18.40.50 Part pillo 18.50.51 Join _aLF [0] (~Alexandre@mutualite-3-82-67-66-128.fbx.proxad.net) 18.50.53 # <_aLF> hi 18.52.09 Join Tim[RIP] [0] (Tim_RIP_@83.73.82.114.ip.tele2adsl.dk) 18.52.18 Part Tim[RIP] 18.53.27 *** Saving seen data "./dancer.seen" 18.57.33 Quit marc77 (" HydraIRC -> http://www.hydrairc.com <- IRC has never been so cool") 18.59.38 Quit ripnetUK () 19.05.59 # Bagder: The channel's topic is a bit outdated... 19.09.08 Quit AciD (Read error: 104 (Connection reset by peer)) 19.26.35 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 19.30.44 Join [IDC]Dragon [0] (~idc-drago@pD9FF80B1.dip.t-dialin.net) 19.30.56 # <[IDC]Dragon> hi again! 19.31.22 # <[IDC]Dragon> amiconn: in case you'd like to flash: http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_ondiosp.zip 19.31.54 # <[IDC]Dragon> plus a cvs up-to-date build for the plugins, of course 19.36.43 # [IDC]Dragon, rockbox works on the Ondio ? 19.36.56 # * uski should try to keep up to date with the latest news :) 19.37.00 Quit AciD (Connection reset by peer) 19.37.01 # <[IDC]Dragon> indeed 19.37.36 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 19.37.42 # if i buy an Ondio, when will I be able to run rockbox on it ? 19.37.54 # ;) 19.38.05 # <[IDC]Dragon> uski: now 19.38.42 # <[IDC]Dragon> or rather: as soon as you'll get it delivered ;-) 19.38.44 # you have support for the NAND flash ? 19.38.52 # lol 19.39.00 # <[IDC]Dragon> it's an internal MMC 19.39.06 # oh ok 19.39.09 # so i can be changed ? 19.39.12 # s/i/it 19.39.30 # or is it a bulk MMC chip, without the connector ? 19.39.42 # <[IDC]Dragon> no, it's a chip that does MMC protocol 19.40.06 # <[IDC]Dragon> but you can use an external MMC, too 19.40.27 # ok 19.40.44 # interesting.. : 19.40.46 # :) 19.40.59 # <[IDC]Dragon> or, you unsolder the chip and hook upo an MMC internally, there's enough space 19.41.13 # even more interesting 19.41.29 # <[IDC]Dragon> would be cool: 1 GB internal, plus n*1GB external 19.41.35 # exactly :)) 19.41.41 # but a bit expensive today 19.41.50 # but maybe in a few months prices will be lower 19.42.08 # <[IDC]Dragon> I'm away now 19.42.12 # oh, by the way, is there a native US english speaker here ? i need some help for my english homeworks ;) only 5 minutes.. 19.42.16 # see you [IDC]Dragon ! 19.51.56 Quit [IDC]Dragon () 20.03.19 Join ripnetUK [0] (~mirc@82-70-100-230.dsl.in-addr.zen.co.uk) 20.12.02 Quit AciD (Read error: 104 (Connection reset by peer)) 20.21.01 Quit elinenbe (" Like VS.net's GUI? Then try HydraIRC -> http://www.hydrairc.com <-") 20.29.23 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 20.53.31 *** Saving seen data "./dancer.seen" 21.22.15 Quit ripnetUK () 21.45.08 Join scott666_ [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 22.20.00 Join [IDC]Dragon [0] (~idc-drago@pD9FF8407.dip.t-dialin.net) 22.20.17 # hi again Jörg 22.20.30 # <[IDC]Dragon> hi there! 22.20.39 # <[IDC]Dragon> flashed? ;-) 22.20.48 # ooo 22.20.57 # [IDC]Dragon, the flashing guy. 22.20.59 # [IDC]Dragon: Nope, not yet 22.21.10 # <[IDC]Dragon> :-( 22.21.23 # [IDC]Dragon: Some questions beforehand: 22.21.52 # <[IDC]Dragon> sure 22.22.07 # (1) Do you also get the strange RoLo behaviour with the archos fw on your FM? (just for comparison) 22.22.19 # <[IDC]Dragon> I haven't tried 22.22.28 # (2) Do you believe it's safe for the SP? You obviously couldn't test... 22.23.04 # (what's the SP?) 22.23.07 Quit methangas (" HydraIRC -> http://www.hydrairc.com <- irc client ownage!") 22.23.34 # uski: There are 2 different Ondio models, see the wiki article and/or archos site 22.23.37 # <[IDC]Dragon> I think it's safe. the bootloader is identical, I put the original plus Rockbox into the image (one at least should work), and the bootloader has minimon as the last resort 22.23.38 # ok 22.23.39 # ty 22.24.38 # <[IDC]Dragon> I can try the SP image, if it comforts you 22.24.55 # [IDC]Dragon: That's why I'm asking whether you get the strange rolo behaviour too. If it is so, and archos fw works for you from flash, flashing should be safe for me too 22.25.02 # <[IDC]Dragon> MAS and tuner shoudn't matter at boot time 22.25.24 # (because then the strange behaviour is caused by some init rockbox does) 22.25.34 # <[IDC]Dragon> the rolo'ed version is different from the real ROM one 22.25.58 # [IDC]Dragon: If you try the SP image on fm, chances are that it hangs on boot with both firmwares 22.26.20 # <[IDC]Dragon> I can uart-boot 22.26.50 # <[IDC]Dragon> in fact, I have to, because the plugin won't let me use the wrong one 22.26.55 # ...because the MAS init tries to start the decoding application, but the MAS memory cells to do so have different addresses. So the init waits forever 22.28.04 # <[IDC]Dragon> ok, so it may hang. was just a suggestion to ease you. 22.28.06 # If possible, just try RoLo into archos fw 22.28.59 # <[IDC]Dragon> I'll try, but fail to see why this is comforting or not 22.29.36 # Btw: I just found a way to speed up mmc writing by 50%, while still polling. Unfortunately this doesn't work for reading, have to implement DMA for speedup 22.29.56 # <[IDC]Dragon> whoo, how? 22.30.15 # Sending back-to-back by properly switching the SCI mode 22.30.45 # I did already perform a quick test, the 50% are real-world, no estimation 22.31.13 # <[IDC]Dragon> but you have a poll loop, with a certain reaction time? 22.31.20 # ooo interesting: it seems to be possible to add a tuner to the SP model, simply by soldering some components 22.31.43 # Yes, but for sending, I can use the double-buffering of the SCI if it is set to send-only 22.32.25 # So the transfer-loop housekeeping is done in the background, while the last byte is still transferring 22.33.14 # <[IDC]Dragon> nice 22.33.50 # Just optimizing a bit further (remembering the last status to avoid switching it every time) 22.34.27 # Maybe I don't need DMA for writing at all 22.34.48 # <[IDC]Dragon> if you do back to back already, then no 22.36.22 # I'm now pretty close to the theoretical max speed for writing. Theory says < ~350 kByte/s, real world is now ~330 kByte/s 22.36.43 # <[IDC]Dragon> for readig, the bitswap loop may poll the DMA pointer, running behind it, for minimum latency. 22.36.58 # <[IDC]Dragon> (sorry if you already said that) 22.37.06 # Ah, nice idea. 22.37.31 # My idea so far was to follow the block count, swapping each block as soon as it is completed 22.38.09 # <[IDC]Dragon> for multiples, yes, also possible 22.38.32 # <[IDC]Dragon> but gives a 1 sector swap latency at the end 22.38.48 # Your approach might deliver the lowest latency, but the block-wise approach may even allow to yield() once 22.39.01 # So it's not blocking the whole box 22.40.32 # <[IDC]Dragon> rolo'ing Archos s/w hangs at about 60% of its progress bar 22.40.59 # Ooops. This is different from the SP. 22.41.05 # <[IDC]Dragon> how about one yield() and then running behind the DMA? 22.41.36 # I could also yield every time the bitswap has catched up 22.41.53 # s/catched/caught/ 22.42.12 # <[IDC]Dragon> but that may happen close before the end 22.42.36 # Or even better, yield every time the bitswap has caught up, but only if > n bytes to go 22.43.08 # <[IDC]Dragon> hmm 22.43.57 # Problem: The DMA is chunked into block size anyway, with some necessary polling inbetween 22.44.12 # <[IDC]Dragon> I think if we do it at the start, we're more sure to reach it again at the end, then stick as close as possible 22.44.25 # <[IDC]Dragon> do the uncertain part first 22.45.12 # <[IDC]Dragon> what block size do you have in mind? 22.45.35 # Yes, but a complete transfer might run for several seconds. Just yielding once would not help much 22.45.35 # The block size is fixed, 512 bytes 22.45.35 # <[IDC]Dragon> ah, Ok, I was thinking in sectors 22.45.52 # <[IDC]Dragon> huh? 22.46.01 # <[IDC]Dragon> (confused again) 22.46.25 # <[IDC]Dragon> if you do multi-block, it can be quite long? 22.46.32 # <[IDC]Dragon> in one go 22.46.49 # <[IDC]Dragon> with no further command 22.46.59 # Each data block comes in with a start byte in front, which has to be polled for (worst case: 10 ms with the internal flash), the 512 bytes of data, then 2 bytes crc 22.47.51 # Multi-block transfer is unlimited with MMC, you send a start command, and the card starts transferring block after block until you send a stop command (reading) or a stop token (writing) 22.48.00 # <[IDC]Dragon> ok. Then we can poll for start, set the DMA, yield, run behind bitswapping. 22.48.15 # <[IDC]Dragon> sequence repeats for each sector 22.49.02 # gtg 22.49.12 # have a nice technical talk ;) 22.49.39 # For sector-wise, I think its better to use this sequence: poll for start, set DMA, bitswap previous block, yield, wait for end of DMA 22.50.38 # If the thread itself should do the run-behind bitswap continuously, the poll-for-next would have to be done in the ISR 22.53.33 *** Saving seen data "./dancer.seen" 22.54.26 # <[IDC]Dragon> I have to leave now 22.54.27 Quit uski ("Leaving") 22.54.38 # <[IDC]Dragon> (like uski) 22.54.46 # <[IDC]Dragon> nite! 22.54.52 Quit [IDC]Dragon () 22.54.55 # nite [IDC]Dragon 23.20.14 Quit AciD (Read error: 104 (Connection reset by peer)) 23.20.45 Join AciD [0] (~gni@longchamp44-1-82-67-133-87.fbx.proxad.net) 23.44.13 Quit gromit` ("Client exiting")