--- Log for 13.12.108 Server: niven.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 4 days and 15 hours ago 00.00.05 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-e67d2bc7a1d64a2b) 00.00.58 # Bagder: ping 00.01.08 # kugel, did you also try it with SDA #defines as 5? 00.01.32 # bertrik: the lcd driver sets pin 5 00.01.39 # unlikely that this one will owrk 00.01.41 # work* 00.01.55 # I think there's a bit of a bug in funman's patch, it passes an int pointer where a byte pointer is expected, don't know if this has any actual impact 00.02.14 # no, it doesn't 00.02.30 # I tried changing that 00.02.35 # helpo: please define "weird instructions" 00.02.37 # helpo, the wiki has the step for the e200R 00.02.58 # actually, at least you get a value other than 0 or 255, which indicates that there is an actual device somewhere responding to out request 00.03.05 Join Thundercloud [0] (n=thunderc@84-51-130-71.judith186.adsl.metronet.co.uk) 00.03.08 # helpo: we just know unknown instruction, so I guess we cannot help 00.03.25 Quit MethoS- (Remote closed the connection) 00.03.32 # * kugel was kidding 00.03.46 # * bluebrother didn't understand this joke 00.05.24 # bertrik: possibly. funman said I shall try different delays, the -4 indicates a failed read 00.05.27 # * amiconn had yet another hard freeze experience on his H180 today :\\ 00.05.44 # kugel, ah of course 00.07.06 # amiconn: On SH, using 1u for a shifted bit is more efficient? I should check the kernel. 00.07.33 # ok 00.08.00 # helpo: please explain your problem 00.09.02 Quit helpo ("http://www.mibbit.com ajax IRC Client") 00.09.32 # * gevaerts seems to not have been running a current build after all... 00.09.44 # hrm, nothing shifty there without priority 00.10.23 Join helpo [0] (i=4b3a331d@gateway/web/ajax/mibbit.com/x-f9a250d1b208f789) 00.10.38 # alright i figured out the problem 00.10.44 # my device is not supported 00.10.49 # 'Note: Rockbox doesn’t function on the newer v2 models. They can be identified by b checking the Sandisk firmware version number under Settings!Info. The v1 firmware is named 01.xx.xx, while the v2 firmware begins with 03.' 00.11.25 # i have version 2 and i was fallowig all the directions correctly but rockbox was not detecting my media player 00.11.35 # bertrik: what delay would you think is sufficient? 00.11.48 # helpo: that would indeed explain things 00.12.06 # bertrik: I also tried this one { int old = TIMER1_VALUE; while(TIMER1_VALUE + 4 > old) ; } as posted by funman a little later, same results though 00.12.09 # gevaerts: I don't know if what I committed makes any difference for mrobe100. It didn't matter for GBF but it's more correct anyway. 00.12.09 # kugel, try something very slow, i2c can't really be too slow, so perhaps increase it by a factor 100 00.12.17 # awwww, the sad part is that rockbox wont work... ;[ 00.12.54 # jhMikeS: testing now 00.13.09 # helpo: Work is underway to support the v2 models, but it's still far from ready 00.13.29 # any talk about dates? 00.13.45 # version 3 came out so i though it would be supported.... 00.14.39 # version 3 predates the first V2 code I believe, so no suprise it didn't add support 00.15.11 Quit EspeonEefi ("さよなら") 00.18.34 # jhMikeS: I can't reproduce the problem at all anymore. This seems to be a bit more random than I thought at first 00.19.59 # no check between r19409 and r19410 to see it that really mattered? 00.21.20 # I tried r19410, r19396 (latest daily), and 3.0, and it now always works 00.21.57 # maybe mrobes need some time to warm up? :p 00.22.21 # * gevaerts thought the same :) 00.23.42 Quit Thundercloud (Read error: 54 (Connection reset by peer)) 00.23.46 # * gevaerts finds something 00.24.30 Join Thundercloud [0] (n=thunderc@84-51-130-71.judith186.adsl.metronet.co.uk) 00.25.01 Join MTughan [0] (n=MTughan@134.117.165.42) 00.25.06 # jhMikeS: in 3.0, if the headphones are plugged in while booting, it works. If they are plugged in later, it fails. Now trying other versions 00.25.25 # Bagder: can we get content-type: text/plain for diff and patch files on the tracker? 00.25.52 # Just installed Rockbox on my iPod yesterday, seems to work. But I just replaced some files, and the old ones still show up. Does an iPod cache file names, does Rockbox, or is something else going on? 00.26.28 Quit gregzx ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 00.27.08 # MTughan: seems you haven't set the database to auto-update 00.27.26 # bluebrother: I just forced it to update, and the old files show up in the file view as well. 00.27.47 # Although Auto Update wasn't on, thanks for the tip. 00.28.11 # MTughan: also enable dircache, for even better auto-update (I think) 00.28.44 # gevaerts: All right, I'll look it up. 00.28.44 # I believe update and auto-update don't detect deleted files if the database is not set to "Load to RAM" 00.28.55 # didn't auto-update require dircache? 00.29.02 # or however that option is called 00.29.31 # bluebrother: no, I think it's "just" slow without 00.30.01 # Oh, I forgot to copy over the files in one directory, happened to be the one I was looking in... Others updated fine. 00.30.14 # Well, thanks for the help and database config flags at least. :P 00.33.01 # And dircache is enabled... One more thing. Is there any "soft-off" mode in Rockbox, so the player doesn't have to load from scratch every time? 00.33.22 # nope 00.33.42 # Well, Vorbis and FLAC playback override that... Thanks for the help. 00.33.46 # i know that the beast HW at least supports some sort of suspend, since the OF uses it. :/ 00.33.47 Part MTughan 00.34.00 # some of the ipods don't have a "real" off, do they? 00.34.19 # before the 3G they do not 00.34.24 # the 1st and 2nd generation don't 00.34.42 # * gevaerts now doesn't understand this bug at all anymore 00.36.42 Quit jhulst (Remote closed the connection) 00.36.53 # I could reproduce this earphone-while-booting in 3.0, r19396, and r19410 for a while, but now it suddenly always works again 00.37.12 *** Saving seen data "./dancer.seen" 00.40.16 # gevaerts: perhaps the initial state isn't read at boot? 00.40.36 # it has hp detection? 00.40.40 # yes 00.46.44 # jhMikeS: It's a little more complex than that. SH1 has no shift-by-n instructions, only fixed shifts. So libgcc provides subroutines for shift-by-n 00.47.24 # There are 3 of those: arithmetic right shift, logical right shift, and arithmetical left shift (which is identical to logical left shift of course) 00.47.24 # jhMikeS: I added FS#9628, which has all the information I know 00.49.14 # There are two points to consider. (1) Logical right shift by n is a bit more efficient than arithmetical, due to the available instructions. (2) If it is possible to get rid of any of these 3 completely, a bit of binsize will be saved, because the corresponding libgcc routine will no longer be linked 00.49.24 # gevaerts: doesn't sound like something I can address without a device. 00.50.05 # amiconn: It always uses a function or inlines simple instanes (like division). 00.50.09 # That said, with r19409 all uses of arithmetical right shift by n are already removed, so __ashrsi3 is no longer included in the rockbox core. 00.50.10 # *on ARM 00.50.15 # jhMikeS: I guess your initial state theory is not improbable. I'll see if I can get at it tomorrow 00.50.53 # amiconn: to a certain degree, we can try to make all logical shifts left, or right, by changing which operand is shifted... 00.50.54 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 00.51.20 # there are going to be expressions that doesn't work for, and it'd be a pain to go through all the shifts in RB, i'd think... :/ 00.51.46 # But of course you could still save a tiny amount of binsize and execution time on SH by using logical right shifts instead of arithmetical ones where possible 00.52.12 # I mean fixed shifts - the variable ones are already optimised this way. 00.52.43 # E.g. >> 4 translates to 2 instructions for unsigned, but 4 instructions for signed 00.53.30 # amiconn: you've explained an oddity that i encountered trying to compact the bmp reader a bit - it seemed that the 15/16 bit cases could be merged by using calculated shifts - but you say makes it clear that it would be cheaper on SH to branch the code and use fixed. 00.53.58 Quit helpo ("http://www.mibbit.com ajax IRC Client") 00.57.56 # *what* you say. 00.58.12 # Unhelpful: Depends - if the fixed shift would need too many instructions when inlined (I don't know the exact limit gcc uses), that fixed shift will also be turned in a subroutine call (though without a parameter) 00.59.33 # I agrees with Zagor about the database app (PCTOOL) - basically create a version of the sim with a tiny main() routine and accepting some commandline arguments 00.59.41 # Would be easier to maintain 01.00.10 # If you see calls to e.g. __ashiftrt_r4_NN (NN being a number from 1 to 31), this is what I mean 01.00.28 # isn't the main problem that nobody is actively maintaining the database app? 01.00.57 # we could consider adding database building to rbutil. In that case a small sim wouldn't be too helpful 01.01.08 # amiconn: urgh, that could lead to terrible space-efficiency, if all of those functions are being copied into the object at link :/ 01.01.32 # Those functions are actually interleaved code 01.02.14 # something along the lines of a series of single shifts with a label at each instruction, basically? 01.02.16 # bluebrother: Making it a, say 25-line "patch" to the sim would make it so much easier to maintain 01.02.31 # bluebrother: I don't see how the current situation makes things any easier for rbutil 01.02.53 # The whole bunch of __ashiftrt_r4_0 to __ashiftrt_r4_31 totals 41 instructions (82 bytes) 01.04.01 Quit saratoga ("CGI:IRC (EOF)") 01.04.08 # Yes, with some special cases short-circuiting >>31, >>24 (and up) and >>16 (and up) 01.05.16 Quit bertrik ("Leaving") 01.10.50 Quit culture (Read error: 110 (Connection timed out)) 01.13.40 Quit bluebrother ("leaving") 01.16.14 Join midgey [0] (n=tjross@71.238.148.140) 01.21.24 Quit Bensawsome (Nick collision from services.) 01.22.38 Quit einhirn (Read error: 110 (Connection timed out)) 01.22.42 Join Guest39166 [0] (n=Bensawso@server.lethaltechnology.net) 01.25.17 Nick Guest39166 is now known as Bensawsome (n=Bensawso@server.lethaltechnology.net) 01.27.17 # rasher: around? 01.27.30 Join perrikwp [0] (i=4aa794a0@gateway/web/ajax/mibbit.com/x-5a7ac68a713477c9) 01.28.15 # midgey: for a short while 01.28.35 # i've been looking at some of the lang updates on the tracker 01.28.42 # i'd like to get them in before 3.1 01.28.50 # wtf? Gcc uses __ashrsi3 for a variable shift (in the grelib) where clearly all involved variables are unsigned!? 01.29.49 # midgey: What else besides FS#9553? 01.29.54 # Doesn't matter much, but it's really strange behaviour... 01.30.42 # FS #9239 and FS #9587 (if we can get the patch to apply) 01.32.14 # Ah yes, I guess we might as well add the turkish one. Maybe someone should check if there's anything in the old one that's not in the new one, since it's translated from scratch 01.32.39 # I'd be happy to have FS#9587, but I've no idea what's happened to that patch 01.33.01 # i looked at fixing it manually, but it's way too huge 01.34.02 # amiconn: tbh, i really didn't understand the purpose of that transformation it performed in ata.c... it turned a left shift into a right one, and if the code had been taken as written, there wouldn't be a need for worrying about sign :/ 01.34.24 # i'm looking at the turkish one right now, it looks like some of the voice strings are gone 01.35.02 # Transforming it into a right shift saves a register 01.35.36 # err, scratch what i just said, i formed the patch backwards 01.36.56 # Anyway, gcc sometimes produces weird and inefficient code. The greylib code I was looking into (grey_mono_bitmap_part inner loop and surroundings) is just one example... 01.37.56 Join mc2739 [0] (n=chatzill@cpe-67-10-238-175.satx.res.rr.com) 01.37.59 # Rather more often than just sometimes... 01.38.27 Join domonoky1 [0] (n=Domonoky@g229069095.adsl.alicedsl.de) 01.39.36 # amiconn: saves a register at the cost of requiring a static library symbol that was unneeded before, but gcc doesn't do inter-object-file optimization yet :/ 01.40.18 # Well, one static library symbol is needed either way, just not the same. The left shift would need __ashlsi3 01.41.56 # right, and gcc can't make a smart decision about it, unless it learns to revisit that decision at link time. 01.43.59 # gcc isn't involved at all in linking 01.49.14 Join slact [0] (n=chatzill@ool-457bfab5.dyn.optonline.net) 01.49.25 Quit jhulst (Remote closed the connection) 01.50.30 # strictly binutils at that stage, right... :| 01.52.24 Quit kugel ("ChatZilla 0.9.84 [Firefox 3.0.4/2008111319]") 01.55.16 Join fdinel [0] (n=Miranda@modemcable204.232-203-24.mc.videotron.ca) 01.55.22 Quit domonoky (Read error: 110 (Connection timed out)) 01.56.43 Quit ender` (" Washing your car to make it rain doesn't work.") 01.57.54 # rasher: it looks like the turkish patch does lose a few strings 01.58.15 # it also has a lot of untranslated english 01.58.18 # midgey: Maybe it's worth it to construct a script that merges the two.. I'll look into it 01.58.41 # And remove strings that are identical to english as well 01.58.49 # well, the ids are there, they've just been replaced with english 01.59.29 # he also likes to use Title Case a lot 01.59.32 # Should be possible to get a reasonable result with an automatic merge if it compares to the english phrase as well to see which one has it right 01.59.44 # I think that's less of an issue 02.00.05 # i wasn't sure if we had a consensus on that 02.00.33 # He probably shouldn't use it, but it's not a deal-breaker 02.01.12 # Just tried the portuguese patch against all revisions of portuguese to see if my site had an old revision for some mad reason - still doesn't apply 02.01.30 # i tried a few old revisions 02.01.47 # are you sure how cases are handled in Turkish? Just saying because there are some languages that do differently (well at least German does ;) ) 02.02.00 # pixelma: I did say probably 02.02.10 # it's inconsistent at least 02.02.22 # but i have no idea how turkish works :) 02.02.41 Quit moos ("Rockbox rules the DAP world") 02.03.38 # I bet you'll find words in German which are verbs (then spelled lower case) and also nouns (upper case), but don't know a thing about Turkish... 02.03.56 Quit n1s () 02.04.03 # i suppose it's best to trust the translator 02.05.12 # maybe ask directly about this? 02.05.30 # Hrm, I think the portuguese can be mostly saved, actually 02.05.51 Quit Rob2222 () 02.06.04 # you figured out why it's not applying? 02.06.16 Quit Seed ("cu, Andre") 02.06.29 # Not really, no 02.06.48 # But most of the failing bits is all additions 02.07.07 # hey, is anyone interested in a black-background version of the EscapeBoD 2 theme for ipod 5G ? 02.08.39 # http://img205.imageshack.us/my.php?image=dump081212200532ng8.png , http://img372.imageshack.us/img372/9377/dump081212200020jj1.png , http://img126.imageshack.us/img126/2613/dump081212200104ej9.png 02.08.40 Quit domonoky1 (Read error: 104 (Connection reset by peer)) 02.09.37 # it's just luminance-inverted but with non-inverted button gradients 02.09.51 # (and minor tweaks-to-taste) 02.12.56 # does that need multifont, or is the small text all sysfont? 02.13.42 # neither 02.13.42 # Looks like sysfont 02.13.50 # (yteah, it's a sysfont) 02.14.04 # (sorry, the "neither" was to adifferent conversation) 02.18.43 Join Rob2222 [0] (n=Miranda@p4FDCF076.dip.t-dialin.net) 02.21.09 Quit Chronon ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 02.22.56 Quit Nico_P (Remote closed the connection) 02.23.40 Quit midgey () 02.31.35 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 02.37.13 *** Saving seen data "./dancer.seen" 02.41.26 Quit XavierGr (Nick collision from services.) 02.41.37 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 02.47.48 # * rasher fixed the portuguese patch 02.48.31 # Still no flaming idea what went wrong 02.49.09 Quit fdinel ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 02.49.13 Quit lasser (Read error: 145 (Connection timed out)) 02.50.36 Quit herrwaldo ("Konversation terminated!") 02.53.17 # gevaerts: what's the cleanup function for usb storage? I need to undo audio_get_buffer. 02.54.24 Join mib_lx2l6kdh [0] (i=d8ef5c7f@gateway/web/ajax/mibbit.com/x-d0cda7cc7db03e8d) 02.54.30 Nick mib_lx2l6kdh is now known as MarcGuay (i=d8ef5c7f@gateway/web/ajax/mibbit.com/x-d0cda7cc7db03e8d) 02.55.09 # jhMikeS: LIttle problem with the keyclick/recording fix. It doesn't reactivate after you leave the recording screen. 02.55.25 # Only by restarting playback does it come back into effect. 02.55.33 # MarcGuay: I was just fixing that right now. 02.55.44 # Roger. 02.57.25 # Is it considered normal that if you scroll quickly it doesn't click for every entry you pass? (with Keyclick Repeats set to Off, at least) 02.58.05 # if repeats are off, yes it's normal 02.58.30 Quit mofux (Read error: 104 (Connection reset by peer)) 03.01.39 Join kharo1 [0] (n=teemu@a88-114-255-186.elisa-laajakaista.fi) 03.02.46 Quit kharo (Read error: 110 (Connection timed out)) 03.03.57 Join midgey [0] (n=tjross@71.238.148.140) 03.05.42 Part toffe82 03.08.59 # * jhMikeS wonders if wheel messages shouldn't just ignore that setting 03.09.01 # midgey: Got it. No idea what happened though. 03.09.11 # i noticed 03.09.33 # i was trying mess with the patch by hand. i'm not sure what was wrong 03.09.45 # If you check the diff, you see that it's vaguely different from the one he posted in some "from"-lines 03.10.13 # Like there were edits to the original portugues.lang, which seems odd though 03.10.14 # Oh well 03.11.05 Join MTughan [0] (n=MTughan@134.117.165.42) 03.11.10 # odd, i tried copy and pasting from the original lang file into the diff and rebuilding it manually. didin't seem to help 03.11.23 Join Xillius [0] (n=Xil@ip-145.net-81-220-95.rev.numericable.fr) 03.11.28 # hello guys 03.11.41 # Rockbox can play FLAC files, right? Because it doesn't seem to be. 03.12.00 # anyone knows about an xm/mod plugin support for rockbox sansa ? 03.12.29 Quit jeffdameth (Read error: 113 (No route to host)) 03.13.59 Join jeffdameth [0] (n=jeff@dyndsl-095-033-088-186.ewe-ip-backbone.de) 03.14.16 # MTughan: can you be a bit more specific than that? it supports flac on all targets with software decoding, as far as i know. 03.14.59 # I'm running an iPod 5th gen (aka Video), with the latest stable of Rockbox. The FLAC files were transcoded from AIFF by ffmpeg. 03.15.27 # Rockbox just seems to skip by all the files in the folder without actually playing any of them. 03.15.36 # Xillius: mod should play fine... 03.16.26 # and there are no messages displayed at all about what happens? in my experience, when it fails to decode something, it says why... 03.16.41 # It just stays on the frontend. 03.17.25 # Displays the file name for the title, but the artist and album fields read "(root)". 03.17.50 # scorche 03.17.56 # by default it should play it ? 03.17.57 # MTughan: do you know how your .flac files are tagged (which tag format)? 03.18.13 # pixelma: Not sure. I used VLC to save the metadata. 03.18.17 # Xillius: mod support was added back in May 03.18.47 # yeah havent updated since then... 03.18.50 # thanks for the info 03.19.23 # any idea about xm/it ? 03.19.43 # Xillius: next time please update before you come in here to ask... 03.21.45 # pixelma: Does the container format matter to Rockbox? I used OGG. 03.22.26 # definitely, rockbox generally only supports whatever the "native" container is for a codec 03.22.50 # Xillius: i am not sure about xm or it...i know there is a patch in the tracker though 03.23.03 # Unhelpful: As I know, OGG is the one used with FLAC. 03.23.24 # MTughan: no, flac has it's own native format. 03.23.31 # http://flac.sourceforge.net/faq.html#general__native_vs_ogg 03.24.08 # the ogg container thing is something that got added when it was incorporated into the xiph codec family, and there's really no benefit from it except for slightly larger files that play on fewer devices. 03.24.09 # Thanks scorche. 03.28.24 Join Llorean [0] (n=DarkkOne@adsl-65-68-72-166.dsl.hstntx.swbell.net) 03.28.25 # i'm trying to register on the rockbox TWiki, and it's giving me a bad error when I enter the validation code 03.28.46 # Hmm, using the FLAC container still doesn't seem to be working. 03.28.51 # something about it not having write permissions 03.29.57 # how did you convert them? 03.30.17 # I used ffmpeg. Want the output options? 03.31.13 # if you named the output file .flac, and didn't go out of your way to force a container format, it should be right. why not use the reference encoder, though? 03.31.19 Quit Thundercloud (Read error: 54 (Connection reset by peer)) 03.31.33 # Where's the reference encoder? I just used ffmpeg out of convenience. 03.31.59 # I guess off the FLAC SF.net page, eh... 03.32.07 # the one that comes from flac.sf.net. generally the binary is named "flac", or "flac.exe" on windows 03.32.23 # I'm running on OS X, so a BSD underbed. 03.33.08 # i'm not sure what the "right" way is to get flac installed on OS X 03.33.30 # There seems to be command line tools available. I'm downloading them now, will explore. 03.33.47 # good luck 03.34.21 # we should probably move this to #rockbox-community, it's become a conversion issue, now that we've established that the problem was probably the ogg container. 03.34.50 # Maybe. They play fine in VLC. 03.35.34 # yes, ogg flac will play fine in vlc, to my knowledge, but it won't in rockbox 03.36.01 # Yeah, I could see that. I'll see how far I get with the reference encoder. 03.41.26 # Nice, that seems to work. Thanks Unhelpful. 03.41.35 # Even keeps the metadata from the original... 03.42.02 # glad it worked. enjoy your rockbox :D 03.42.14 # I imagine I will... 03.43.17 # ...so any ideas on TWiki erroring out on registration? 03.46.24 Quit kharo1 (Read error: 60 (Operation timed out)) 03.49.06 Part MTughan 03.49.44 Join kharo [0] (n=teemu@a88-114-255-186.elisa-laajakaista.fi) 04.01.49 Quit Xillius () 04.03.53 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 04.04.50 # * jhMikeS hates it when he thinks of a better, cleaner solution to something _after_ committing a bunch of changes. argh! :\ 04.09.38 Quit Rob2222 () 04.10.01 Join blkhawk- [0] (n=blkhawk@g227020033.adsl.alicedsl.de) 04.10.58 Quit blkhawk (Read error: 60 (Operation timed out)) 04.10.59 Nick blkhawk- is now known as blkhawk (n=blkhawk@g227020033.adsl.alicedsl.de) 04.14.10 Quit MarcGuay ("http://www.mibbit.com ajax IRC Client") 04.19.08 # TWiki detected an internal error - please check your TWiki logs and webserver logs for more information. 04.19.10 # RCS: failed to create file path: Permission denied 04.20.57 Join CaptainKewl [0] (n=jason@cpe-68-173-40-122.nyc.res.rr.com) 04.36.28 Join ameyer [0] (n=ameyer17@adsl-75-57-183-54.dsl.emhril.sbcglobal.net) 04.37.16 *** Saving seen data "./dancer.seen" 04.51.47 Join Darksair [0] (n=user@58.192.38.181) 04.55.38 # ..maybe i just neeed write access or something?... 04.55.41 # who do i ask for that? 04.57.46 # you need to be registered to *get* write access... 04.58.27 # maybe i did register... 04.58.51 # i can't tell, it just gives me a blank plage when i try to attach stuff 04.59.39 # oh, now, for that, you do need write access 04.59.56 # you really don't know if you're registered or not? :/ 05.00.43 # well, it gave me that error when i entered the emailed validation code 05.01.12 # but it didn't say "GTFO" when i logged in. just blank pages when i try to attach, it seems... 05.01.31 # if you're able to log in, i would say you're registered. 05.03.44 # might you be able to point me to the login page? 05.04.26 # ooh, wait 05.04.34 # it's giving a normal Acess Denied error now, i think... 05.05.20 # try to edit a page? 05.05.48 # http://www.rockbox.org/twiki/bin/oops/TWiki/WikiName?template=oopsaccessdenied;def=topic_access;param1=change;param2=access%20not%20allowed%20on%20web 05.05.56 # that looks stateless, so i think the link'll work 05.07.04 # did you register with first+last name, as suggested? 05.07.08 Quit miepchen^schlaf (Read error: 110 (Connection timed out)) 05.07.21 # yes, got a validation email and everything 05.07.27 # try http://www.rockbox.org/twiki/bin/view/Main/FirstnameLastname 05.07.39 # (obviously with your names) 05.07.50 # then it doesn't exist 05.08.30 Join blkhawk- [0] (n=blkhawk@222-154-18-175.jetstream.xtra.co.nz) 05.09.01 Quit Darksair ("Use the Force, Luke!") 05.10.05 # hrm. maybe try the email provided, if you seem to be unable to complete your registration? http://www.rockbox.org/twiki/bin/view/TWiki/TWikiRegistration 05.10.30 Quit blkhawk- (Client Quit) 05.11.12 Join blkhawk- [0] (n=blkhawk@222-154-18-175.jetstream.xtra.co.nz) 05.12.05 # i'm not sure what you mean 05.12.59 # if that page doesn't exist, you're not a registered user. there's an email at the bottom of the registration page for issues. 05.13.23 # ah, that 05.13.32 # guess that's what i'll do then... 05.13.35 # thanque. 05.14.10 # he's on irc as well, so you could ask Bagder... probably should take it to the community channel, though, this is getting less and less about rockbox itself by the minute 05.14.28 Quit blkhawk- (Client Quit) 05.14.35 # yep... 05.16.49 # slact: What's your wiki name? 05.17.23 # LeoP . Against the rules for the moment, i know... 05.18.06 # (i don't much care if the name gets deleted, i'm just trying to post a theme) 05.18.19 # slact: Per the registration page, you have to ask for write permissions in this channel 05.18.32 # slact: http://www.rockbox.org/twiki/bin/edit/Main/WebHome?t=1229141862, Step 2 05.18.49 # Register with the correct name and I'll give you write access 05.18.53 # yes, but TWiki gave mea a mean error when i entered the activation code provided in the email 05.19.09 # so i wasn't sure if it was time for Step @ yet. 05.19.37 # and you're quite unlikely to get them if you're not going to follow the registration rules. we need to know who actually contributes things to the wiki, especially stuff like themes, primarily because of copyright issues. 05.19.52 # slact: Try registering with the correct name and I'll give you access, we'll see if that works 05.21.04 # very well. http://www.rockbox.org/twiki/bin/view/Main/LeoPalmer 05.23.05 # ( that is, my wiki username should be LeoPalmer ) 05.25.29 # You need to go through registration with that name. 05.26.02 # i did. 05.26.48 # Have you received a confirmation email for your attempt to register with the name "LeoPalmer" (NOT your LeoP attempt) yet? 05.27.07 # Llorean: yes...see back-log.. 05.27.32 # scorche: He responded to jhulst's "What's your wiki name?" question with "LeoP" though 05.28.21 Join Darksair [0] (n=user@58.192.38.181) 05.29.38 Join sajes_ [0] (n=sajes@66.82.244.88) 05.30.42 # scorche: I just wanted to be sure the registration with the new name was actually complete. 05.31.53 # well, that's what's in question 05.32.10 # slact: So did you receive a confirmation email for the LeoPalmer name? 05.32.13 # yes. 05.32.27 # and entered the validation code. and it gave me a mean error. 05.33.10 # TWiki detected an internal error - please check your TWiki logs and webserver logs for more information. RCS: failed to create file path: Permission denied 05.33.54 # trying to enter the code a second time, however, sends me to a normal "code invalid" page. So clearly it did /something/, just not sure what. 05.33.59 # * scorche nods and sits around for certain people to wake up 05.40.04 Join LambdaCalculus37 [0] (n=rmenes@rockbox/staff/LambdaCalculus37) 05.40.08 Quit amiconn (Read error: 60 (Operation timed out)) 05.40.47 Join amiconn [50] (n=jens@rockbox/developer/amiconn) 05.46.08 Quit sajes (Read error: 110 (Connection timed out)) 05.47.38 Join gregorovius [0] (n=diego@host212.190-30-156.telecom.net.ar) 05.55.57 Join pixelma_ [0] (n=pixelma@rockbox/staff/pixelma) 05.55.59 Quit pixelma (Read error: 110 (Connection timed out)) 06.00.22 Quit LambdaCalculus37 ("Ka-chunka") 06.02.02 Quit n17ikh|Lappy () 06.05.34 Quit mc2739 ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 06.07.57 Quit XavierGr (Read error: 60 (Operation timed out)) 06.12.45 # well, anyway, http://slact.net/miscellanea/EscapeBod-black.zip is the theme i wanted to upload. If someone else cares to do it, be my guest. 06.28.56 Quit aarcane ("Leaving") 06.31.56 Quit GodEater (D-lined) 06.33.32 Quit perrikwp (D-lined) 06.37.18 *** Saving seen data "./dancer.seen" 06.53.05 Quit Darksair (Connection timed out) 06.56.19 Quit Aurix_Lexico (Read error: 110 (Connection timed out)) 07.00.19 Join perrikwp [0] (i=4aa794a0@gateway/web/ajax/mibbit.com/x-b25e87b63811e957) 07.04.07 # amiconn: so, you said coldfire has a div instruction, and arm does not. i see that sh1 does? what about a different brightness() for arm, with three multiplies and a shift instead of two and a div? 07.04.28 Join crackmonk [0] (n=crakmnky@adsl-68-126-42-204.dsl.pltn13.pacbell.net) 07.14.29 Quit esthar ("KVIrc 3.4.0 Virgo http://www.kvirc.net/") 07.14.43 Quit crackmonk (Remote closed the connection) 07.14.47 Join n17ikh|Lappy [0] (n=n17ikh@130-127-73-84.lightsey.resnet.clemson.edu) 07.42.49 # hm, what's "Eraser" build? 07.44.21 Join Rob2222 [0] (n=Miranda@p4FDCF076.dip.t-dialin.net) 08.04.19 Join Duchess [0] (n=Duchess@bas16-montreal02-1177684057.dsl.bell.ca) 08.07.24 Join Seed [0] (n=ben@bzq-84-108-232-45.cablep.bezeqint.net) 08.08.01 # Hi I'm having an issue using ipodpatcher, if someone feels up to helping me out. 08.12.24 # Duchess: Did RBUtil fail to work for you? 08.15.09 # Well, heh, thing is I'm actually trying to use it as a general tool not really related to rockbox, but I figured since I found the download off the rockbox website, I would ask you guys about my issue. 08.15.10 Join Rob2223 [0] (n=Miranda@p4FDCDBBA.dip.t-dialin.net) 08.16.32 # Duchess: Well, it's much less likely anyone will be able to help with questions about using it for things it's not meant to. 08.17.03 # No no, I'm not trying to use it inappropriately, ipodpatcher *is* a general-purpose tool 08.17.36 # I'm trying to use it to backup firmware. 08.17.50 # From one of the list of supported iPods? 08.17.56 # Yup. 08.17.59 # So what's the problem? 08.18.49 # Is it okay if I copy-paste the output? 08.18.58 # use a site like pastebin.ca 08.19.09 # The channel guidelines are pretty clear what to do about multi-line pastes. 08.19.47 Quit Rob2222 (Read error: 60 (Operation timed out)) 08.19.59 # http://pastebin.com/d5f15a306 08.20.22 # Did you try "sudo ./ipodpatcher" instead then? 08.20.34 # I tried with no luck 08.20.56 # It gives you the exact same message about permissions even when run with su? 08.22.08 # No it gets stranger if I do it that way, for some reason it won't even recognize the command 08.22.50 # Are you doing it from the location the executable is actually located in, or at least typing the correct path to it? 08.23.29 # I type the right path, yeah. 08.23.45 # If it doesn't recognize the command, you're typing something wrong. 08.23.51 # Since that's your shell reporting the error, and not iPodpatcher. 08.24.06 Quit midgey () 08.24.07 # I might be, though I'm just stumped why it's not working at the outset anyway. 08.24.16 # Because you don't have the required permissions. 08.24.18 # It can't work without them. 08.24.55 # Huh. Weird. 08.25.04 # What's weird about it? 08.25.13 # There are certain restrictions OSes put on what applications can do. 08.25.33 # normal users do not have acces to raw disk devices, normally. that would be insecure and dangerous 08.25.46 Join write_erase [0] (n=Olivier@royale.aixmarseille.com) 08.26.06 # True, I think the main issue is that I'm doing this at almost 2:30am, haha. 08.26.19 # Hi... do rockbox support remote control serial protocol ? 08.26.40 # strangely, I *think* my debian setup gives me raw disk access *shudder* 08.27.01 # write_erase: What player do you have? 08.27.33 # ipod 3rd gen ... which has serial IIRC 08.28.05 # There's no support for it at all in Rockbox. 08.28.52 # There is manual here: http://www.rockbox.org/manual.shtml -> iPod 3rd gen 08.29.02 # Why not supported ? 08.29.06 # No support for *serial* on it. 08.29.13 # Alright well, thanks for the help guys, I'll tinker with this for a while and if it doesn't work I'll give it up. 08.29.18 # * Duchess waves 08.29.20 Part Duchess 08.29.38 # you mean the rockbox firmware don't support serial remote control ? 08.29.47 # Not on the 3G iPod. 08.29.47 Quit denes_ (Read error: 110 (Connection timed out)) 08.30.02 Join denes_ [0] (n=denes@pool-0598.adsl.interware.hu) 08.30.11 # not 3G ipod but ipod Gen3 08.30.25 # 3G means "3rd Gen" 08.30.27 # ok 08.30.43 # does the remote works on other devices ? 08.31.03 # Some devices with remotes have support, yes. 08.31.15 # Plus there's some experimental work being done for newer iPods. 08.31.46 Quit gregorovius () 08.33.04 # Where can I get the feature chart ? so I can see what' supported ? 08.33.24 # What targets support lcd_set_{back,fore}ground? 08.34.31 # write_erase: What feature chart? 08.34.47 # There's just the features in the manual 08.35.07 # J-23: I believe any that are more than 1bpp, but I'm not certain. 08.35.23 # should it work on simulator? 08.35.33 # Yes. 08.35.40 Quit jhulst (Remote closed the connection) 08.35.48 # * J-23 thinks what is he doing wrong 08.35.50 # * amiconn points J-23 to the helpful wiki 08.36.15 # http://www.rockbox.org/twiki/bin/view/Main/GraphicsAPI 08.37.11 # write_erase: you could try here: http://www.rockbox.org/twiki/bin/view/Main/DeviceChart 08.37.20 *** Saving seen data "./dancer.seen" 08.50.53 # I set colors with lcd_set_{fore,back}ground, but I still all colors are as in theme 08.56.35 Join lucent [0] (n=eshattow@97-112-225-119.chyn.qwest.net) 08.56.57 # I own a Sansa Clip and Sansa Fuze 8GB now :) 08.57.17 # is either hardware of interest to capable developers? 08.57.19 # amiconn: it's been bumped off the bottom by all the bugfixing, but the gain was on the order of 4.5KB on color targets, and i think closer to 1.5-2KB on greyscale 08.57.23 # I don't need both 08.57.34 # Unhelpful: My point is that we have smooth scaling, we should offer it on all targets that can afford it 08.57.47 # The greyscale targets certainly belong to this group 08.58.19 # you think so? it wouldn't be hard to code that, a quick clone-and-hack job. 08.58.20 # And while the greyscale LCDs are merely 2bpp, you get a higher effective depth through dithering in the wps, but that's not my only point 08.59.00 # If the bmp reader + scaler would allow a pluggable output stage, coverflow could use the greylib on greyscale targets, for an effective depth of ~7bpp 09.00.26 # amiconn: doesn't yet, but that's a matter of adding a function pointer w/ the same signature as resize_on_load to bmp_read_* 09.00.31 # The greylib currently has no bmp loader, a fact that I wanted to change for a long time already :/ 09.01.00 # Hmm, I'd prefer the data post-resizing 09.01.21 # I.e. load, smoothly resize, and then pass the data to the output stage 09.01.42 # what i'm saying is you could have an 8-bit greyscale resizer in pluginlib 09.01.43 # Think of the greylib as just another pixel format 09.02.24 # Actually the simplest one you can think of. Just 8bpp in natural order. 09.02.34 # right now the inside loop of the scalers is direct-output in a target format... although, they do both generate whole lines at a time, we could add an output_line function... 09.02.48 # AH, hmm 09.03.05 # sorry, actually, nearest doesn't, but you're talking about doing away with nearest, pretty much. 09.03.22 # Not sure whether it's worth having this in the core then, but imho it would then make sense to share the source file between core and pluginlib 09.05.03 # well, if we support smooth scaling on greyscale targets, there's really only one scaler, then. we can pass an output_line function in that copies lines to the target bitmap 09.05.30 # the one in core can be 2bpp or 16bpp, depending on target, and an 8bpp greyscale can be in pluginlib 09.05.38 # weird, I see a patch supporting radio mode on Sansa Clip - I thought that rockbox wasn't able to run on the Clip though due to limited resources? 09.05.54 Quit gevaerts (Nick collision from services.) 09.06.05 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 09.06.09 # lucent: Rockbox is actually coming along nicely on the clip 09.06.30 # wha? :) I would like to try, if it is "reasonably" safe to revert 09.06.40 # You'll need to compile the tools and stuff for yourself. 09.06.43 # my Sansa Clip 2GB is now my 2nd player 09.06.51 # yeah I could figure that part out 09.06.57 # I'm surprised though 09.07.13 # how does the interface work on that tiny little display :P 09.07.26 # It's still just a list of text, like it is on anything else. 09.07.31 Nick pixelma_ is now known as pixelma (n=pixelma@rockbox/staff/pixelma) 09.07.41 # thanks for that info 09.07.57 # has it gotten far enough to play back audio? 09.08.21 # we could use exactly the *same* scaler if we always scale in color, and then convert to greyscale only at output... i wish i'd kept my multiply counts for the color scaler, i could try to figure which was more efficient :/ 09.08.24 # lucent: A little bit. 09.08.30 # * lucent smiles :) 09.08.30 # It usually crashes after a short period of playing 09.08.53 # if another user testing the code is handy, I will try 09.09.01 # Unhelpful: I'd think that scaling in greyscale would be faster 09.09.18 # lucent: We need more people actually working on it. Investigating the code and figuring out where the crashes are happening, and why 09.10.22 # oh, I'm a good bug tester but not much of a coder then 09.10.25 # amiconn: well, remember, brightness costs 3 multiplies, though... and the smooth scaler doesn't actually have any per-input-pixel multiplies, right now. 09.11.02 # hmm 09.11.13 # That'd be an interesting comparison 09.11.29 # trying to find out how to check out the rockbox code that I would need to build to get a clip firmware 09.11.42 # where on the rockbox website is that information mentioned? 09.12.16 # i need to do some work here, but i'll be back in a bit, and recount those multiplies first :) 09.12.30 # lucent: If you just follow the link to the wiki, the main page should contain links to an awful lot of useful pages. 09.13.08 # Llorean: wiki, got it. thanks 09.13.47 Join n1s [0] (n=nils@rockbox/developer/n1s) 09.14.32 Join blkhawk- [0] (n=blkhawk@222-154-18-175.jetstream.xtra.co.nz) 09.17.12 # http://www.rockbox.org/twiki/bin/view/Main/HowToCompile is what I am looking for :) 09.21.24 # Llorean: is Clip an ARM core? 09.21.59 # yes 09.22.08 # great! 09.26.06 Quit blkhawk- ("Caught sigterm, terminating...") 09.26.08 # n1s: I have a nice FM menu item on my beast but I can only listen to God on it (cosmic background radiation). :d 09.26.41 # jhMikeS: hmmm 09.27.42 # i think i get worse reception on the beast then the h300 but it's hard to tell because fm is kind of weak here 09.27.44 # hmmm, weird. I take that back, it's tuning now. :\ 09.27.55 # oh :) 09.29.10 # Still, strange volume leaps when switching regions. 09.29.49 # jhMikeS: that is the softmute, when it decides it is not tuned to a valid station it drops the volume by 16dB so it's actually a feature 09.30.34 Join GodEater [0] (i=c2cbc962@gateway/web/ajax/mibbit.com/x-f579ea9151f1c249) 09.30.49 # but it is kind of weird because it is supposed to set a bit to tell if you are on a valid station but that seems to never get set... 09.30.50 # But it is tuned. It goes silent or quiet, then when I go back to the screen, it pops back up. 09.33.24 # n1s: Nice job on the tuner though. Don't let my probing for strange behavior say otherwise. 09.34.01 # strange, i don't think i've had that but it seems very position dependent so moving just a few cm can mean going fron clear signal to just noise 09.34.18 # jhMikeS: thanks, and feel free to probe :) 09.35.17 # amiconn: ok, the color downscaler is 9*dw*sh + 12*dw*dh multiplies 09.35.55 # i hope i can get proper seeking/scanning working soon but therere's so much to do before christmas :/ 09.36.10 # calling brightness per output pixel would make that 9*dw*sh +15*dw*dh multiplies 09.37.12 # n1s: tuning is a bit sticky. you set the proper GPIO settings on the tuner? 09.37.23 # converting the scaler to work in 8bpp greyscale, and calling brightness on input pixels, means 3*sw*sh + 3*dw*sh + 5*dw*dh 09.37.40 # erm, sorry, last term is 4*dw*dh. 09.38.27 # jhMikeS: not sure really, from what i understand the gpios are only for interrupts from the tuner, which we currently do not use 09.38.28 Quit gromit`` (Read error: 110 (Connection timed out)) 09.38.31 # if you didn't then that would explain why the MCU GPIO pins don't register correctly 09.38.55 # or maybe i don't understand wht you mean :) 09.39.49 # for input dimensions 2x the output dimensions, that's 2/3 as many multiplies for color->grey->scale, instead of color->scale->grey 09.40.09 # n1s: You have to set the GPIO lines on the tuner in its registers to be functional was all I was saying. You're probably familiar with that alread. 09.41.15 # jhMikeS: yeah, ok, as i said i only think they are used for interrupts, do you think setting them up will affect tuning? 09.41.38 # at 4x, color->grey->scale is about 25% more multiplies... but i hope we're not going to make greyscale targets do that, anyway. 09.42.20 # n1s: so that loop isn't needed and it could get rid of the sticky feeling from the UI 09.43.12 Quit Seed ("cu, Andre") 09.43.27 # jhMikeS: aha, yes it can indeed, bertriks patch in FS9611 does this and it works fine, or at least the same 09.44.15 Part tkooda ("thanks!") 09.44.22 # hmmm. and we can avoid i2c traffic to check the mono/stereo bit. 09.45.03 # * jhMikeS listens to The Doors on 94.7 09.45.32 # Some stations wouldn't come in at all on the Clip radio patch, for me. 09.49.38 # n1s: we definitely need the volume ranges combined to match pcm. -54db is pretty loud still. 09.50.15 # For the record, I just read some of the backlog and just wants to point out with the "read audio data from flash" (FS9322?) patch, the clip is reasonably stable, although there still appear to be some issues with the PCM driver and the sd driver 09.50.32 # jhMikeS: yes, i just didn't know which volume to use :/ 09.50.50 # will look at it later, gtg now 09.51.53 # n1s: The volume attenuates the ADC after min is hit for the HP amp to get a 96dB range. It could actually be much larger than that. 09.52.07 # *DAC 09.53.47 # hrm, all of the in-the-loop code would be cut to nearly 1/3 the size, too, i'd imagine... which would bring the smooth scalers on greyscale in line with the cost of the NN scaler now 09.54.50 # * jhMikeS wonders if a 190dB volume range on the beast would be excessive? 09.56.59 Join rvvs89 [0] (n=ivo@pdpc/supporter/base/rvvs89) 09.58.05 # jhMikeS: pretty much 09.59.27 # jhMikeS: Is most of that downward? 10.00.13 # if full scale is 0 dB, -186dB would be full scale * 2^-31 10.00.40 # Llorean: -184 to +6 if DAC+HP are combined 10.00.52 # jhMikeS: What's the current range? 10.00.57 # -190dB would be full scale*10^(-19) 10.01.07 # Llorean: -90 to +6 10.01.36 # I guess it more or less boils down to "which is most similar to what we do on other players?' 10.01.57 # and would be percieved as approximately full scale * 2^-19 IIRC 10.01.58 # Llorean: The beast is really a loud player though 10.02.03 # This is true. 10.02.15 # I know the lower limit on the F is just a little higher than I'd personally like it to be, even with my replaygained music. 10.02.34 # I don't really see the harm in offering users ridiculous lows, since nothing forces them to go that far down anyway. 10.03.03 # maybe a bit of binsize or ram usage, although probably not 10.03.07 # The line can go in effect -104.25 to +6 combined with HP so it's a good range 10.03.16 # ameyer: The beast is a beast in terms of RAM too. 10.03.51 # and I'd imagine it'd be miniscule anyway 10.04.02 # even on something like the clip with 2 MB 10.08.11 # Llorean: Really, I've wondered about limiting the maximum on the beast. It's just ridiculously loud at the upper end and my headphones aren't even terribly efficient. 10.11.12 # jhMikeS: People on other players ask us occasionally if we can make it louder. 10.11.26 # I say we give them the freedom to deafen themselves, if they feel they really must. 10.12.52 # jhMikeS: don't forget car adaptors and the like - one of ours is quite quiet, and needs either the beast up to -10, or the stereo up well above where it's used for other channels. 10.12.56 # I blasted myself by mistake once though just because I forgot I had it cranked. :p 10.13.19 # jhMikeS: fixed.cfg =P 10.14.24 Join gregzx [0] (n=chatzill@dtc77.neoplus.adsl.tpnet.pl) 10.17.34 Join lasser [0] (n=chatzill@Waaa2.w.pppool.de) 10.21.08 Join bertrik [0] (n=bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 10.24.27 # * pixelma wonders whether fixed.cfg is described in the manual or at least in the wiki 10.24.52 # It wasn't last time I looked, but that was some time ago. 10.25.12 # It's one of those things that went from "first idea" to "final form" in like, 30 minutes of discussion in here. 10.25.13 # it is 10.25.25 # With a few really bad ideas in between. 10.27.06 # in "Advanced topics - Specifcations for .cfg Files." 10.28.44 # and weird... when I c-p parts of the manual. all lower case "f"s are lost 10.32.28 # Wasn't there an issue like that previously? 10.33.10 Join bmbl [0] (n=Miranda@unaffiliated/bmbl) 10.37.19 Quit rvvs89 ("leaving") 10.37.21 *** Saving seen data "./dancer.seen" 10.38.20 # amiconn: as far as brightness itself goes, i'm inclined to think we keep the existing version, with the div, on SH, where it's smaller code and we don't dither or have >1bpp output. we could probably go even more low-quality, really. 10.39.49 # Did you compare sizes on SH? 10.40.17 # yes, >>8 is more code, i'm guessing the extra multiply is what puts it over. 10.42.21 # the >>4 version is smaller on arm than >>8, we should probably use that on PP targets if the main display is color, and the >>8 version on greyscale main-display targets 10.43.42 # i don't know how that split works out on coldfire... we should probably stick to whichever is decent and smallest there, as well, *if* the main screen is color 10.44.49 Join esthar [0] (n=esthar@student164-247.hampshire.edu) 10.45.42 # Llorean: that was with the textsc function (small caps) which was used for settings (leading to a broken search in some pdf viewers and bloated html), bluebrother made the manual build with some other function and font and said this fixes it. For me all lower case "f"s are lost, no matter if they are in simple text, headline or else. When pasting into Notepad++ with enabled view of control characters I get an "FF" instead 10.45.54 Join MethoS- [0] (n=clemens@host-091-097-240-161.ewe-ip-backbone.de) 10.46.01 # now 10.47.06 Quit MethoS- (Remote closed the connection) 10.48.21 Join stoffel_ [0] (n=sfr@p57B4DF1B.dip.t-dialin.net) 10.50.36 Join seraph [0] (n=seraph@pD9E225D4.dip0.t-ipconnect.de) 11.02.29 Join AndyI [0] (i=AndyI@212.14.205.32) 11.13.08 Quit AndyIL (Connection timed out) 11.20.27 Join hobbs [0] (n=nandrew@p3m/member/hobbs) 11.24.05 Join JdGordon [0] (n=jonno@rockbox/developer/JdGordon) 11.25.26 # bertrik: I tried FS 9611 briefly, and at least one frequency didn't seem to come in at all. Strangely ones both above and below it did. 11.25.36 # And it's one I can pick up quite well in the OF. 11.28.17 Quit gregzx ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 11.28.55 # Llorean, weird. I don't have an explanation for that. 11.29.01 Quit reacocard (Read error: 104 (Connection reset by peer)) 11.29.25 # I have the feeling I'm still missing something in the initialisation. 11.29.52 Join gregzx [0] (n=chatzill@dtc77.neoplus.adsl.tpnet.pl) 11.30.07 # * amiconn has the impression that the tea5767 is a far better tuner than the sii one 11.33.43 Join reacocard [0] (i=reacocar@saga.silenceisdefeat.org) 11.37.16 # I can't compare because the only other target with a tuner I have is a c200v1, which has a lvXXXX tuner 11.37.40 # at least the si470x is easy to use, the one in the c200 is a nightmare 11.38.25 # my last week's comparison between OndioFM (TEA) and c200 (LV) was that the Ondio had a better reception 11.39.14 # and the auto search function gave "cleaner" results 11.40.03 # (from a user's perspective) 11.40.11 Join fredddy [0] (n=freddy@p3E9E3203.dip0.t-ipconnect.de) 11.41.38 Join ender` [0] (i=krneki@foo.eternallybored.org) 11.42.26 Join culture [0] (n=none@cpc1-bele3-0-0-cust658.belf.cable.ntl.com) 11.48.55 # amiconn: at a guess, i'd say greyscale scaler is maybe 1-2wk worth of spare-time work to get right, based on how the color scaler went. maybe less, because i'm just adapting, maybe more, because of holidays. but i'm starting on it in a branch, and we'll see where it goes :) 11.51.10 Nick fxb__ is now known as fxb (n=felixbru@h1252615.stratoserver.net) 11.51.59 Join Schmogel [0] (n=Miranda@p3EE217D7.dip0.t-ipconnect.de) 11.54.53 Quit stoffel_ ("leaving") 11.58.02 Join moos [0] (n=moos@81-66-158-133.rev.numericable.fr) 12.01.05 Join miepchen^schlaf [0] (n=miepel@p579ECE80.dip.t-dialin.net) 12.01.36 Join mofux [0] (n=quassel@dslb-092-078-049-119.pools.arcor-ip.net) 12.02.26 Quit _lifeless (Remote closed the connection) 12.02.37 Join __lifeless [0] (n=lifeless@90.151.46.135) 12.07.40 # Llorean, what frequency was that. On my clip, I don't hear anything around 96 MHz, not even noise. The received signal strength indicator shows a fairly strong signal. I can imagine that the radio is picking up a clip clock frequency or a harmonic thereof 12.10.24 Quit Schmogel (Read error: 104 (Connection reset by peer)) 12.11.32 Join robin0800 [0] (n=robin080@cpc2-brig8-0-0-cust394.brig.cable.ntl.com) 12.15.46 Join Schmogel [0] (n=Miranda@p3EE217D7.dip0.t-ipconnect.de) 12.17.07 # bertrik: 106.9 12.18.24 Join Thundercloud [0] (n=thunderc@84-51-130-71.judith186.adsl.metronet.co.uk) 12.26.00 Quit perrikwp ("http://www.mibbit.com ajax IRC Client") 12.26.19 Quit advcomp2019 ("Ex-Chat") 12.27.59 Join domonoky [0] (n=Domonoky@rockbox/developer/domonoky) 12.30.02 Quit tessarakt ("Client exiting") 12.37.24 *** Saving seen data "./dancer.seen" 12.44.14 Part jon-kha ("[IRSSI] so real, you'll wet yourself!") 12.44.30 Join jon-kha [0] (i=jon-kha@kahvi.eu.org) 12.44.44 Quit fredddy (Remote closed the connection) 12.46.03 Join fredddy [0] (n=freddy@p3E9E3203.dip0.t-ipconnect.de) 12.46.12 Quit Schmogel (Read error: 54 (Connection reset by peer)) 12.50.37 # hmm, looks like upscaling AA still doesn't work on my M5 (it does in the sim) with r19410. Weird. 12.53.05 # * pixelma switches WPSs and tries what happens on downscale 12.54.54 # that works 12.57.47 # bertrik: any chance you could update your sansa c200/e200 power patch --- looks like it missed 3.1 freeze! 12.58.05 # blah, sorry my fault... forgot to rename the cover.50x50.bmp on target 12.59.07 # * pixelma goes to corner 13.09.24 Quit seraph ("Ex-Chat") 13.17.27 Quit miepchen^schlaf () 13.20.36 Join advcomp2019 [0] (n=advcomp2@unaffiliated/advcomp2019) 13.21.20 Join AndyIL [0] (i=AndyI@212.14.205.32) 13.25.18 Join casainho [0] (n=chatzill@89-180-152-130.net.novis.pt) 13.25.42 # hello :-) 13.26.22 # can someone help me on build GNU Debugger? is there any script on RB sources to build it? like the "rockboxdev.sh"? 13.26.50 # casainho: GNU debugger as in "gdb" ? 13.26.54 # casainho: http://www.rockbox.org/twiki/bin/view/Main/CrossCompiler 13.28.06 # Llorean: thank you!!!!! :-) 13.28.37 # I will build it right now, since I have now my JTAG hardware and OpenOCD working :-) :-) 13.32.27 Quit AndyI (Read error: 110 (Connection timed out)) 13.32.48 Quit jhMikeS (Nick collision from services.) 13.32.54 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 13.36.26 # rasher, you shouted something like 'wfms' yesterday, was that a joke or am I completely missing something? 13.37.24 Quit Thundercloud (Remote closed the connection) 13.38.23 # bertrik: I think everyone wants it, there was first attempt in the past to make it working (JdGordon?) 13.39.19 # yeah, I had a very very early attempt 13.39.47 # it reuses the wps for radio or something like that? 13.40.24 # cant even remember how I did it (or if it even worked) other than I chated and filled in a fake id3 struct with the info 13.40.26 # which wasnt very good... 13.40.44 # a wfms would be a very nice addition thouhg 13.41.26 # indeed, and I think everyone is ok with this 13.43.19 # sounds like a nice job for Mr. Someone 13.43.28 # we need to decide if we want to reuse tags or create new ones, and do we do it as a seperate file or as a wps mode 13.43.33 # same as a rec screen wpos 13.44.04 # + how to handle statusbars in general (they want to be wps-ifityed also) 13.44.05 # and status bar 13.44.07 # JdGordon: I'd say just use the same .wps file. 13.44.13 # hehe to slow :) 13.44.24 # Just as a %fm conditional, so you can change a few things around for the FM screen. 13.44.27 # *add 13.44.58 Quit casainho ("ChatZilla 0.9.84 [Firefox 3.0.4/2008111318]") 13.45.13 # the downside with that is wps files for screens which on some targets have fm and some dont have alot of extra cruft 13.45.37 # Who cares? The memory's wasted already, since we pre-reserve memory for the WPS. 13.45.54 # not if it ends up needing us to increase that buffer size 13.46.16 # alhough with some cleverness we can ignore bits which are only used for fm 13.46.16 # Allow a few of the ID3 tags to show station name and frequency, and the progress bar to graphically represent the "tuner" with 0% being the lowest available frequency and 100% being the highest. =P 13.46.38 # Tags aren't going to make us increase the buffer size. New graphics are. 13.46.43 Join faemir [0] (n=faemir@88-106-244-173.dynamic.dsl.as9105.com) 13.47.01 # * JdGordon does like the idea of having the entire interface specified in a single wps file with the position of the menu viewport there also 13.47.05 # Allowing it to reuse WPS graphics will probably save memory overall. 13.47.07 # having both in the same file means that we don't need to spin up the disk to go to fm which would be nice imho, unless we use seperate buffers for fm but that would be a waste 13.47.20 Join write__erase [0] (n=write__e@royale.aixmarseille.com) 13.47.40 # Plus, FM is in a sense "the music player" still, so having it encourage a unified look for the two is nice. 13.48.29 # Hi... rockbox rocks... But I realy nead the remote control feature. Any reason it's not implemented on ipod 3G ? I'd do the job if there are no particular reason 13.48.38 # s/nead/need/ 13.48.57 # there is a patch which enables this 13.48.57 # write__erase: The reason is that nobody's done the work. It's not a simple job. 13.49.05 # JdGordon: Not for 3G 13.49.08 # oh 13.49.38 # Llorean, but rockbox implements serial remote, ru 13.49.40 # right ? 13.49.53 # write_erase: For some players, sure. 13.49.54 # The problem is it's not enabled for 3G 13.49.58 # It's not just a case of enabling it. 13.50.10 # You also need to write all the drivers for it. It's not the same for every player. 13.50.12 # yeah ... low level uart control :-) 13.50.29 # * bertrik agrees with Llorean so far w.r.t. the wfms 13.50.49 # There should be the code in linuxipod kernel 13.51.06 Join Aurix_Lexico [0] (n=comrade@c-68-56-205-239.hsd1.fl.comcast.net) 13.51.08 # Well, we'd love to see a patch for it. 13.52.30 # No indicator for battery charge on ipod3g... funny ... 13.52.31 # bertrik: well, if we just reuse tags then it shouldnt actually be too hard to implement.. the problem is the rest of the radio code needs work to play nice with it 13.52.39 # recorder/radio.c is very messy imho 13.53.23 # write__erase: Well, the 3G isn't common. We'd love someone new working on it. 13.53.43 # :-) 13.54.24 Quit lucent (Read error: 110 (Connection timed out)) 13.54.31 # no svn ? 13.55.16 # write__erase: Could you explain the question? "no svn?" doesn't have a context for me to know what you're asking. 13.55.48 # sorry I'm looking for the sources, through CVS, SVN or any source control protocol 13.55.56 # bertrik: hmm.. it might not even be all that much work 13.55.57 # It's in SVN. 13.56.22 # write__erase: In the wiki index there should be a section "For developers" with lots of information. 13.59.00 # JdGordon, I'm not so familiar with radio.c yet, I didn't realise that radio required this much code. I think the interface towards the tuners looks nice, clean and simple. 13.59.50 # you do? it is?! or are you only taking about the actual hardware interface? 14.00.20 # I started working on a patch to move more of that code out of apps into firmware but its not quiet finished 14.01.39 # I mean the interface in tuner.h 14.02.09 # ah yes, that part is nice 14.03.47 # wow, there is support for multiple tuners ... 14.04.04 # not at the same time though... 14.04.27 Join Raynes [0] (i=kvirc@AC8238BF.ipt.aol.com) 14.05.24 Join _jhMikeS_ [0] (n=jethead7@adsl-75-45-238-169.dsl.sfldmi.sbcglobal.net) 14.05.24 Quit jhMikeS (Nick collision from services.) 14.09.40 # n1s: where is your beast radio patch? 14.09.48 # and the ams radio patch? 14.10.12 # * JdGordon searches gmail and finds them 14.10.20 # JdGordon: beast radio went in a couple of days ago 14.10.24 # finds that the beast 1 was commited already 14.10.38 # which is nice, didnt break my radio patch 14.11.41 # JdGordon: I think that to get seeking working nicely i will have to extend the tuner interface a little, will that be nicely doable after your changes? 14.12.50 # i guess so... right now im trying to remove the tuning logic from apps... so ideally it would just say "tune/seek to freq and let me know if its tuned"... 14.13.57 # http://pastebin.com/d59befe9 is the interface I have so far 14.14.19 # which is mostly cut/paste straight out of radio.c 14.14.54 # that fm region sturct also will be removed from the .h as its only needed for tuning (which apps/ doesnt need) 14.14.54 Join herrwaldo [0] (n=waldo@ip-81-11-214-212.dsl.scarlet.be) 14.16.23 # what is the difference between radio_set_frequency and radio_scan_frequency ? 14.17.10 # void radio_set_frequency(int freq) 14.17.11 # { 14.17.13 # curr_freq = freq; 14.17.15 # tuner_set(RADIO_FREQUENCY, curr_freq); 14.17.16 # } 14.17.17 # bool radio_scan_frequency(int freq) 14.17.19 # { 14.17.23 # curr_freq = freq; 14.17.25 # return tuner_set(RADIO_SCAN_FREQUENCY, curr_freq); 14.17.27 # } 14.17.30 # although looking at it, its not very nice :p 14.17.46 # set should force the freq wheras scan would get the nearest station to it 14.17.50 Nick sajes_ is now known as sajes (n=sajes@66.82.244.88) 14.18.56 # so scan starts at curr_freq and just goes to the closest station? 14.19.11 # yeah 14.20.09 # hmm, then maybe this can work without changing the interface, how does radio.c find out which freq it scanned to? 14.20.43 # call radio_get_frequency or radio_get_station 14.22.18 # does it do this currently or do you intend to make it do this? 14.24.23 # thats the intention 14.25.30 # sounds good, the si4700 seeking is basically: set a bit for seeking up or down, 3 different signal measures by which it validates a station and set it off 14.26.04 # and when it finishes you can check if it decided it failed and at which freq it ended 14.27.07 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 14.27.17 # how do you know when its finished? 14.28.57 # ultimately i want to use an interrupt, but you can also check a "finished" bit 14.29.07 Join stoffel_ [0] (n=sfr@p57B4DF1B.dip.t-dialin.net) 14.29.50 Part Raynes ("Reality is that which, when you stop believing in it, doesn't go away") 14.32.52 Join bluebrother [0] (n=dom@rockbox/developer/bluebrother) 14.34.36 Join mcuelenaere [0] (i=mcuelena@rockbox/developer/mcuelenaere) 14.35.33 # n1s: do you tihnk we could do that in a tick task for the other tuners? 14.37.28 *** Saving seen data "./dancer.seen" 14.38.47 # JdGordon: i'm not familiar with how the other tuners work but i imagine it would be possible. 14.39.14 Join kugel [0] (n=chatzill@unaffiliated/kugel) 14.39.21 # would it be a good idea thouhg? 14.39.38 # * JdGordon wants to make the code for the radio screen as simple as possible 14.39.50 Quit XavierGr (Nick collision from services.) 14.39.59 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 14.39.59 Join Jaykay [0] (n=chatzill@p579E7B3E.dip.t-dialin.net) 14.41.11 Quit esthar (Read error: 60 (Operation timed out)) 14.43.27 # for me, tell the tuner to scan, get interrupt/ check for "finished" status, read new freq, update screen seem like a good plan 14.43.41 Quit stoffel_ ("leaving") 14.46.02 Join esthar [0] (n=esthar@student164-247.hampshire.edu) 14.47.00 # i don't know if a tick task is needed, a check; sleep loop would do fine i would think 14.47.19 # gevaerts: thanks for the jz4740_usbtool.c fixes 14.47.29 # what is the best way when i notice that something in the wikipages is wrong/out of date? 14.47.46 # register and fix the problem? 14.47.47 # Jaykay: fixing it 14.48.19 # n1s: well, a tick task would mean apps could get the tuner scanning and then continue doing nothing for all tuners 14.48.25 # ok so i have to register myslef in the wiki (ß) 14.48.37 # (?) 14.49.17 # JdGordon: yes, maybe that is better 14.49.30 # Jaykay: you need to register to edit, yes 14.50.33 # * JdGordon would like a partial playlist viewer in the wps (and preset viewer in the fm screen) 14.50.57 # the registration page sasy i should ask for writing permissions, so now i ask for write permissions :) 14.51.00 # JdGordon: would certainly be nice on portrait screens 14.51.31 # Jaykay: what's your wiki name? 14.52.20 # JohannesLinke if i did everything in the right way 14.53.43 # bertrik: a (poor) joke 14.55.27 # Jaykay: ok, should have write permissions now, promise not to spam :) 14.55.41 # ok i promise :) 14.55.42 Quit robin0800 (Read error: 104 (Connection reset by peer)) 14.56.16 Join Darksair [0] (n=user@117.89.34.248) 14.57.00 Quit Darksair (Client Quit) 14.57.25 Quit Aurix_Lexico (Remote closed the connection) 15.00.38 Quit kachna ("Konversation terminated!") 15.06.25 # hmm. How much additional room should be left on the device after installing? 1MiB? 0.5MiB? 15.06.41 # Depends an awful lot, I should think. 15.06.56 # You won't need much at all for the .cfg file and the nvram. 15.07.10 # Compared to that though, if you want to use database or dircache it can get pretty big, right? 15.07.20 # well, I'm adding a space check prior to installing for rbutil 15.07.28 # bluebrother: we have a couple of nasty bugs triggered by the disk getting full when trying certain things... 15.07.52 # yeah, the database can take several megs 15.08.08 # and my idea was to compare free space with the extracted size. That is a bit off due to cluster sizes on the player. 15.08.40 # bluebrother: Maybe warn if <15mb just in general. 15.08.54 # but if I consider that we should have 1MiB left after installation it should be safe. But should we have a bigger safety? 15.09.16 # Better to play it really safe, at least until Rockbox itself is able to deal better with running out of space, right? 15.09.22 # Llorean: could be done, but I think that would be a separate thing. For now I want to warn / abort during installation. 15.09.23 # bluebrother: maybe let them install if it fits but if you have, say < 10MB free say "Very little disk space free, certain functions in rockbox may not work as intended" or something 15.09.25 # true. 15.10.13 # I think just a warning "Your player is nearly full. While Rockbox can still be installed, some features will create files, and if you run out of disk space may experience unpredictable failures." 15.12.47 # Bagder: can I have the registration email for TWiki user BenZavala? I wish to contact him about a recently uploaded theme. He says "PM me" but leaves no publicly visible email address nor mention of forum / IRC nick. 15.14.03 Join fdinel [0] (n=Miranda@modemcable204.232-203-24.mc.videotron.ca) 15.14.18 Quit jeffdameth (Read error: 110 (Connection timed out)) 15.14.22 # soap: All the album images used in RockFlow? 15.15.44 Join jeffdameth1 [0] (n=jeff@dyndsl-095-033-118-151.ewe-ip-backbone.de) 15.17.01 # ? No. Not if you're asking the question I think you are asking. 15.17.13 Join mcuelenaere_ [0] (n=mcuelena@rockbox/developer/mcuelenaere) 15.17.23 # Just a slight issue with the structural content of his theme. Nothing major at all. 15.17.34 # Ah 15.17.42 Quit mcuelenaere_ (Read error: 104 (Connection reset by peer)) 15.17.46 Join mcuelenaere__ [0] (n=mcuelena@78-21-191-98.access.telenet.be) 15.17.55 # Unlike the most recent 5G upload which broke half the rules. 15.18.12 # (at least he left a contact address) 15.20.34 # why is there http://www.rockbox.org/twiki/bin/view/Main/SandiskE200BatteryMeasurements ? there isnt such a page for any of the other players.... 15.20.45 # and the first paragraph is out of date. 15.20.49 # does/will the new theme site require some kind of account ore a valid contact email? 15.21.09 # Jaykay: that was from early in the e200 dev cycle. 15.21.31 # so this page should be deleted or what? 15.21.55 # n1s: maybe, probably.. we'll find out in 4-6 years time :D 15.22.18 # It should be labeled as a historical artifact - but I don't see a reason to delete. 15.22.33 # JdGordon: :P 15.23.04 # n1s: if you help getting the new theme page up and running, you could decide if it will do that :-) 15.23.11 # soap: its useless^^ 15.23.12 # MarcGuay had gone through and tagged many of the outdated pages - if you want do to so with this one you should look at how he did those other old ones. 15.23.38 Join kachna [0] (n=kachna@r4ax178.net.upc.cz) 15.23.51 # can you give me a link to one of those tagged pages? 15.24.01 # you can search as easily as I can. 15.24.13 # and I do not know one off hand. 15.24.16 # domonoky: i have written exactly 0 lines of php in my life and is perfectly happy with the default theme/wps so i'm not sure i'm the right guy for that :) 15.24.27 # but i dont know what i should search for 15.24.37 # I just remember his massive cleanup efforts. I would also post a link on that page to SansaRuntime 15.24.44 Quit sajes (Read error: 104 (Connection reset by peer)) 15.25.35 Join petur [50] (n=petur@rockbox/developer/petur) 15.26.21 # hmm. My current implementation has one flaw: it requires the space of the extracted files to be actually free, regardless if there will be files overwritten (like during an update). 15.26.50 # should I simply ignore this? The biggest archive would be doom afaics, and that has ~15MiB. 15.27.48 # couldn't you just check the return code from the failing copy? 15.28.08 # sure, but my current attempt is to check the available space before installing anything 15.28.33 # if I'd just look if space runs out during extraction I might have a partly extracted build on the player 15.29.59 # or even two mixed builds, if an update fails due to this. Which I imagine could happen if someone updates from a quite old build and the new one just needs that few bytes more he is missing 15.29.59 # yeah, since it's such small sizes anyway, i think it can be ignored but it doesn't feel entirely clean 15.30.55 # yep, same here ... but checking the space the extracted files already take on the device, if present at all, would be a bit of additional work :) 15.32.57 Join rvvs89 [0] (n=ivo@pdpc/supporter/base/rvvs89) 15.35.12 Quit mcuelenaere (Read error: 110 (Connection timed out)) 15.39.59 Nick JdGordon is now known as JdGordon|zzz (n=jonno@rockbox/developer/JdGordon) 15.40.28 Quit Horscht (Read error: 110 (Connection timed out)) 15.41.40 Nick mcuelenaere__ is now known as mcuelenaere (n=mcuelena@78-21-191-98.access.telenet.be) 15.43.56 Join Horscht [0] (n=Horscht@p4FD4D761.dip.t-dialin.net) 15.46.39 Quit soap (Nick collision from services.) 15.46.50 Join soap [0] (n=soap@cpe-76-181-69-157.columbus.res.rr.com) 15.47.28 Join Aurix_Lexico [0] (n=comrade@c-68-56-205-239.hsd1.fl.comcast.net) 15.47.32 Quit soap (Nick collision from services.) 15.47.42 Join soap [50] (n=soap@rockbox/staff/soap) 15.48.37 # mcuelenaere: you're welcome. I was trying out some code analyser I found on the net, and it pointed them out (as well as dozens of false positives elsewhere) 15.50.10 # ahh cool, how's the program called? 15.50.10 # _jhMikeS_: You need usb_storage_disconnect() (which wasn't there when you asked) 15.50.21 Join dfkt [0] (i=dfkt@unaffiliated/dfkt) 15.50.28 # mcuelenaere: this was with cppcheck 15.55.06 Join {phoenix} [0] (n=dirk@p54B45E91.dip.t-dialin.net) 15.57.37 Join einhirn [0] (i=Miranda@p5B0307B2.dip0.t-ipconnect.de) 15.59.51 Join einhirn_ [0] (i=Miranda@p5B0307B2.dip0.t-ipconnect.de) 16.03.06 Quit faemir ("Leaving") 16.09.46 Join mcuelenaere__ [0] (i=mcuelena@d54C4B86B.access.telenet.be) 16.10.22 Join mcuelenaere_ [0] (n=mcuelena@78-21-191-98.access.telenet.be) 16.10.26 Quit mcuelenaere (Read error: 104 (Connection reset by peer)) 16.10.31 Nick mcuelenaere_ is now known as mcuelenaere (n=mcuelena@rockbox/developer/mcuelenaere) 16.14.02 Join perrikwp [0] (i=4aa794a0@gateway/web/ajax/mibbit.com/x-70fa3a5bea504b72) 16.18.32 Quit einhirn (Read error: 110 (Connection timed out)) 16.28.09 Quit mcuelenaere__ (Read error: 110 (Connection timed out)) 16.32.35 # is it possible to use PCRE in Rockbox plugins? 16.33.16 Quit Jaykay ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 16.34.43 Join LambdaCalculus37 [0] (n=rmenes@rockbox/staff/LambdaCalculus37) 16.36.30 # J-23: You need to find a C library that implements them, and compile that as part of your plugin. 16.37.29 *** Saving seen data "./dancer.seen" 16.37.32 # so I can even use pcre.h from my distro? 16.37.52 # J-23: if your distro runs on your player 16.38.30 # J-23: Google tells me that PCRE is a regular expression library in C. So you need to port that library to Rockbox. 16.39.06 # But looking at it, I'm sure there are simpler regexp libraries if you really need one in Rockbox. 16.39.54 # Doesn't FS#4755 use PCRE? 16.40.35 # Doesn't look like it. 16.40.46 # (based on the files modified/added by the latest version of the patch) 16.41.00 # ah, somebody just posted pcre.h for MacOS 16.42.04 # Maybe the PC-based conversion tool uses it. 16.42.17 # yes. 16.42.45 # But that has nothing to do with using it in a Rockbox plugin. 16.42.51 # Why would you want regular expression support? 16.43.43 # I ask just to know 16.44.38 Quit einhirn_ (Read error: 104 (Connection reset by peer)) 16.51.42 Quit gregzx ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 16.56.08 Join Schmogel [0] (n=Miranda@p3EE217D7.dip0.t-ipconnect.de) 17.06.10 Join miepchen^schlaf [0] (n=miepel@dslb-088-075-090-047.pools.arcor-ip.net) 17.07.24 Join faemir [0] (n=faemir@88-106-244-173.dynamic.dsl.as9105.com) 17.16.30 Quit LambdaCalculus37 ("Ka-chunka") 17.17.21 Quit n1s () 17.33.03 Join lucent [0] (n=eshattow@75-174-180-52.chyn.qwest.net) 17.33.13 Quit XavierGr (Read error: 104 (Connection reset by peer)) 17.33.15 # thanks @ ameyer 17.33.19 # regex playlist generator plugin! 17.34.54 # anyone else running rockbox on Sansa Clip? could suggest to me which patches to look into? 17.37.17 # lucent: all ams-sansa players are still under heavy development, so nothing for normal user, but if you want to help out fell free :-) 17.38.11 # domonoky: I had a Sansa Clip 2GB Red and recently acquired a Sansa Fuze 8GB Silver, so my Clip can become a sacrificial lamb ;P 17.40.07 # a red clip? Are those the v2 clips? 17.43.12 # I'm not sure, how would I determine this? 17.44.19 # the 2GB Clip that I own is running the OF V01.01.30A at the moment 17.44.28 Join Strife89 [0] (n=michael@204.116.245.152) 17.44.29 # don't know. Maybe they have a "v2" marking on the back? 17.45.00 # oh, the silkscreen wore off on my device a long time ago :P 17.45.19 # hmm, firmware version at least was the only indicator one could count on. Assuming the v2 also have a firmware v3 would make that hardware v1 17.46.51 # Yes, looks like it's a "revision 1 clip" according to sandisk sansa clip forums post 17.46.57 # http://forums.sandisk.com/sansa/board/message?board.id=clip&thread.id=10534 17.47.43 # lucent: then try out what we already have in SVN.. and try to improve it. :-) 17.48.27 # status for the different ams-sansas: http://www.rockbox.org/twiki/bin/view/Main/SansaV2 :-) 17.48.57 Quit {phoenix} (Remote closed the connection) 17.49.10 # domonoky: do you suggest adding any additional patches for my "V1 Clip" like FS 9332 ? 17.49.44 # lucent: first build and install a standard build 17.49.51 # okay will do 17.49.57 # I need to set up my toolchain today 17.52.17 Quit __lifeless (Remote closed the connection) 17.54.35 # I wonder what happens, I have all my music on the Clip in "MTP" mode... I have a copy of this music elsewhere but I am curious to know what happens to the MTP music when loading rockbox? 17.55.52 Quit bmbl ("Woah!") 17.56.57 # lucent, I have a clip too but I don't know, probably nothing. I avoid MTP where possible. 17.57.59 # bertrik: with the OF using MTP made "database refresh" faster 17.58.05 # so that's my motivation for using it ;) 17.59.30 # ah interesting. I was looking for a way to speed it up or skip it altogether 17.59.32 # some interesting things are in motion for Ubuntu users too, this might be offtopic for rockbox, but the VFS layer in Gnome is getting updated and should support browsing MTP devices as files and folders 18.00.24 # so Rhythmbox's MTP support plugin would need an overhaul to directly access files on MTP players based on that new access scheme 18.00.51 # That is indeed off-topic here :) 18.00.52 # that's what I was set to work on until I heard rhythmbox is sort of running on the Clip =) 18.01.27 Join toffe82 [0] (n=chatzill@99.146.80.191) 18.01.35 # rockbox you mean? 18.03.08 # petur: what about http://www.rockbox.org/tracker/5675 ? 18.03.27 # no, it was offtopic though, I meant Rhythmbox (Gnome destkop environment's default music player and software application for loading music onto MTP capable players) 18.05.11 Join Jaykay [0] (n=chatzill@p579E7B3E.dip.t-dialin.net) 18.05.39 Quit slact ("ChatZilla 0.9.84 [Firefox 3.0.4/2008102920]") 18.07.39 Quit fdinel (Read error: 110 (Connection timed out)) 18.11.32 Join Strife1989 [0] (n=michael@204.116.245.152) 18.11.57 Quit Strife89 (Nick collision from services.) 18.12.05 Nick Strife1989 is now known as Strife89 (n=michael@204.116.245.152) 18.12.12 # Hmm... do I need to apply rockbox-multilibs-arm-elf-gcc-4.0.3.diff patch to build rockbox for the clip? 18.13.04 # I think rockboxdev.sh applies all patches itself 18.13.38 # oh, I didn't want to install to /usr or /usr/local, I was preferring to keep everything in a non-root owned directory and change my environment variables beforehand 18.13.47 # I'll go read that script now though 18.14.06 # Change the script then. The destination directory is easy to change 18.14.07 # lucent, you can change a variable right at the top of rockboxdev.sh to point it wherever you like :) 18.14.38 # ah! that is great 18.14.38 # kugel: just closed ;) 18.14.56 Quit tvelocity (Remote closed the connection) 18.15.10 # one bug less \o/ 18.19.55 Join karashata [0] (n=karashat@69.41.192.215) 18.22.36 # i suggest closing of http://www.rockbox.org/tracker/2999 because http://www.rockbox.org/tracker/7432 hass more functions and is more up to date..... 18.24.45 Quit Strife89 ("Bye, guys!") 18.25.16 # btw how do i write those links that only the fs#xxxx is shown, as bbcodes in some forums? 18.26.56 # [url=the_url_you_want]text_to_display[/url] 18.28.02 # Jaykay: while FS#2999 does indeed seem (very) outdated, I'm not sure if both support the same targets 18.28.14 Join EspeonEefi [0] (i=eefi@STRATTON-SIX-FOURTY-SIX.MIT.EDU) 18.28.46 # fs2999 supports only uslt tags, sncviewer much more (including uslt) 18.29.28 # Yes, but do both of them work on all players? 18.29.45 # where do I enable test hdd, don't remeber if it is the good name :) 18.30.21 # toffe82: add test_disk.c to apps/plugins/SOURCES 18.30.37 # gevaerts: going by SOURCES, the latter seems to compile on any target 18.30.41 Join mofux_ [0] (n=quassel@dslb-088-072-138-076.pools.arcor-ip.net) 18.30.47 # gevaerts: ok 18.32.19 # kugel: even the Player? 18.32.35 Quit mofux (Read error: 60 (Operation timed out)) 18.32.35 # yep 18.33.07 # or maybe not. I haven't applied, but it's next to vbrfix and viewer 18.33.13 Join gregorovius [0] (n=diego@host212.190-30-156.telecom.net.ar) 18.37.32 *** Saving seen data "./dancer.seen" 18.38.10 Join casainho [0] (n=chatzill@89.180.152.130) 18.38.26 # Bagder: are you there? 18.41.09 Join Thundercloud [0] (n=thunderc@84-51-130-71.judith186.adsl.metronet.co.uk) 18.41.13 Join BHSPitLappy [0] (n=BHSPitLa@unaffiliated/bhspitmonkey) 18.41.13 Quit karashata ("G'bye everyone!") 18.43.07 # bluebrother: hello :-) 18.43.13 Join Kitti [0] (n=himka_co@195.5.125.25) 18.43.17 Part Kitti 18.43.26 # linuxstb: hello :-) 18.46.45 # hello 18.47.49 Join Seed [0] (n=ben@bzq-84-108-232-45.cablep.bezeqint.net) 18.47.58 # bluebrother: can I know if you use debug? 18.48.11 # and what IDE you are using? 18.48.26 # if I use debug? What do you mean? 18.48.29 # for debug, I wanted to ask about JTAG 18.48.31 # and my IDE is vim :) 18.49.16 # well, what's the exact question about JTAG? 18.49.58 # hmm 18.49.59 # because until now I just saw tutorials for ARM7 of people using JTAG debugging, GBD and Eclipse 18.50.09 # keyclick's nice now after the rework 18.50.23 # I got it working today :-) - here a screenshot: http://farm4.static.flickr.com/3163/3104368953_2744f24f18_o.png 18.50.45 # bluebrother: so, do you use JTAG debugging? 18.51.11 # yes, but not for Rockbox. Though that doesn't make much of a difference 18.52.22 # bertrik: how to go back to the OF on a Sansa Clip after Rockbox is loaded? 18.52.25 # so, do you use commands to OpenOCD? 18.52.32 # gevaerts: gevaerts: now whats about fs#2999? 18.52.41 # lucent, hold the home button while booting 18.52.44 # bluebrother: or you are not using OpenOCD? 18.52.49 # well, when I used gdb I used it directly. 18.52.51 # bertrik: ah. Very nice 18.53.08 # lucent, the "hold" button works too IIRC 18.53.24 # no, haven't used OpenOCD yet. Back the time I had an emulator for ARM I had a BDI2000 which connects to gdb directly 18.53.37 # what makes e200v2 buttons work in bootloader, but not in Rockbox? 18.53.49 # planning to get a JTAGkey for ARM though. 18.54.07 # bluebrother: ah, okok -- I don't see to much information on RB wiki about this subject... maybe people at RB do not use JTAG debug because of missing connection to players... 18.54.16 Join karashata [0] (n=karashat@69.41.192.215) 18.54.17 # J-23: lcd and shared physical connections (that's what I assume) 18.54.24 # ;/ 18.54.35 # bluebrother: I got one "cheap", from Olimex -- AE 18.54.52 # bluebrother: I got one "cheap", from Olimex -- ARM-USM-TINY for about 55 euros 18.55.04 # okok 18.55.09 Quit karashata (Client Quit) 18.55.17 # I will now try to understand better to use debug :-) 18.55.19 # bye bye 18.58.01 # the JTAGkey tiny is ~30EUR 18.58.12 # which is the reason why I want to get that ;-) 18.58.15 # + 30 EUR shipping I think 18.58.27 Join karashata [0] (n=karashat@69.41.192.215) 18.59.02 # yep, unless you have connections you can use ;-) 19.00.57 Quit moos ("have a good night") 19.01.31 # bertrik: okay, and how to make the clip use rockbox.zip I've made? 19.01.41 # that part is not so clear for me 19.03.06 Join Chesteta [0] (n=Chesteta@dyn57-017.res-hall.ndsu.NoDak.edu) 19.03.53 Quit karashata ("G'bye everyone!") 19.03.56 # hi; im "the guy" who wanted to help figuring out the keymap of the e200v2... if anyone is willing to help me in the endevor id appreciate it :) 19.04.09 # yay more ams-sansa people 19.04.39 # haha ive been looking at the development thread twice a day for a month waiting for things to work 19.04.51 # now i can actually help (hopefully) 19.05.03 Join Nico_P [50] (n=nicolas@rockbox/developer/NicoP) 19.05.26 # I'm going to try rockbox out on my Sansa Clip 2GB v1 today (hopefully) 19.05.30 # lucent, sarcasm or you have one too? 19.05.51 # Chesteta: I own a 2gb clip v1 and a Fuze 8gb 19.06.15 # lucent: nice 19.06.18 Join karashata [0] (n=karashat@69.41.192.215) 19.06.37 # lucent, did you already install the bootloader? 19.06.42 # yes 19.06.48 # bertrik: ah, no I haven't seen documentation yet on the bootloader 19.06.56 # bertrik: where do I look for this? 19.07.02 # (sorry, answered lucents question) 19.07.39 # lucent: I have installed the bootloader if you need help 19.08.00 # yes, where do I find out how to install the bootloader on a Clip? 19.08.36 # can someone please tell me where in Makefile of bootloader I can setup the Optimization of GCC? because I am doing debug with GNU Debugger and I am getting some errors and I think the problem is on otpikization 19.08.38 Quit freqmod_qu (Remote closed the connection) 19.08.52 # Chesteta, lucent: you build the bootloader file using the ordinary rockbox build system 19.09.03 # Nobody wrote the documentation yet AFAIK. Putting rockbox on a Clip is not recommended for general use yet, so maybe we shouldn't even document it. 19.09.29 # then you pass the bootloader file, and (any) OF file to rbutil/mkamsboot/mkamsboot (which you need to "make" once before) 19.09.32 # lucent: build a bootloader. merge it with a OF binary with mkamsboot (in rbutil dir) and copy the resulting binary with the right name to the player 19.09.47 # ah 19.09.48 Quit Nico_P (Remote closed the connection) 19.10.08 Quit mcuelenaere () 19.10.32 # wow my irc just lagged quite a bit, got a full page of txt at once 19.12.07 # still not sure how to build the bootloader 19.12.18 # heres how i did it: 1) download device firmware (say for example you wanted to update to the latest sandisk firmware) 2) build mkamsboot (navigate to that directory and run the build command) 19.12.19 # ../tools/configure --target=bootloader or some such? 19.12.48 # just run configure, it will guide you 19.13.25 # domonoky: I've built configure's "55) Sansa Clip" target... am I all set? 19.13.32 # 3) create a bootloader for your device (mkdir bootbuild-in root directory (instead of just build)) then run ../tools/configure and select your device and then select "B" instead of "N" (b for bootloader) 19.14.29 # 4) run a build command in the bootbuild folder. you should have a file in there with a .sansa extension; this is the rockbox bootloader 19.14.40 Join freqmod_qu [0] (i=quassel@2001:700:300:1430:213:d3ff:fee9:5ed0) 19.14.45 # ah okay I have that file from your step # 4 19.14.51 # I'm starting to see how this works 19.16.20 # 5) copy the .sansa file you build in the bootbuild directory and the bootloader you downloaded in step 1 (the sandisk "stock" firmware) into the mkamsboot directory 19.16.48 # cool. Now I'm following :) 19.16.58 # thanks a heap Chesteta ! 19.17.10 # then you will run the command "mkamsboot [sansafirmwarename.bin] [rockboxfirmwarename.sansa] [outputfilename.bin] 19.17.15 Quit mofux_ (Read error: 110 (Connection timed out)) 19.17.17 # no problem lucent :) 19.17.24 Quit Chesteta () 19.17.28 Join mofux [0] (n=quassel@dslb-088-072-143-034.pools.arcor-ip.net) 19.17.36 Join Chesteta [0] (n=Chesteta@dyn57-017.res-hall.ndsu.NoDak.edu) 19.17.36 # bluebrother: are you there? 19.19.05 # lucent: it took me about 4 hours to figure that out :) its isn't ever stated in steps on the site... and i hadn't used the svn for quite some time 19.22.20 # [ERR] No room to insert bootloader, aborting 19.22.21 # Segmentation fault 19.22.25 # niiiice... :P 19.22.32 # oh; forgot: lastly, step 6) you will connect to your sansa (in MSC mode i believe) and put the newly generated file (i'd rename it to be the name that sandisk initally named it) in the root directory... once copied unplug your device and it will install the new firmware. 19.22.37 # lucent: careful, the rockbox.sansa from the normal build is not the bootloader 19.22.46 # ohhh 19.22.49 # good call 19.22.52 # my mistake! 19.22.59 Quit herrwaldo ("Konversation terminated!") 19.23.04 # and don't just unplug, unmount/safe remove first 19.23.12 # yea; lucent: be sure you use the bootloader build, should be 64k 19.23.45 Quit Thundercloud (Remote closed the connection) 19.24.21 # BTW, a failed bootloader installation can brick your device, there is no known recovery mechanism 19.24.25 # much better now that I follow directions correctly 19.25.17 # casainho: yep ... just doing other things the same time 19.25.43 # lucent: bertrik is correct: with the e200v2 there is a way to open it up and recover the device (some contacts to trip on the circuitboard) but there isnt for the clip 19.25.51 Join herrwaldo [0] (n=waldo@ip-81-11-214-243.dsl.scarlet.be) 19.26.57 # wasn't there an issue with the sd card driver for ams sansas > 1 GB? 19.27.11 # cool, bootloader appears to work 19.27.21 # "*PANIC* SD:DATA TIMEOUT," 19.28.14 # bertrik: confirmed? 19.28.15 # :P 19.28.22 # damn I got that a while ago; stopped happening lately though :) 19.28.42 # i have and 8gb too so idk 19.29.12 # lucent: you did build rockbox (normal build) and put .rockbox in the root directory right? 19.29.37 # Chesteta: yep 19.30.55 # important: as these ams-sansa targets are in a early state, we dont want bug-reports. fix them yourself :-) 19.31.03 # gevaerts: whats about fs 2999? 19.31.11 # domonoky: noted, thanks 19.31.32 # Jaykay: I'm inclined to close it, but I'd like to wait for a few more opinions 19.31.38 Quit herrwaldo ("Konversation terminated!") 19.32.19 # is anyone willing to help me work on the keymaping for the e200v2? 19.32.19 # ok.... but when will you get them? 19.32.43 # Jaykay: when people get here :) 19.32.59 # I have the device and some freetime but dont really khow where to start :) 19.33.16 # wow, so i guess this task will keep open for the next few years^^ 19.33.28 # bertrik: I found a delay which doesn't make i2c_read_data() return -4 (returns 0 instead, as it should), but still no button 19.33.54 Join mofux_ [0] (n=quassel@dslb-092-078-053-080.pools.arcor-ip.net) 19.34.03 # i think sometimes you should simply close a task even if you are not sure.... if anybody needs the patch than he will ask for reopening..... 19.34.52 # Jaykay: I mostly agree, but this is a part of rockbox I'm not very familiar with. If I haven't heard anything by tomorrow night, I'll close it though 19.35.14 # ah that sounds good :) 19.35.19 # Chesteta: shouldnt the e200v2 just use the e200 keymap ? (so no real keamap work needed i would think) 19.35.22 # kugel, what did it read in that case? 19.35.53 Join midgey [0] (n=tjross@71.238.148.140) 19.36.13 Quit Jaykay (Read error: 104 (Connection reset by peer)) 19.36.26 Join herrwaldo [0] (n=waldo@ip-81-11-217-198.dsl.scarlet.be) 19.37.02 # bertrik: 0 19.37.37 # but I initialised btn with 0, so it might not have changed at all 19.39.01 # I think the data line was probably stuck at 0. The i2c read routine read a 0 and thought it was an ACK, then read more data which is not suprisingly also 0. 19.40.15 # well, funman made it be initialised with 0 19.41.15 # domonoky: oh alright; in the developer thread it was mentioned about testing the keymap (by atomikpunk, reply #498). I was going to try and help with that but perhaps it has already been taken care of 19.44.00 # bertrik: the hardwaremapping page reads that SDA is GPIOB1 19.44.02 Join Jaykay [0] (n=chatzill@p579E7B3E.dip.t-dialin.net) 19.44.12 # and A0/A5 are SCL 19.44.47 # bertrik: funman either confused those or used "wrong" variable names 19.49.03 # Chesteta: I think I'm stuck unless there's a patch for the > 1GB SD driver :) 19.49.47 # kugel, I wrote the entry about fuze i2c I/O in the hardwaremapping page... I may have made a mistake. Or maybe this code was linked in the firmware but is not actually used. Or we're overlooking something else. 19.49.48 # lucent: you could shrink the partition to below 1Gb :-) 19.49.55 # ha, maybe! 19.50.20 # domonoky: there's no partition listed though 19.50.32 # domonoky: do you infer that I create one? 19.50.32 # lucent: I dont know of any; I know how to use the svn and use patches but as far as making them (actual programing) i dont, you just need to press the left arrow key while powering on to get to the sansa firmware :) 19.50.35 Quit mofux (Read error: 113 (No route to host)) 19.51.11 # (or atleast on the e200v2 it works that way...) 19.51.37 # lucent: I don't know if creating a partition table on the clip is a good idea, but just shrinking the filesystem should work 19.51.42 # ./util/MTP/sendfirm won't compile for me, it says there is a mismatch in the amount of arguments with a function from libmtp 19.52.00 # bertrik: when I change it, i2c_read_data() returns -4 again... 19.52.44 # Aurix_Lexico: what version of libmtp do you have? It compiles fine here 19.53.23 # 0.3.0 19.53.33 # I have 0.2.6 19.53.56 # lucent (cc domonoky): i tried using the windows disk management console and also paragon partition manager and the sansa e200 would not let me create a different sized partition... this is when I was getting the PANIC** (sd message) 19.53.57 # kugel, does the delay have to have a very specific value to return 0? i2c delays can be made very long and i2c should still work. 19.54.50 # bluebrother: I would like to know how I can define -O0 (optimization of GCC) on bootloader makefile... because I am doing debug and I need it... 19.54.50 # I added a rather long delay, really 19.55.11 # Aurix_Lexico: I can confirm that it fails with 0.3.*. Can you install 0.2.something? 19.56.01 # I'll try 19.56.05 # casainho: you need rather -g to create debug symbols. Disabling optimizations helps during debugging too, but is not strictly necessary (at work we debug with compiler optimizations enabled. Can be confusing at times) 19.56.05 Quit miepchen^schlaf () 19.56.46 # ah, okok - so I see on makefile an option to do debug that uses the -g option 19.57.07 # Chesteta: I do have many files on my Sansa Clip 2GB, and then I added the .rockbox structure 19.57.11 # maybe it's just out of range 19.57.12 # bluebrother: in what kind of company do you work? what devices you do? 19.57.40 # i request committing of http://www.rockbox.org/tracker/task/4719 and http://www.rockbox.org/tracker/task/2533..... 19.58.09 # lucent: oh; I erased everything (backed it up first) and then put rockbox on there... that is probably why its working now :) 19.58.24 # the first one clears the button queue after zooming in mandelbrot, the second makes aplles in snake appear immediatly 19.59.07 # Jaykay: not during the freeze 19.59.36 # While those may be nice improvements, I don't think they qualify as bugfixes 19.59.37 # casainho: in the bootloader Makefile the CC option -g is used if DEBUG is defined. 19.59.48 # so I guess a make DEBUG=1 whould do it 20.00.02 # okok - thanks 20.00.12 # though I haven't tried :) 20.00.22 # gevaerts: I think the second one is a bugfix. Or do you think it's intended to delay the next apple? 20.00.24 # gevaerts: why not bugfixes? 20.00.50 # kugel: it could well be 20.01.07 Join {phoenix} [0] (n=dirk@p54B45E91.dip.t-dialin.net) 20.01.29 # Jaykay: both of them are at least debatable in my opinion 20.02.04 # ok then you can simply commit them since they are not really new features ;) 20.02.09 # ok i stop.... 20.02.23 # Jaykay: btw: don't request committing. You may suggest it, but only if you accept to do the work that might need to be done before committing 20.03.16 # They are changes in behaviour for things that are (in my opinion) not clearly wrong. If someone else wants to commit them, fine, but I won't during the freeze 20.03.36 # i thought the "i suggest..." is annoying because im writing it every time...... and i tried both patches and they work fine (the second after the sync, which i did) 20.04.13 # Chesteta: confirmed, now that I have done a "format" and reloaded the .rockbox directory structure, the rockbox firmware loads and runs correctly 20.04.31 # Chesteta: so there is a limitation in the bootloader that it must load from < 1GB , that's my guess 20.04.32 # gevaerts: so ill suggest comitting after 3.1.... hehe 20.04.35 # lucent: nice! do your buttons work :) mine dont :( 20.05.15 # Chesteta: yes, buttons are working, it does have a panic and SD timeout though 20.05.23 # I tried playing some music and got the panic 20.05.26 Join saratoga [0] (n=41becb3b@gateway/web/cgi-irc/labb.contactor.se/x-90e8e95b08566bea) 20.05.44 # Jaykay: sure :) We won't go wild with untested commits then either, but for those two, why not? 20.06.13 # lucent: i believe that you are correct about the bootloader limitation; as an experiment try putting over 1gb of files (songs) on your device and then add a few more (to be sure they are put in the +1gb section of the chip) see if you can play them 20.06.13 # lucent, one very useful patch for ams sansa players at this moment if the buffering_flash patch, I'll look it up 20.06.17 # Chesteta: though "Play" is mapped to the center button 20.06.26 # another thing: is it allowed to post patches in the tracker who relates to other patches which arent in svn? 20.06.40 # (http://www.rockbox.org/tracker/task/4857? for rockboy) 20.06.48 # Jaykay: yes, as long as those are in the tracker. 20.06.53 # bertrik: I applied the buffering flash patch, thanks! 20.07.17 # or at least, I don't see a reason why it shouldn't be allowed 20.07.22 # Jaykay: for those I'd post the patches to that specific task 20.07.32 # downgrading libmtp worked, I now have the rockbox bootloader on my zen vision:m and not much to do with it 20.07.46 # lucent: whats the fs number of the patch? 20.08.07 # gevaerts: i didnt plan to post a patch..... i know as much as nothing about programming in c^^ 20.08.27 # Chesteta: should be FS9332 20.08.29 # Jaykay: ah, ok. I slightly misunderstood you then :) 20.08.40 # thanks :) 20.09.13 # so f2 4857 is out of date because rockboy isnt in the tracker? 20.09.49 # lucent: so can you play music?! :) 20.10.12 # Jaykay: how is it out of date? 20.10.48 # oggs and wav play nicely, mp3s are known to skip/stutter a lot on the clip 20.11.20 # maybe out of date are the wrong words (as you may have noticed i cant write english...) but rockboy is not in svn (?) and not in the tracker so fs 4857 is not needed 20.11.23 # Chesteta: I don't have any music on there right now, let me try... 20.11.35 # I wasn't really interested in playing music with it yet 20.11.36 # ... now if only my buttons worked... lol 20.11.52 # Jaykay: rockboy _is_ in svn 20.12.04 # damned....... 20.12.06 # http://svn.rockbox.org/viewvc.cgi/trunk/apps/plugins/rockboy/ 20.13.35 # ok i was confused because its not shown in the plugin section.... 20.14.22 # Are "##MUSIC#" and "##PORT#" hidden directories? 20.15.23 # lucent, yes those are weird, rockbox sees them, but both windows and linux do not 20.15.26 # but there isnt anybody working on rockboy...? 20.15.43 # saratoga: which target have you referred to when you said you like the backlight fade (again, I'm glad you like it :) ) 20.15.48 # Jaykay: nope 20.15.55 # ok 20.16.03 # bertrik: I've heard rumors of ways to make those visible from Windows platform using flash drive recovery tools 20.16.25 # bertrik: it's not normally iterated with the mass storage driver in Linux kernel 20.16.55 # bertrik: I looked at the generic i2c, and i2c_read_data == -4 basically means that the sda pin is 0 20.17.04 Quit Chesteta (Read error: 113 (No route to host)) 20.17.16 Join Chesteta [0] (n=Chesteta@dyn57-017.res-hall.ndsu.NoDak.edu) 20.17.22 # kugel: sansa e200 20.17.28 # sorry... wifi issues 20.19.50 # Jaykay: you can see whos working on files by looking at that SVN link i posted above 20.19.58 # Chesteta: confirmed, music plays back 20.20.16 # Chesteta: I'm still getting frequent panics with the SD issue mentioned before, and the database 20.21.20 # * bertrik hasn't seen any sd panics on his 1GB clip in the past week 20.21.59 # lucent: is that after putting 1+ gb of data on the device? 20.22.21 # no, did a "format" using utility in OF 20.22.32 # kugel, no, -4 is returned when the i2c slave does not ACK the device address, which means it didn't send a 0 back after receiving the address 20.22.36 # then added .rockbox/* and a single mp3 in the MUSIC dir 20.23.08 # ok... I was also wondering if we could partition our devices into multiple small drives 20.23.30 # would be a pain to navigate :) 20.23.32 # bertrik: getack returns 0 "if (iface->sda())"; 20.23.45 # Chesteta: wouldn't help anyway. The problem is at a lower level 20.23.48 # i think the problem is that the SD driver can only read one bank of the SD card 20.24.00 # pretty sure the rockbox fat driver is workign fine 20.24.09 # I tried as i stated before but with no luck... there may be other partition tools that work better 20.24.10 # and sda() is "return SDA_PIN" 20.24.41 # saratoga: Clip has.... an embedded SD? 20.24.49 # I'm confused about that part 20.24.57 # bertrik: (and i2c_outb returns getack, and if getack is 0, i2c_read_data returns -4) 20.24.59 # saratoga: so if we format in fat (instead of fat32) it may work better? 20.25.21 # yes, there seems to be some kind of NAND flash <-> SD controller built-in 20.25.29 # saratoga: yep, it looks like bank switching needs to be implemented, I surely will have a look as soon as buttons work 20.25.47 # kugel: which player do you have access to? 20.25.55 # fuze 4gb 20.26.00 # :) 20.26.13 # it's scary to try a bootloader without knowing if the buttons will work 20.26.53 # the buttons work in the bootloader. Besides a faulty bootloader can't break the player, since the dual boot isn't handled by the bootloader 20.27.15 # ah 20.27.22 # lucent: you got it working once before :) 20.27.47 # I've got an 8gb fuze and would be willing to test any work you put in on the SD driver 20.28.11 # kugel, so sda() returned something else than the expected 0 and caused getack to return 0, which is interpreted as failure. So sda() was high, not low as was expected. 20.29.00 # bertrik: ah right, I missread 20.29.26 # Chesteta: no the fat driver is working fine, hence it doesn't matter 20.29.40 # we've been using it for years on targets with 10s of GB 20.29.46 # Chesteta: fat driver probably covers all "versions" of FAT 20.29.49 # so our sda_pin is high. but they key is that the sda_pin doesn't change upon button press I guess 20.29.57 # saratoga: oh right on, understood ;) 20.30.10 # ive got a question: why are there sometimes revisons whose diffs are only showing -no changes-? (as the last revision) 20.30.36 Join admin1lbo [0] (n=admin1lb@pool-72-88-166-100.nwrknj.east.verizon.net) 20.30.55 # white space changes or svn property changes I think 20.31.06 # bertrik: why does it sda_hi() after checking sda() ? 20.31.21 # what is svn property? 20.31.45 # Jaykay: r19423 only changed whitespace 20.31.55 # ok thanks 20.31.59 # quick question how do you install rockbox on an sansa e200 with the utliity in fedora 10 20.32.01 # ? 20.32.14 # Jaykay: http://svn.rockbox.org/viewvc.cgi/trunk/apps/lang/english.lang?r1=19422&r2=19423&pathrev=19423&diff_format=u 20.32.37 # thanks 20.32.41 # kugel, I don't know. I think the generic driver is a bit weird. 20.33.11 # I'd think it should be done before, and the sda() checks if it worked 20.33.24 # but I haven't written it and I don't understand it at all 20.33.39 # kugel, are you familiar with i2c at all? 20.33.44 # not at all 20.34.18 Quit faemir ("Leaving") 20.34.32 # but returning 0 if it's high and then setting it high is surely weird 20.37.36 *** Saving seen data "./dancer.seen" 20.37.57 # sda is a bidirectional pin in the protocol, so master and slave can both set it. In this case, first the master checks the sda state, produces a clock edge, then sets it high. 20.39.20 # the generic i2c driver is a bit weird because it explicitly set sda as output and then outputs a high level, this could produce a bus level conflict if the slave tries to drive it low at the same time. 20.41.04 # in the i2c protocol that I'm familiar with, the SDA and SCL lines are never set to a "hard" 1 and can only output a hard 0. Setting the pins to high-impedance mode (inputs) allows a set of pull-up resistors to pull the lines high. 20.41.58 # bertrik: "could produce conflicts" doesn't sound good 20.42.20 # maybe you can rewrite it a bit so it meets your knowledge and I see if it works better? 20.43.37 Join faemir [0] (n=faemir@88-106-244-173.dynamic.dsl.as9105.com) 20.44.09 Join n1s [0] (n=nils@rockbox/developer/n1s) 20.45.36 Quit mofux_ (Read error: 110 (Connection timed out)) 20.45.58 Join mofux [0] (n=quassel@dslb-092-078-076-182.pools.arcor-ip.net) 20.49.06 Quit saratoga ("CGI:IRC (EOF)") 20.50.48 # bertrik: weird that I get -4 no matter of the delay if I change scl/sda accordingly do teh hardwaremappings page, isn't it? 20.51.15 # but neither result in a button detection so... 20.53.35 # two questions regarding the lang files: is there any sense in writing sometimes sound_settings and sometimes sound settings (without _) 20.53.40 # and what is superbass? 20.53.58 # help need a way to install rockbox on my sansa e200 20.54.45 # admin1lbo: download rbutil 20.54.55 # tried it and it doesn't do diddly 20.55.06 # admin1lbo: bootloader piggybacks onto existing firmware 20.55.10 # admin1lbo: do you have an e200 or an e200v2? 20.55.16 # e200 20.55.24 # and bootloader wont install or run 20.55.30 # admin1lbo: so what exactly goes wrong? 20.55.38 # tried both the utility and doing it manually and nothing 20.55.39 # it wont boot 20.55.44 # "nothing 20.55.51 # "nothing" is a it vague 20.55.54 # release 3.0 20.56.02 # it wont boot 20.56.28 # * domonoky thinks rbutil shoudnt do "diddly" whatever that is :-) 20.56.37 # So does it show anything on the screen? 20.57.02 # NO IT DOES NOT BOOT INTO ROCKBOX IT JUST BOOTS INTO THE ORIGINAL FIRMWARE 20.57.22 # So why didn't you say that? 20.57.35 # I did I quote' it wont boot' 20.57.43 # but it does boot 20.57.48 # it boots into the original firmware 20.57.58 # k you got me there 20.57.59 # And now you say it _does_ boot into the OF. Please make up your mind before asking for help 20.58.02 # Chesteta makes an excellent point 20.58.02 # "it doesnt boot" could mean the device does not power up 20.58.19 # I have to run and go to work 20.58.26 # peace lucent 20.58.26 # thanks for all the advice and help today, folks 20.58.49 Quit admin1lbo (Remote closed the connection) 20.58.58 # Rockbox is really neat, I am anxious to make it my daily firmware for music playback :) 21.00.56 # is anybody so nice and answers my questions? ;) 21.01.26 Part denes_ 21.02.33 # * bluebrother wonders what diddly means 21.02.47 # midgey: Not too happy with the way Turkish turned out, but I think that's all there was in it 21.03.02 # better than nothing 21.03.14 # Jaykay: Do you mean in the desc field? That doesn't matter - it's simply a comment 21.03.18 # bluebrother: usually it's vulgar and refers to sex, but in the silly or obscure context of "nothing meaningful" 21.03.30 # admin1lbo: http://www.rockbox.org/twiki/bin/view/Main/RockboxUtility 21.03.48 # and with that I'm out... ;) 21.03.49 # Jaykay: Superbass is a feature of the archos sound decoding wotsit that adds "Super bass" to the sound 21.04.50 # rasher: when i compile rockbox for i.e. the sansa e200 i guess the "translation" for superbass is still in the lang file? 21.05.48 # Jaykay: Nope - only the targets which have the "masf" feature get that in their lang file 21.06.07 # so same thing with mdb? 21.06.41 # Jaykay: Yup - the text to the left of the colon denotes which targets include that phrase 21.06.44 Join maddler [0] (n=maddler@217.133.171.24) 21.07.10 # ah i see 21.07.12 # thanks 21.08.27 # petur: doesn't the recording screen still fall back to sysfont when the text doesn't fit on the display? 21.11.01 Join miepchen^schlaf [0] (n=miepel@p579ECE80.dip.t-dialin.net) 21.11.04 # rasher: did I miss something in the Serbian update? 21.12.19 # midgey: you could've deprecated LANG_RESTARTING_PLAYBACK 21.12.39 # im sorry if im annoying.... why is fm-radio translated with ukw-radio in german? 21.12.43 # its the same 21.12.44 # bah, i'll fix that 21.16.37 # Jaykay: why not? I believe UKW is (or at least was) the more common abbrevation, just saying - I didn't translate that myself so can't tell you the reason but I don't see any need to change it 21.16.41 # Jaykay: you'll have to ask one of the germans about that. Jörg Hohensohn did the translation, but he's not around here much. 21.17.59 # pixelma: i think fm is the more common abbrevation^^ 21.18.10 # and im german:) 21.18.21 # but ok there is no need in changing this 21.22.16 Quit herrwaldo ("Konversation terminated!") 21.24.36 # Jaykay: but don't let that stop you to suggest improvements, I know some things could possibly be translated better 21.25.07 Join thegeek [0] (n=nnscript@s243b.studby.ntnu.no) 21.25.43 # ok so my suggestion for improvement is to change ukw-radio in fm-radio^^ 21.26.10 # but since its the same its equal.... 21.26.29 # i mean there is no sense in changing this 21.26.32 Join herrwaldo [0] (n=waldo@ip-81-11-218-42.dsl.scarlet.be) 21.27.15 Quit gregorovius () 21.28.00 # I mean in general :) 21.28.09 # ok^^ 21.29.40 # another question(...) why are there so much "prhases" in the lang files which are deprecated? why dont you delete them? 21.31.10 Join einhirn [0] (i=Miranda@p5B0307B2.dip0.t-ipconnect.de) 21.31.10 # * bluebrother has heard UKW much more often than FM in german 21.31.11 # deleting them make it incomaptible to previous versions, especially for older voice files. 21.31.53 Quit casainho ("ChatZilla 0.9.84 [Firefox 3.0.4/2008111318]") 21.32.56 # * Jaykay still thinks that fm is more often used, but he also thinks its not worth discussing about it 21.33.05 # domonoky: thanks^^ 21.33.28 # Jaykay: you could ask wikipedia about that. I bet those guys know best ;-) 21.34.58 # i already did, but they dont say how often wich version is used ^^ 21.35.05 Join nk [0] (n=44dd351c@gateway/web/cgi-irc/labb.contactor.se/x-839f3ae902786f12) 21.37.29 Join Zagor [242] (n=bjst@rockbox/developer/Zagor) 21.38.37 # so my cd player says fm (yes he can play radio;)) 21.39.16 # may sansa just says "radio" :-) 21.40.23 # lol 21.40.46 # not bad^^ 21.41.08 # which language? 21.41.17 # german 21.41.59 # Not a bad idea - the FM is more or less redundant 21.43.02 # but actally there isnt any phrase whish just says "radio".... 21.43.07 # but doesnt matter 21.43.42 # i agree with rasher, in fact fm and ukw is useless^^ 21.43.50 # are.... 21.44.44 Quit mofux (Connection timed out) 21.45.02 Join mofux [0] (n=quassel@dslb-092-078-078-250.pools.arcor-ip.net) 21.45.19 # the DAB equipped targets (some D2s and the Logik DAX) also only have DAB exclusively right? 21.45.54 # just making sure, if so I agree that the "UKW" could be dropped 21.46.01 Quit Chesteta (Read error: 113 (No route to host)) 21.47.04 # * kugel votes for "Rundfunk" :) 21.47.23 # * Jaykay agrees with kugel 21.48.08 # so kugel what is more used: fm ore ukw? :) 21.49.26 # my radio says FM, but I'm used to both. I don't feel strong about either 21.55.50 # frequency modulation or ultrakurzwelle? tough choice on a global scale... 21.56.49 # I'll bet FM works in a lot of languages 21.57.05 # would work in German too 21.57.20 # or does ;) 21.57.22 Join ZincAlloy [0] (n=d9eefff6@gateway/web/cgi-irc/labb.contactor.se/x-a81f4b35a96452b8) 21.58.57 # 5 second backlight timeout is a lousy default 21.59.18 # It seemed a bit fast for me 22.01.07 # it's way too short. 30 is reasonable."backlight" on many targets pretty much means "display". when the backlight goes out, you see nothing. hence it's a power mgmgt mode, which should only kick in after user idles a while 22.01.43 # also, new users seem to be challenged with that short timeout 22.01.50 # indeed 22.02.00 # I whole-heartedly agree 22.02.21 # i would think 15 is better 22.02.22 Quit mofux (Connection timed out) 22.02.23 # not 30 22.02.30 # Maybe the default should be dependent on READABLE_WITHOUT_BACKLIGHT (don't we have a define like that?) 22.02.32 # I can understand. They try to read the main menu and have hardly time to read 22.02.44 Join mofux [0] (n=quassel@dslb-088-072-146-220.pools.arcor-ip.net) 22.03.33 # rasher: like I introduced in this patch? FS#8523 22.04.33 # kugel: Ah, that might be what I was thinking of. 22.04.53 # yeah I don't think we have anything like that in svn 22.05.05 Quit nk ("CGI:IRC (EOF)") 22.05.15 # Nope, that's why I introduced it :) 22.06.39 # kugel: have you tried a battery bench with and without this patch, for example with caption backlight on to simulate backlight usage during playback? 22.07.23 # rasher: No, but there was a report in another task that "showing wps" vs "showing main menu" makes up a 15% difference in runtime 22.08.00 # with backlight off all the time, that is 22.08.18 # not bad.... 22.08.39 # i guess aeverythings updated in the wps even if the bakclight is off 22.08.45 # including the statusbars? 22.08.49 # Jaykay: hence the title of that task 22.09.17 # the wps is updated since there're targets where the screen is readable without backlight 22.09.19 # "Rundfunk" does not include TV? 22.09.40 Quit n17ikh|Lappy () 22.09.50 # i think this was a joke, rundfunk is really old-fashioned..... 22.09.54 # bluebrother: hmm, right. I guess ZincAlloy's "Hörfunk" matches even better 22.10.22 # urgh, that sounds even more 50s 22.10.33 # yes :) 22.10.48 # "MP3-Abspieler" :) 22.11.00 # n1s: yes, but only in cases where you have a very very large font selected (insanely) compared to your screen size. So I wouldn't care about it using sysfont at that moment, it is just better than showing a splash 22.11.34 # mp3 is still to new for abspieler^^ 22.11.40 # petur: what does it use the sysfont for? Displaying text, or numbers? 22.12.21 # kugel: i thought the patch only disables chaning of alternating textes? 22.12.22 # is a READABLE_WITHOUT_BACKLIGHT really necessary? Are there any targets with color display around that are actually readable without backlight and non-color targets that are unreadable? 22.12.30 # "Digitalaudiospieler" 22.12.36 # better^^ 22.12.58 # Jaykay: No, I think the title tells what it does 22.12.58 # someone should make a "old german" translation ;-) 22.13.03 # bluebrother: I think someone reported the Nano to be readable, but I'm not sure 22.13.08 # kugel: ok 22.13.12 # Could be another target I'm thinking of 22.13.22 # rasher: we could ignore the nano :P 22.13.22 # isn't the video readable too? 22.13.26 # bluebrother: don't some ipods have transflexive screens? 22.13.29 # why should a patch aim for disabling alternating sublines? 22.13.43 # yes, the Ipods with colour screens are quite readable without backlight 22.14.01 # kugel: i think you mentioned the reason already, battery runtime? 22.14.53 # Zagor: I don't know, hence the question ... but I only experienced color -> unreadable, non-color -> readable 22.14.56 # Video, Nano, 4G Photo/Colour (although I didn't find the latter as good as the two former but could only compare from memory) 22.15.34 # Zagor: Hmm, getting back to that patch, I'm under the impression that this should be wanted in svn? 22.15.51 # but withoud the fast-changing lines.... 22.15.54 # kugel: the patch or the define? 22.15.58 # Jaykay: of course.. 22.16.05 # Zagor: both 22.16.06 # both^^ 22.16.08 # -.- 22.16.12 # kugel: which patch is that? 22.16.20 # http://www.rockbox.org/tracker/task/8523 22.16.34 # it needs work 22.16.40 # but from the idea, I mean 22.16.48 # IMO it would be a real pitty to turn the LCD off on the Video/Nano without backlight 22.16.48 # It seems like something that should be done 22.17.05 # kugel: yes, I like the idea 22.17.43 # but I think the check shouldn't be for backlight, but rather for lcd_enabled 22.17.46 # ...if we can show that wps updating actually costs anything 22.18.34 # did someone make measurements about the power saving when disabling the lcd? 22.18.39 # is there any sense in disabling the lcd completely after maybe a minute without backlight? 22.18.41 # on players with those not readable lcds.... 22.19.02 # bluebrother: i dont think so, if its appreciated i would do this.... 22.19.12 # I'm wondering if it really makes much of a difference. 22.19.20 # Jaykay: on unreadable lcd:s it would make more sense to disable instead of just turning off the backlight 22.19.28 # Zagor: http://www.rockbox.org/tracker/task/8379#comment21201 22.19.40 # again, if we find it makes a power difference 22.20.36 # zagor: but the lcd is not disabled right? 22.20.56 # this should save even more power 22.21.03 # Jaykay, Zagor: Targets where the display is unreadable without backlight do already turn of "lcd_enable(false)" in their backlight_off function 22.21.04 # disabling the LCD is already done on some of those unreadable ones (on the Sansas and X5 for sure) 22.21.06 # kugel: thanks, I missed that comment. 15% is a lot. 22.21.16 # that sounds a lot. Having actual current numbers would be still interesting though. 22.21.33 # Zagor: and I heard a very similar report some time ago 22.22.07 # bertrik benchmarked runtime on a c200 (IIRC) before committing the LCD disable 22.22.10 # some time as in a few month, way after that comment 22.22.41 # pixelma: the disabling doesn't stop the wps updating though 22.24.05 # which leaves the question how much power the wps needs, and if / to what extend that depends on the theme used 22.24.41 # another thing: is there any way to disable the database rebuild on the e200 without connecting it with a computer? 22.25.15 # bluebrother: it probably is very depending on the wps used. 22.25.37 # Zagor: that's my guess too. 22.25.40 # its kinda annoying if you just want to check something out in the OF but changed a file with rockbox 22.25.54 # probably thinks like scrolling also affect it 22.25.58 # kugel: I know, but thought one question was also about power savings from turning the LCD off 22.26.01 # Jaykay: OF is annoying per definition :) 22.26.02 # things* 22.26.15 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 22.27.30 # zagor: i agree^^ but i think rockbox should make comparisons with the OF as easy as possible, because the finding of resons why rockbox is better will be easier.... 22.27.56 # Jaykay: well we can't change how the OF works 22.28.54 # rockbox can prevent the OF of e200 from rebuilding the database when the player is connected with a computer.... 22.29.41 # Jaykay: yes, but that is an exception. 22.30.02 # we managed to find some bits to fool the OF into skipping that rebuild 22.30.06 # back to the wps updating: shall i do some battery benchs with(out)the patch and different themes? 22.30.30 # Jaykay: that'd be grand. Try a completely blank wps as well 22.30.44 # Zagor: so it would be easy to do that i.e. when a second button is hold down.... 22.30.56 # this would make some things easier 22.31.18 # rasher: what do you mean with a completely blank wps, and where do i get this? 22.31.43 # just use an empty wps file. It should show simply nothing :) 22.31.48 # that test could take some time though :) 22.32.07 # I think main menu vs cabbiev2 is most interesting so start with that please :) 22.32.14 # a totally empty .wps will show the status bar 22.32.34 # Jaykay: A file with simply "%wd" on the first line 22.32.54 # pixelma: not when the statusbar is disabled right? 22.33.41 # ah true, it respects the global setting. Didn't think of it as I never disable the status bar in menus 22.33.45 # Jaykay: you may use a .ape music file, to shorten the whole test 22.34.55 # kugel: well that will decrease the significance of wps differences 22.35.30 # i agree with zagor, additionally i dont have music in .ape^^ 22.36.51 # Zagor: but using mp3 or flac will not show reliable results either, as they need less cpu than unboosted 22.37.08 # so the wps updating is basically free 22.37.38 *** Saving seen data "./dancer.seen" 22.38.21 # I'd say the best test is showing the wps, but pause the music . 22.38.28 # how about mp3's with 320kbits? 22.38.45 # zagor: this would need more than a day..... for a single test 22.38.45 # we want to know how much difference different wpses do, nothing else 22.38.48 # Zagor: that could take a while to show real drain... 22.39.11 # * rasher points Unhelpful at FS#9631 22.39.21 # Zagor: the cpu runs at 30MHz at minimum. Everything that doesn't need 30MHz will not show any difference I think 22.39.24 # rasher: sudoku_generate takes a char* as second argument but you pass it a const char*. Thus you discard the const qualifier. Make sudoku_generate take a const char* and everything is fine 22.39.55 # Zagor: on the e200 that is 22.40.01 # but when music is paused there will be no progress bar or time display updates (maybe also a factor who knows) 22.40.12 # Unhelpful: I don't know if's related, but I have a particular album art which data aborts in pictureflow, but not in the wps (cabbiev2) 22.40.49 # not to mention peak meter when someone uses it 22.41.18 # boosting is done in specific places in the code, is it not? 22.41.22 # the test music needs to drive the cpu a bit, else it doesn't add cpu load 22.42.12 # at least I think so. 22.42.45 # unless we "sleep" the chip when we can 22.42.54 # which we at least used to do 22.43.55 # kugel: cant the cpu switch to 24mhz? i saw it somewhere im entwicklerbereich (debug) 22.43.56 # I don't see how wps changes can affect power consumption at all, unless the lcd activity uses more power 22.44.17 # more wps cpu use doesn't affect cpu_boost() frequency 22.44.18 # bluebrother: ah! 22.44.26 # Jaykay: 30 and 80 are the performance levels 22.44.52 # unless, as Bagder says, we sleep away idle time 22.44.52 # kugel: when you press select in cpu frequenzy, it switches to 24mhz 22.44.52 # ... 22.45.13 # in which case I maintain that cutting the codec out of the test will yield much better accuracy 22.45.13 # Zagor: copying data (especially graphics) around for display? 22.45.27 # Zagor: well, when the cpu needs to calculate the updates, it can't sleep 22.45.30 # but why doesnt the cpu use 24mhz when it has nothing to do? 22.45.47 # yea, you're probably right then 22.45.57 Quit karashata ("G'bye everyone!") 22.46.09 # Jaykay: because the clock switch isn't free so it's about finding the "best" compromise 22.46.41 # Jaykay: probably because someone has chosen 30MHz when he did the port 22.46.47 # and we only have one boost level 22.47.04 # kugel: not only that, it has also been tested and proven 22.47.50 # Bagder: 24MHz works well too though. But it's way too slow without some gui boost implementation 22.48.09 # since for example the gui doesn't boost, we need speed enough to do a non-sluggish gui 22.48.13 # I wouldn't call that working well 22.48.32 # I agree, it's a weird definition of "workign well" 22.49.06 # personally, I'd like interaction to cause boost 22.49.12 # I think he means it's been tested and works, but is too slow for the gui 22.49.34 # right, but I meant tested and works fine for sound + ui and the rest 22.49.41 # "well" as in the hardware does that well (not counting the software in). Also, the only situation I tried 24MHz was with gui boost 22.49.42 # urgh. Updating from Qt 4.4.0 to 4.4.3 increases the rbutil binary by about 1MiB :( 22.49.43 # yeah, I know :) 22.50.00 # 24mhz _works well_ when you just navigate through menus or files.... 22.50.01 # * bluebrother goes checking if he overlooked something to disable when building 22.50.03 Quit mofux (Read error: 110 (Connection timed out)) 22.50.09 # I'm a bit surprised that 24 MHz is apparently not enough for non-sluggish GUI 22.50.25 Join mofux [0] (n=quassel@dslb-092-078-063-080.pools.arcor-ip.net) 22.50.29 # isn't that most nostable on things like ipod video with its huge screen 22.50.59 # amiconn: did you look any more at clk div boosting on pp targets? 22.51.04 # yea, it didn't add sluggishness to the e200 (if I remember correctly) 22.51.13 # I've tested it shortly without gui boost 22.51.24 # rasher: everything.... 22.51.31 # ... which basically is an argument for different speeds on different targets 22.51.35 Join mofux_ [0] (n=quassel@dslb-088-075-020-144.pools.arcor-ip.net) 22.52.00 Quit mofux (Read error: 60 (Operation timed out)) 22.52.31 # according to Buschel, the difference between 24MHz and 30Mhz doesn't yield as much runtime as one might think 22.53.39 # kugel: we're not using scale-on-load in PF yet 22.54.01 # Unhelpful: no, but you changed the load function too. and pf loads bitmaps 22.54.05 # i could do another two battery benchs, only showing the menu. one time time with 24, one time witz 30mhz 22.54.11 # yippie 22.54.30 # Jaykay: you can't run 24MHz without changing the source 22.55.11 # in case you have 24MHz, you're obviously using a custom build. Only tests with the official build are valuable 22.55.21 # so why does "cpu frequency" show 24mhz when pressing select? 22.56.04 # kugel: i've not found any cases of the unscaled loader failing in a bit... is there a particular AA that you could add to the scaler FS task, perhaps? 22.56.27 # Unhelpful: Sure! 22.56.37 # kugel: ? 22.57.01 # Jaykay: you're running a custom build. Download and install the official one before you do any tests please 22.57.19 # no im running the official build...... 22.57.42 # hm 22.57.46 # i did apply a patch for snake and for mandelbrot, they dont have anything to do with the 22.57.52 # cpu frequency 22.58.27 Quit Gareth (Excess Flood) 22.59.02 # be until at least tonight before i can check it... if it breaks in sim, you could try a sim build with ROCKBOX_VERBOSE_BMP_LOADER (i think) 22.59.25 # Jaykay: You're right. I didn't know this is possible 23.00.41 # Jaykay: don't touch cpu frequency if you make test. Let rockbox handle boosts 23.00.56 # tests where you force a freq will hardly be meaningful 23.01.02 # ok 23.01.12 # rasher: did you mean to upload FS#9633 as a bug? ;) 23.01.59 # Unhelpful: Oki doki 23.02.44 # kugel: but if i do two benchs with 24 and 30mhz and only showing the menu, we would know wether 30mhz uses much more power than 24.... if this is the case then the developers could set the standard cpu frequency to 24mhz 23.03.13 # so rockbox is only switching too 30mhz if its really needed 23.03.20 # don't we have three frequency steps on H100? IIRC there's 11MHz too (but that's only used in the fm screen) 23.03.42 # midgey: err nope 23.04.04 # actually, a sim at all should tell you if it's any of the things that will cause an unscaled load to fail, all or nearly all of those have regular DEBUGF 23.05.02 # Zagor: when I log into flyspray, I can see dates on any of the comments 23.05.05 # also, if anybody has a handy reference for C constant size/type suffixes... i need 16-bit, and all i remember is that U==unsigned :/ 23.05.15 Part Jaykay 23.05.46 # midgey: I assume you mean can't? :) 23.05.54 # indeed 23.06.16 # we'll chalk that up to stress from finals :) 23.06.51 # Unhelpful: I don't believe there _is_ a suffix for that 23.06.56 # Unhelpful: only U, L, and LL 23.06.59 # do you see "bagder" next to all comments, despite the fact that he's not commented on the task, or committed it, etc? 23.07.04 # midgey: what do you see instead? nothing? 23.07.10 # s/committed/reported/ 23.07.22 # midgey: did you set "Detailed date format" to something silly in your prefs? 23.07.26 # hobbs: cast it in the operation, then? 23.07.31 # Unhelpful: I suppose so. 23.07.39 # Unhelpful: s maybe? 23.07.50 # 123s, that'd be my guess 23.08.07 # syntax highlighting says otherwise :/ 23.08.16 # rasher: haha looks like it got overwritten with my username during the updgrade 23.08.37 # weird 23.08.57 # what's it supposed to be set to? 23.09.14 # blank? 23.09.19 # surely not either "midgey" or "bagder" ;) 23.10.05 # blank works for me 23.10.09 # * rasher has it set to %Y-%m-%d %T, but that's probably not standard 23.10.24 # if i try blank it reverts to my username 23.10.25 # Zagor: Nope. I know it's doable, and should be relatively easy. But I see no need for it, and it limits the choice of clock frequencies 23.11.03 # the gain would be to lower the cost of boost 23.11.08 Join Gareth [0] (i=gareth@www.wiked.org) 23.11.29 # setting it to the same as rasher worked... 23.12.39 # Zagor: Yes, but imo there's no real need. We can't do that on all targets anyway, and hence we need always need a mode of operation that limits the boost/unboost rate 23.13.00 # On a lowmem target things are different, of course 23.13.23 # hrm, need to look @ the SH asm ref again 23.14.11 # amiconn: not necessarily. we could use two different models: very low idle freq with lots of boosting for div-clk targets and a higher idle freq with less frequent boosting for coldfire 23.15.07 # amiconn: i went back to the "old" bmp loader for reference when i started on HQ greyscale, and i see a fair number of differences that i didn't introduce, in terms of how things are calculated. the comments seem to suggest that you did a lot of the size optimization, i might need to bother you (more than i have) at some point about getting loader size down :/ 23.15.12 # Maybe, but then there are 2 facts which contradict each other 23.15.25 # I don't know if the gain would outweigh the added complexity though 23.16.23 # If we want to lower the idle freq and boost for ui, it would make sense to go 24MHz. But then we'd also want the extra bonus of disabling the pll when at 24MHz - which then means we cannot boost quickly... 23.17.04 # Unhelpful: interesting. The cover doesn't show in the sim, but on target 23.17.29 # and pictureflow shows a wrong cover in the sim 23.17.30 # amiconn: those are not contradictory. we simply cannot disable pll in that scenario. 23.17.33 # Unhelpful: Imo the non-scaling loader size difference isn't that large. But I might have a look anyway 23.17.35 # kugel: now i *know* that's not me ;) 23.17.51 # Right now I'm going to compare sizes for the >>8 brightness versus svn 23.18.07 # * amiconn is curious 23.18.09 # Unhelpful: You're the bmp man now, no matter of the changes you did :) 23.18.31 # everything is of course a matter of "how much do we gain" versus "how much does it hurt" 23.18.33 # ah, that's a size lose pretty much everywhere, i have a smaller mono brightness that's probably good enough for mono. 23.18.45 # Unhelpful: pf segfaults when I click on that wrong image 23.19.13 # tbh i've seriously considered that we should do (0,1,0)/1 for mono ;) 23.20.27 # Unhelpful: Why does the image show up on target? 23.20.52 # kugel: i don't know, did you clear cache on both? it might be wise to do that manually, also... 23.21.01 Quit mofux_ (Read error: 110 (Connection timed out)) 23.21.07 # btw: it shows in pictureflow, it data aborts after clicking it 23.21.10 # Unhelpful: Saving binsize is always good, but it's not everything. A speed gain may be worth some binsize, as well as an accuracy gain 23.21.24 # Unhelpful: pictureflow cache you mean? yes I did that 23.21.33 Join mofux [0] (n=quassel@dslb-092-078-062-000.pools.arcor-ip.net) 23.21.36 Quit dfkt ("-= SysReset 2.53=- Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.") 23.21.59 # amiconn: on mono-only targets, we never dither, hence i'm a bit less concerned with grey accuracy there. also, they have the lowest memory :/ 23.22.23 # kugel: wrong picture reminds me of that bug that was said to be fixed yesterday (the one with the clear cache)... do you have album art for all your albums and/or did you change music files/directories recently, updating the database but not pictureflow? 23.22.27 # (2,5,1)/8 has mean-squared-error of ~22 grey levels 23.22.33 # The mono targets do have a greylib though, and if we want to make the line output pluggable... 23.23.30 # oh! i thought that was only on the 2bpp targets. what uses it on mono, sliding_puzzle? 23.23.34 # pixelma: I updated the database and then cleared the pf cache (using its option) 23.23.48 # I'm fairly sure that my fix really fixes it 23.25.37 # hmm 23.26.21 # Unhelpful: Not sliding_puzzle, no. Atm there is no plugin that uses the greylib and bmp files, mainly due to the fact that there is no bmp loader for the greylib yet 23.27.15 # But while bmp scaling and dithering etc doesn't make much sense in the core on mono targets, having it available for plugins would be a good thing, imo 23.28.07 # kugel: are there some albums without art, only showing the default? I only have a very few and when the bug happened to me I could usually see the art two times - one in the right place and the other a few steps before or after depending on how content had changed, probably on the old "spot" it would have been. Didn't try since yesterday 23.28.10 # Not all mono targets are lowmem, btw 23.28.47 # pixelma: I think that just happened to me, yes 23.29.01 # i know about some of the "modern" mono targets. maybe the "nice" load+scale should be available in pluginlib, and the stripped one in core, on lowmem targets? 23.29.09 # deleting the pf folder manually results in "?" instead of the same cover twice 23.29.19 Quit jhulst (Remote closed the connection) 23.30.12 # I dunno how you measured, but I get an increase by a mere 16 bytes on recorder for the >>8 brightness 23.30.23 # kugel: sounds like the bug hasn't been fixed. Maybe it's not only related to the prepared bmps but also on how pf "remembers" the order? 23.30.37 # This is within measuring uncertainty (section alignment is 16 bytes on SH) 23.30.39 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-3f83bc7424eb8c8b) 23.31.43 # pixelma: pf deletes the old cache now, but only for covers it's going to create. My test showed that it doesn't delete one of the the cache files 23.32.23 # Same amount on arm (mini g2), and +24 bytes on coldfire (h120) 23.32.37 # i was using "actual" size from rockbox-info, but perhaps i need to look @ the symbol w/ nm? 23.32.45 # But it's faster (no division) and more accurate 23.33.01 # I also used actual size from rockbox-info.txt 23.33.31 # pixelma: indeed 23.34.19 # bizarre. i get +16 for the /256 brightness, and -32 for (2,5,1)/8 23.34.31 # on sh, that is 23.34.36 # ZincAlloy: wanted to ask you... now there's the possibility to show something else while adjusting the volume, do you think this could be used in cabbiev2 (I'd find it quite useful if the volume icon could change and dB will be shown as the statusbar does, when there's space enough the dB could also show near the icon only while adjusting). It probably needs some viewport overhaul of the theme though and would take some time 23.34.40 # Yes, +16 for >>8 23.34.46 # Why is that bizarre? 23.35.19 # i guess not, it matches yours 23.35.41 # I saw the dicussion of CPU frequency 23.35.43 # * Unhelpful claims tiredness 23.35.48 # this is actualyl something I've explored quite a lot 23.36.08 # basically, you will use a couple extra MHz doing LCD updates on most color targets 23.36.15 # and WPS updates too 23.36.20 # so the boost pecentage goes up 23.36.34 # on PP this means 1 mA of additional battery load for every 3MHz 23.36.47 # so updating the WPS takes about 1 mA of additional power 23.37.19 # however, my MP3 on COP patch worked around this problem by shifting a lot of the decode use for MP3 to the COP 23.37.20 # pixelma: it did work before I moved the deletion a little down in the function. And that broke it without me noticing 23.37.31 # meaning theres extra MHz available for WPS updates without boosting 23.37.50 # so they're free, provided you have PP and only use MP3/FLAC/MPC 23.38.29 # however this is still not very efficient, and I have some ideas how it could be further improved 23.39.15 # I would eventually like to change how boost works, such that the normal frequency depends on how recently the buttons have been touched 23.39.46 # this way we could disable the WPS on targets like the Sansa, and reduce the CPU clock accordingly to save more power 23.42.35 # amiconn: regarding PLL, I'm assuming the gain Toni saw from it was because he actually reduced the core clock to 24MHz, and that the gain Buschel saw [<1mA] is correct 23.42.42 # in which case we might as well just leave it on 23.42.44 Join freddy_ [0] (n=freddy@p3E9E0552.dip0.t-ipconnect.de) 23.42.56 # what's the normal power usage at 30 MHz for the Sansa anyway? 23.42.59 # though obviously its worth further testing on my part 23.43.10 # 30mA with current SVN according to Toni 23.43.31 # saratoga: I don't understand. how does boost percentage go up with lcd updates? 23.44.01 # so 3 MHz = about 3% battery life hit? 23.44.22 # Zagor: CPU time is spent in the driver and in the WPS code 23.44.47 # on the test_disk_log of test_disk, the value to put on the wiki are the last three ? 23.45.01 # on color targets, couldn't you disable the WPS when the LCD was off? 23.45.11 # I know, probably easier said than done 23.45.17 # saratoga: do you really mean boost, or do you mean "not sleeping"? 23.45.26 # Zagor: boost 23.45.30 # sleeping saves almost nothing on PP 23.45.38 Quit fredddy (Read error: 60 (Operation timed out)) 23.46.03 # rasher. pixelma: http://www.rockbox.org/tracker/task/9634 23.46.53 # saratoga: then, again, please explain how frequent lcd_update causes more cpu_boost() calls to be done. I don't see how that can be. 23.47.13 # Zagor: perhaps this will clarify what I mean: http://www.duke.edu/~mgg6/rockbox/30mhz-2.png 23.47.52 # Zagor: time spent in the LCD driver and WPS code requires a higher average CPU clock then would otherwise be needed, this increase in CPU clock increases power draw from the battery 23.48.59 # saratoga: so you mean with less lcd_update we could lower the standard clock speed? you're not talking about the cpu_boost() call? 23.49.02 # * ameyer wonders what the power consumption of a CFmodded iPod Mini 2G is at 30 MHz 23.49.03 # this shows what boosting does to CPU load: http://www.duke.edu/~mgg6/rockbox/80mhz.png 23.49.21 # saratoga: after that what Bagder said, even doing stuff at 30MHz isn't free, if it wakes up sleeping cores 23.49.25 # Zagor: the codec thread will boost the CPU more frequently the less of the CPU's time it gets 23.49.43 # kugel: sure but sleepign the core barely saves anything 23.49.58 # that's what I thought too 23.50.28 # Unhelpful: Do you know what *is* weird? Using a >> 16 version is effeictively +/-0 on SH1... 23.50.31 # see the first graph I posted, it shows one CPU going to sleep while the other is still on 23.50.43 # whaaaaat? 23.50.48 # yes 23.50.51 # saratoga: aha! thank you 23.51.20 # Try it. Factors are 19596, 38469 and 7471 23.51.34 Quit petur ("Zzzzz") 23.52.38 # +80 bytes on arm though, and +36 on coldfire 23.52.43 # i think the best solution would be to have the button code set a time stamp the last time a button changed, then have the normal CPU frequency change between 24 and maybe 45MHz depending on how recently a button was pressed 23.52.55 # saratoga: so my assumption that using a codec which effectively runs under 30MHz most of the time will yield inaccurate measurements when measuring "show wps" vs "show main menu/blank wps"? 23.52.58 # the WPS update speed could also respond 23.53.26 # + was true 23.53.26 # kugel: yes using mp3 for this will not work 23.53.27 Part blkhawk ("Leaving") 23.53.35 # you should probably use AAC or just disable MP3 on COP 23.53.36 Join jrsharp [0] (n=jrsharp@c-98-193-244-253.hsd1.tn.comcast.net) 23.53.44 # AAC being the same speed as MP3 without the COP 23.53.45 # saratoga: The idea being discussed was switching to just using the post divider(s) for boostin gon PP 23.54.07 # amiconn: I'm not familar with how boosting actually works, how would that change things? 23.54.11 # Then boosting becomes essentially free, and can be done for the ui if a button is pressed 23.54.29 # ah you mean it eliminates the transistion time? 23.55.05 # Right now we have to wait for pll relock, which takes ~500µs on PP. Just switching the post divider (or even using the post-divider selector) takes maybe 1µs 23.55.29 # that'd be nice 23.55.40 # Thing is, we can do this on PP and on AS3525. We cannot do this on coldfire 23.56.05 # So we have to maintain 2 boosting strategies if we decide to go that route 23.56.20 # It also means that we are limited in the choice of frequencies 23.56.50 # but what would this new strategy do to power consumption while unboosted 23.56.59 # nothing 23.57.01 # though even 500us isn't bad, thats only 15uA at 30MHz 23.57.31 # or rather 15uA of average additional boost current 23.57.45 # i think my units are getting mixed up here 23.57.54 # should be in watts, I think 23.57.58 # But we would be able to boost/unboost more often, i.e. boost for ui operation (less sluggishness even witha low unboosted clock on G5), and having a smaller pcm buffer 23.58.15 # yeah that would be great 23.58.38 # what about power consumption while boosting part of the time?