--- Log for 30.09.108 Server: brown.freenode.net Channel: #rockbox --- Nick: @logbot Version: Dancer V4.16 Started: 28 days and 18 hours ago 00.00.36 # dereine: I'd second the c200 or e200 if you're looking for a small, flash player. 00.02.10 Join quelsaruk [0] (n=kvirc@84.122.193.15.dyn.user.ono.com) 00.03.38 Quit Nico_P (Read error: 104 (Connection reset by peer)) 00.03.59 Quit massiveH ("Leaving") 00.04.30 # scorche i tried WinFF several times now but i cant change the size of the video to be 176 x 132 so it will fit my ipod.... please can u tell me what im doing wrong 00.04.59 Join lasser [0] (n=chatzill@Wb954.w.pppool.de) 00.05.17 # confused: This isn't really on-topic for here, but what happens when you try? Also, can't you just use the provided (on the wiki I think) preset? 00.05.18 # * kugel just reads about WinARM 00.05.49 # Sounds promising to compile rockbox natively on a windows machine 00.07.08 # ok when i try i can change only options like 4:3 and so on or if i want it for ipod and other mp3's (it never says ipod nano) and the wiki is making me more confused 00.07.38 # cuz the way its explained on the wiki u kinda gotta know what to do to understand it 00.08.36 Join ender` [0] (i=krneki@foo.eternallybored.org) 00.09.06 # kugel: ever heard of yagarto? 00.09.29 # not yet 00.09.38 # so can u help me linuxstb 00.09.39 # you'll still get issues with shells and possibly missing scripting stuff 00.10.00 # confused: Please use real words like "you" here, as per the channel guidelines. 00.10.16 # ok 00.10.18 Quit freqmod_qu (Read error: 104 (Connection reset by peer)) 00.10.25 # confused: The current version of WinFF should have Rockbox presets, but you'll need to look through its documentation for how to use it. 00.10.26 # confused: No, I've never used winff. I would suggest searching the winff forums, and if you can't find an answer, post a question 00.11.08 # thinking of tools like sed, awk and stuff. Maybe running from inside msys would help with this 00.11.15 # alright thank you 00.11.48 # bluebrother: yea, msys was my first thought too 00.11.51 Join mercora [0] (n=mercora@91-64-187-234-dynip.superkabel.de) 00.12.41 # hey there is the link to the ui simulator down on the extra section of the website or is it me ? where could i find the sim ? 00.12.45 # kugel: amiconn has recently had success getting the cross compilers and such set up in interix. 00.12.55 Join freqmod_qu [0] (i=quassel@2001:700:300:1800:213:d3ff:fee9:5ed0) 00.13.16 # mercora: Generally you should compile your own from the latest source. We don't provide a binary of it, and third party ones may be out of date and mislead you. 00.13.28 Quit bmbl ("Woah!") 00.13.56 # is there documentation on setting up the development environment ? 00.14.09 # mercora: What do you want to use the sim for, btw? 00.14.24 # mercora: And yes, it should be linked in the developers section of the wiki docs index, I think. 00.15.07 Quit bluebrother ("anyway, time for sleep") 00.16.39 # Llorean: just for creating a theme but who knows what else i want to do with it is it a full emulator for the software or just UI ? 00.17.15 # I can't install interix on my xp64. 00.17.32 # at least the setup aborted telling me that 00.17.54 Quit petur ("Zzzzz") 00.18.07 # mercora: It's a UI simulator, no emulation happens which is why we don't call it an emulator. 00.18.33 Quit faemir (Remote closed the connection) 00.20.07 Quit lol3izer_ ("out") 00.20.10 Join lol3izer_ [0] (i=lol3@72.2.63.189) 00.20.27 # Llorean: amkes sense to me thanks for the help ;) 00.22.07 Join DerDome [0] (n=DerDome@dslb-082-083-193-096.pools.arcor-ip.net) 00.23.32 # thank you Llorean your advice worked and I got my video loaded :) 00.25.15 Quit mf0102 ("Ex-Chat") 00.25.51 Quit herrwaldo ("Konversation terminated!") 00.27.25 Quit mirak ("Ex-Chat") 00.28.32 Join RyoS [0] (n=ryo@cl-1804.ham-01.de.sixxs.net) 00.28.35 # hi all 00.28.55 # morning 00.29.07 # maybe the answer is asked everyday 10x, but: powerhandling on iAudio X5 - is there anything going around anymore? :/ 00.29.34 # um.... 00.29.35 # i just changed my battery to a 1100mAh pack, and it gives me 7hours 33minutes, just like original.. 00.29.52 # i dunno, all i know is ipods 00.29.53 # RyoS: Did you run it to test? 00.29.53 # testing it for almost 4 days now, trying OF now.. 00.29.54 # :/ 00.29.56 # oh 00.29.57 # nvm 00.29.58 # Llorean: yes 00.30.17 # RyoS: So you ran the player from full to empty and it the battery benchmark file only gave you 7h 33m? 00.30.30 # Rockbox consistently gets better battery life than the original firmware for other testers on the X5 00.31.11 # sometimes less i think.. today i charged it fully, updated to 3.0 release, went to work. something between 3-4h the battery ran low on me 00.31.14 # :/ 00.31.19 Quit ender` (" I have the heart of a small boy. I keep it in a jar on my desk.") 00.31.27 # That's definitely not normal 00.32.42 Join MethoS_ [0] (n=clemens@dyndsl-085-016-163-173.ewe-ip-backbone.de) 00.33.47 Join fdinel [0] (n=Miranda@modemcable204.232-203-24.mc.videotron.ca) 00.34.09 # My X5L gets nearly 28 hours, and if http://www.rockbox.org/twiki/bin/view/Main/DeviceChart is correct that one has 2250mAh, so about twice yours 00.34.20 # http://rafb.net/p/UgkCto84.html 00.34.26 Join SUSaiyan` [0] (n=SUSaiyan@cc84863-b.zwoll1.ov.home.nl) 00.34.35 # those are the latest logs, if you might want to have a look at the batterybench log 00.34.44 Quit SUSaiyan (Read error: 104 (Connection reset by peer)) 00.35.28 # http://www.batteryupgrade.com/product_detail.php?productId=63549911 <- this is the battery i purchased 00.35.44 # What sort of files are you playing? Do you use the equalizer? 00.36.11 Join BlakeJohnson86 [0] (n=bjohnson@c-24-118-162-123.hsd1.mn.comcast.net) 00.36.49 Quit DerDome ("Leaving.") 00.37.06 # equalizer is put to normal i guess, cant check now since i am charging to test the OF, but i never directly access it 00.38.36 Quit quelsaruk (Read error: 110 (Connection timed out)) 00.39.56 # Which codec do you use? 00.40.13 # RyoS: And during that period you didn't touch the player (no skipping tracks, volume adjustments, etc)? 00.40.21 # nope 00.40.27 # gevaerts: mp3 mostly 00.40.52 # got some albums as flac.. but i dont use them for battery bench 00.42.22 # ok. mp3 should be fine. 7:30 definitely sounds too short to me for mp3 on a new 1100mAh battery 00.42.32 # Perhaps its a stupid question but I really can't find anything about it: How can I apply more than one patch to rockbox (#6800 and #8363)? 00.42.51 # lasser: just apply both of them 00.43.17 # gevaerts: so, anything i could try tomorrow after testing the OF? 00.43.18 # gevaerts: Looking at the bench, another run ran about an hour longer, there's definitely some inconsistency in playback time too 00.44.29 # RyoS: was the volume set the same (more or less) for all tests? 00.44.58 # gevaerts: nope :/ something around 0 and -5 is standard 00.45.05 # my headphones are pretty loud 00.45.32 Join krazykit [0] (n=kkit@host-69-145-35-234.static.bresnan.net) 00.45.41 # so, fully charged, i will start my test with OF now :) 00.45.47 # hm. I get a 15% difference in runtime between maximum and medium volume 00.45.50 # i hate how it looks :S 00.46.16 # Actually, that difference is on gigabeat... 00.46.47 Quit MethoS-- (Read error: 110 (Connection timed out)) 00.48.35 # Llorean: part of the difference is the starting and ending capacities. Those account for about 20 minutes I think. That leaves another 40 for unknown reasons 00.48.40 Quit dabujo ("( www.nnscript.com :: NoNameScript 4.2 :: www.regroup-esports.com )") 00.48.59 Join mmadia [0] (n=chatzill@pool-138-89-96-141.mad.east.verizon.net) 00.53.34 # MarcGuay, I need to expand said wiki page to include a place to put info regarding that patch. We (I) need to get the collected information regarding what works and what doesn't out of that forum thread and into the wiki. I, personally, would not have deleted that entry. It is my fault there is not a proper place to put the information, not the submitter's fault for using the only form found to add said information. 00.54.15 # gevaerts: yesterday night the patches ran into an error, today all seems to be ok... I knew it was stupid :-( Nevertheless thank you. 00.54.42 # lasser: if the patches touch the same code, order may matter 00.55.23 # soap which thread? 00.55.30 # soap: I figured you would be combing the thread at some point. In the meantime, it's not providing false information and the wiki history is easy to farm. 00.56.27 # PS: I'm more than willing to help. 00.56.33 # soap: Re the accessory protocol patch, have there been any negative side effects mentioned by people? 00.56.41 # negative? No. 00.57.18 # But no reports of any sort involving behavior outside testing with accessories. I do not know how many people use it as their primary build. 00.57.28 # Can you think of any reason why it shouldn't go into SVN assuming everything's separated so it doesn't affect other targets? 00.58.36 # I'll admit not having personally tested it myself, as I do not own a single iPod-specific accessory. How about you give me a week of running it as my main build and let me get back to you? I can ask the same thing of the users in the forum thread. 00.59.04 # gevaerts: is there a rule for which patch I have to apply first? 1. Lowest FS# 2. Higher FS# 3. Highest FS#? 00.59.25 # lasser: nope 01.00.08 # lasser: if you get conflicts, you can try a different order, or fix them by hand. That's about as far as rules go 01.00.09 Join MethoS- [0] (n=clemens@dyndsl-085-016-163-083.ewe-ip-backbone.de) 01.00.47 # soap: Sounds good to me. I'd just like to push it in sooner rather than later so we have time to stumble across any kinks and give them lots of time for fixing. 01.02.43 # Llorean: winarm seems to work 01.03.01 Join neddy1 [0] (n=john@nat/sun/x-2f0e052814d814b6) 01.03.19 # kugel: winarm isn't a solution on its own. 01.03.44 # well, together with msys 01.03.56 Join |AhIoRoS| [0] (n=ahioros@200.75.224.98) 01.03.59 # How were you planning on compiling the SH1 and m68k targets? 01.04.13 Join Billenium [0] (i=byd201@c-69-249-254-253.hsd1.pa.comcast.net) 01.04.34 # I didn't plan anything. I'm just interested in how this turns out 01.04.53 # Well, what's the goal exactly? 01.06.21 # You'd mentioned earlier trying to compile Rockbox natively, but for it to be a suitable alternate environment it should really let people have the option to test-compile all targets since patches often have unintended consequences the first time they're written. 01.06.37 Quit neddy (Success) 01.06.38 Quit lasser ("ChatZilla 0.9.83 [Firefox 2.0.0.16/2008070200]") 01.11.51 # soap: An obvious suggestion for the Accessories table, replace the date with the revision number. 01.13.08 # Yea, but that is confusing as well. 01.13.41 # I'd rather it be "0" for pre accessory support. "1" for rev.1 accessory support, "2" for rev.2 accessory support, etc. 01.13.56 Quit MethoS_ (Success) 01.14.06 # That, of course, would necessitate the posting on that wiki page of what accessory support revision we are on. 01.17.36 Join nutrientman [0] (n=45b57a7f@gateway/web/cgi-irc/labb.contactor.se/x-fc0be3a0aef92676) 01.18.30 # also need to add columns for all the features tested with and without accessory power supply turned on. Or at the minimal one - "Is Accessory Power Supply Needed To Make This Stinking Device Work?" (but that long of a title would bust the formatting) 01.18.57 # i loaded rockbox on my ipod 3g, it works fine, except that the computer will not recognize it now. does anyone know how to make the computer see it as a removable disk agasin? what i did was to format the ipod with fat32, copy .rockbox and use ipod patcher and copy a couple of mp3's as a test. 01.19.07 # Would the pre-support info have any value once it's in trunk? Answering my own question: it would for 3.0 users. Hmm. I was also thinking we could easily tell what accesorry support revision we were at by the main RB revision number if it was noted what subversion entry added it. 01.19.47 # soap: Does the revision number matter? 01.20.06 # I mean, as long as there aren't later revisions breaking support for devices, it should just be "without patch" and "with patch" 01.20.16 # It also would have value just so we can keep track of /when/ an accessory was tested. If we do not note that an accessory was tested back in the dark ages then we do not know we need a retester. 01.20.42 # Why don't we get it in SVN, then just require an SVN revision. ;) 01.21.00 # I was assuming we were going with that model. 01.21.15 # Llorean, the revision number matters for just the reasons I outlined above. If we do not know /when/ in the course of support attempts it was tested we don't know if retesting is needed. 01.21.22 Quit coatman ("Buh Bye") 01.21.45 # You are right, SVN revision number does tell all. It is just a harder-to-quickly-parse number. 01.21.54 # soap: I'm not sure I follow that. How do we know retesting is ever needed? 01.22.06 # (This is the same positional argument we had over WPS syntax revision numbers) 01.22.17 # If a device works, it works. We won't know it stops working until someone tries it, and it doesn't work, at which point it's already been retested. 01.22.32 # Until such time as someone tries it, it's in a state of "old, but there's no real reason it shouldn't work as far as we know" 01.22.37 # Retesting is clearly needed if an accessory was reported non-functioning 1 revision in accessory support ago. 01.22.52 # Ah, forward re-testing. 01.22.59 # you're thinking of positive reports, I'm thinking of negative reports. 01.23.04 # yep 01.23.25 # nutrientman: do you connect while Rockbox is running or from an off state? 01.23.37 # and, the way the patch progressed, I think there is a _high_ possibility of regression. 01.24.05 # soap: Yeah, but regression will result in self-testing anyway. 01.24.20 # But you're right, discovering when a non-working device starts working is different. 01.24.21 # Many of the issues appear to my untrained eye to be baud rate negotiation, and a new negotiation plan attempting to solve one accessory might very well bork another? 01.24.36 # soap: I thought most of the baud-rate negotiation issues had been worked out. 01.25.36 # * Llorean will admit he hasn't kept track of it for a few months though. 01.26.11 # One option is to *just* have working devices on the wiki, and ask people to file bug reports against non-working devices (once it's in SVN) 01.26.28 # Among other things, that allows us a return-contact path once it's possible the device is fixed so we can ask the same person to re-test it. 01.26.30 *** Saving seen data "./dancer.seen" 01.26.36 # Presumably this testing will lead to a better understanding of accessory power detection as well and that menu option can be removed. IIRC it was added a temporary hack. 01.26.45 # One of the advantages of showing non-working items on the wiki page is it allows people to see what has been tested and what hasn't. 01.27.19 # It is not only a buyers guide for the cautious, it is a buyer's guide for the adventurous (who choose to buy an untested item). 01.27.21 # soap: We could get someone to add a "peripherals" category to flyspray, and link to that search from the page. 01.27.34 # Meh, lang.h is not found... 01.27.42 # If I were a cautious person I would be hacked the "IpodAccessories" page didn't clearly outline what was known not to be working. 01.27.48 # I think using flyspray for known-bad helps to make sure we can get in contact with them again. 01.28.14 # I'm not against reporting non-working items as bugs, I just don't see why they should be removed from the one-stop lookup page. 01.28.14 # kugel: Why not attempt to work on a solution that's valid for all targets? 01.28.19 # soap: It will need to be made very clear that even though a certain chart says their accessory doesn't work, new testing it required because thing have changed... People may otherwise not bother after seeing the red X. 01.28.36 # *is required 01.28.48 # Llorean: I can start finding one for arm, then if I succeed I can try to find one for the others 01.29.12 # soap: Then you don't need to worry about tracking versions, for one. 01.29.22 # kugel: winarm uses the wrong GCC and binutils version according to their website. 01.30.19 # yea, I've noticed that. I have a doubt though that this is the cause of the lang.h issue 01.30.28 # soap: If we have bug reports, they'll get closed when fixed. But I'm not sure how often the page would get updated to reflect the fixed bugs (much like many of our other wiki pages) 01.30.44 # kugel: Yes, but it does mean it won't be a recommended way to build Rockbox... 01.31.06 # Sure, but let me have some fun please 01.31.08 # I take offense at that! ;) 01.31.23 # I do pretty well keeping my pet wiki pages up-to-date. 01.31.40 # And I start forum threads telling other people to do it for me when I get busy. :P 01.31.45 # kugel: You're welcome to have all the fun you want, but please remember this is for stuff intended to forward Rockbox development. If you know it won't be used, you're basically doing the same sort of stuff as say an unsupported build. Peripherally related, but not really belonging here. 01.31.46 # * scorche wonders why kugel needs Llorean's permission to have "fun" 01.32.24 # Llorean: what if the version turns out as working? 01.32.38 # kugel: We ask people to use the _exact_ same versions we do. 01.32.47 # even if it works, it's not the same version so it won't be a recommended method. 01.33.02 # Llorean: The problem still remains of future revisions breaking the support for previously-working certain accessories. At which point, those bugs get re-opened? 01.33.12 # -certain 01.33.14 # MarcGuay: Or new bugs filed, doesn't really matter. 01.33.34 # kugel: then make a wiki page about it, dont link it anywhere else, really, put a few warnings up, and wait while it slides gently into oblivion and disuse 01.33.36 # MarcGuay: I'm confident people will let us know, vocally, when their accessories that used to work stop. 01.34.03 # I still think the largest issue is that I, personally, would be pissed if I bought something Rockbox knew was non-functional with my iPod and removed wiki reference to said knowledge. 01.34.06 # soap: Well, it's your baby. Just offering some suggestions. 01.34.47 # no no no - We need consensus on this, I'm a worker bee, not a queen. 01.34.59 # I just think Flyspray tasks are, in general, more likely to be productive and useful (especially since someone with the same device can read discussion of its problems more thoroughly if there is any, etc) 01.35.30 # pixelma: thanks for the response, i figured it out. i needed to reboot and hit the ff or rew to get my ipod 3g to go into disk mode 01.35.34 # I think a "Known Working" page is useful, then a link that says "Devices known not to be working" and it links to flyspray filtered for open accessories tasks 01.35.52 # cheers, have a nice day 01.35.59 Quit nutrientman ("CGI:IRC") 01.36.09 # Llorean, that would solve the problem. 01.36.10 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 01.36.48 # soap: I think it'd be the best hybrid solution. Makes the "known good" list easy to view, and makes the "Known bad" list be in a single location, easy for people to submit to (I think flyspray is easier than the wiki), and allows for easy contact-back. 01.37.33 # Of course, for that, we need an "Accessories" category in flyspray. 01.39.03 Quit neddy1 (Connection timed out) 01.40.47 Join neddy [0] (n=john@nat/sun/x-07f55f2c6fbafd8e) 01.46.02 Part toffe82 01.49.16 # objcopy is horribly slow :( 01.50.30 Join LambdaCalculus37 [0] (n=LambdaCa@c-24-0-218-198.hsd1.nj.comcast.net) 01.50.51 # Is using a higher gcc version even viable to you, or do you intend to stick with the known-to-work versions for the time being? 01.51.42 Join webguest20 [0] (n=430aeeaf@gateway/web/cgi-irc/labb.contactor.se/x-d586bd3a32aa3977) 01.51.53 Quit webguest20 (Client Quit) 01.52.07 # s/viable/valuable 01.52.20 Quit Schmo ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 01.52.31 Quit neddy ("Leaving.") 01.52.57 # kugel: is there a good reason for using a higher gcc? 01.53.42 Quit Thundercloud (Remote closed the connection) 01.54.06 Quit confused ("CGI:IRC") 01.54.27 # kugel: For m68k, I don't believe the architecture is supported by GCC 4.x at all. 01.54.44 # it is 01.54.51 # amiconn: I thought it wasn't? 01.55.00 # * Llorean must've misremembered. 01.55.28 # You can use 4.0.x just fine. It produces slightly larger code, which is sometimes a bit slower, but in other cases significantly faster than that produced by 3.4.x 01.55.53 # Why don't we use 4.0.3 for it then, too? 01.56.13 # I guess it's just because it didn't see much testing yet 01.57.41 Join webguest91 [0] (n=430aeeaf@gateway/web/cgi-irc/labb.contactor.se/x-09b4c404f2d3104d) 01.57.59 # scorche: I haven't tested, but I would believe newer compiler versions are likely to create "better" code 01.58.00 # 4.3.x is even supposed to bring a significant performance improvement for coldfire, but so far no one has managed to use this successfully (iirc there were issues with gcc <-> gas interaction for our coldfire variants) 01.58.14 # kugel: and what would give you that impression? 01.58.35 # kugel: "are supposed to" and "are likely to" are two different suppositions. 01.59.09 # Llorean, one last thing... 01.59.25 # What about the "Known partially good" list? ;) 02.00.56 Quit mercora (Read error: 110 (Connection timed out)) 02.03.56 # soap: What does "partially good" mean? 02.04.47 # kugel: I'm going to snippet your patch from eariler and remove all of the SanDisk-related patchings before I patch for the Gigabeat. 02.05.56 # I believe n1s and Lear did some testing of 4.x gcc versions on coldfire but I don't remember the outcome(s) 02.06.38 # scorche: just about every software gets better with the time 02.07.11 # LambdaCalculus37: Well, why do you want to strip it? It's not going to be compiled anyway 02.07.34 # kugel: Remember, GCC supports several architectures. GCC may get better, but its ability to produce optimized code for other architectures is not necessarily consistent. 02.07.53 # kugel: compilers and code is a bit of a different story though... 02.08.38 # Well, I can imagine. I was just saying why I think a higher version _could_ be better 02.08.56 # kugel: You were saying you thought a higher version was likely to be better. Nobody denied that it _could_ 02.09.14 Quit DerPapst (Read error: 113 (No route to host)) 02.09.21 # then why are we arguing? 02.09.50 # Because some of us disagree with the "likely" statement, and you've just now changed it to "could" instead? 02.10.24 Join servlsuser [0] (n=servlsus@207.160.166.98) 02.10.30 # Ok, then I was just saying why I think a higher version is likely to better. 02.10.32 # hello again 02.10.47 Nick servlsuser is now known as nossracer (n=servlsus@207.160.166.98) 02.10.54 # kugel: which we are saying the "likely" bit is highly suspect 02.11.08 # Yes yes, I got that 02.11.13 # thank you again bigbambi for your info earlier it worked beautifully 02.11.50 # however i do have a couple of more questions 02.12.21 # is there anyway to get rid of the delay when i turn my volume up? 02.12.37 # kugel: I've already applied FS#6800 before. Why am I going to do it again? 02.13.43 # nossracer: There's not normally a delay. What player is this? 02.14.08 # sansa e250r 02.15.25 # i am not really sure what i did to it the other night but i have a 2gb sansa and a 2gb sd card and my player was telling me that i had almost 8,000 songs on it 02.15.45 Join neddy [0] (n=john@nat/sun/x-897aec16fa8c50ca) 02.15.49 Part pixelma 02.16.28 Join pixelma2 [0] (n=marianne@rockbox/staff/pixelma) 02.17.13 # LambdaCalculus37: svn revert is your friend here 02.17.50 # Anyway, the built I compiled with winarm on windows runs 02.18.12 # cool 02.19.53 # anybody have any suggestions 02.20.22 # kugel: I reverted the patch. 02.20.28 # Now I'll try yours. 02.20.37 # nice, thanks :) 02.20.43 # * kugel hopes it works 02.23.39 # LambdaCalculus37: I only implemented fading down now, since fading up is done in hardware. If it works, it'd be nice if you compare both and also try different backlight brightness settings 02.23.52 # http://pastebin.com/m6092d6fe 02.24.17 # Doing this on OS X. 02.25.15 # Llorean, "partially good" as in some features work, some don't. 02.25.46 # kugel: Let me try the patch I made from yours that only includes the Gigabeat S changes. 02.25.47 # soap: I'd say those should just have open bug reports too, but I do see some value in having a way to let people know they can get *some* use out of 'em 02.25.58 Quit mmadia (Read error: 104 (Connection reset by peer)) 02.26.02 # LambdaCalculus37: well, you can ignore it, all hunks were applied 02.26.14 # hello? 02.26.29 # the end-of-file seems to be messed up a bit due to pastebin 02.26.58 Part Billenium 02.27.58 # kugel: Well, let's find out! 02.28.07 # * LambdaCalculus37 hits the big red button and compiles 02.28.20 # hehe 02.29.44 # * kugel happily runs a gcc4.1.1 compiled rockbox (although he noticed some warnings during compilation) 02.31.34 # kugel: Speaking of warnings, I got two warnings for backlight.c 02.31.53 # really? 02.32.08 # which? 02.32.19 # http://pastebin.com/m6fb29c90 02.32.40 # * nossracer is showing Channel Stats for #rockbox which will be displayed publicly within 5 seconds. 02.32.46 # Stats for: #rockbox 02.32.47 # Modes: +cntz 02.32.48 # Topic: Please read before speaking: http://www.rockbox.org/wiki/IrcGuidelines 02.32.49 DBUG Sent KICK nossracer to server 02.32.49 # Users: 140 Users 02.32.50 Kick (#rockbox nossracer :No flooding!) by logbot!n=bjst@gateway/web/cgi-irc/labb.contactor.se/x-507a9318582de8ba 02.33.03 Join nossracer [0] (n=servlsus@207.160.166.98) 02.33.08 # whoops 02.33.20 # sorry about that guys new irc client 02.34.06 # * LambdaCalculus37 pets logbot and gives him a beer 02.34.38 # LambdaCalculus37: I don't get this warning(just a weird division by zero one) 02.35.47 # kugel: The universe is about to explode because of this, y'know. ;) 02.36.20 # well since nobody wants to help ill be going 02.36.21 # kugel: Build's almost done. 02.36.26 Part nossracer 02.36.44 # LambdaCalculus37: I actually worry about your warning. I wonder why I don't get it 02.43.49 Quit starnoble ("Leaving") 02.44.44 # how can (HZ/(DEFAULT_BRIGHTNESS_SETTING / 2) be division by zero, if the target defines DEFAULT_BRIGHTNESS_SETTING with 12? 02.46.27 # LambdaCalculus37: wait shortly before installing 02.47.26 Quit neddy ("Leaving.") 02.48.38 # kugel: It's done compiling, but I'll wait (figure you'll want to check something). 02.49.06 # FWIW, initial tests on my iPod Nano show 10% longer runtime after the dual-core MP3 work. (VBR MP3 averaging 191kbps) 02.49.36 # LambdaCalculus37: I set a parenthesis wrong. Want a new patch or should I tell you which line in backlight.c? 02.50.35 Nick fxb is now known as fxb__ (n=felixbru@h1252615.stratoserver.net) 02.50.37 # That said, no WPS vs Cabbie WPS gives you 15% longer runtime. 02.51.16 # *Cabbie v2 02.51.29 # LambdaCalculus37: http://pastebin.ca/1214234 02.51.54 # soap: I've heard about the same difference between showing the wps and showing the main menu 02.52.21 Join neddy [0] (n=john@nat/sun/x-d62d8a5d08e6c865) 02.53.10 # yes, kugel, that is what I mean by "no WPS" - leaving Rockbox in the menu tree instead of WPS. I wasn't very clear about that. 02.53.21 # Curious about no WPS vs empty WPS ;) 02.53.31 Join toffe82 [0] (n=chatzill@adsl-70-135-35-52.dsl.frs2ca.sbcglobal.net) 02.53.39 # kugel: Thanks for the new patch. 02.53.46 # * LambdaCalculus37 reverts the old one 02.53.50 # oh, now that you repeat it, I wonder why I got it wrong :S 02.54.17 # soap: I find myself wondering where a very basic wps (three non-scrolling lines, one for each of the basic tags) would land on battery life. 02.54.41 Quit Nevtus (Read error: 110 (Connection timed out)) 02.55.16 Join Nevtus [0] (n=Nevtus@host81-159-78-176.range81-159.btcentralplus.com) 02.55.30 # I find myself wondering how much runtime would disabling wps refresh/updating with off screen yield 02.56.16 # (on screens that are unreadable without backlight of course) 02.56.39 # kugel: The problem is that, in part, drawing is an additive process. The functions don't really know the overall status of the screen, IIUC, so if you disabled drawing for a period, then re-enabled it, you'd be likely to end up with artifacts. 02.57.25 # there's a patch on the tracker trying to implement it. On the sim you can clearly see the wps isn't updating anymore after some seconds 02.57.29 # kugel: The whole entire patch is still referring to paths on your computer. 02.57.51 # kugel: Didn't you remove that patch from your build because it causes glitchy behaviour? 02.57.59 # * kugel blames Geany's version diff plugin 02.58.10 # No 02.58.49 # Oh, you left it in your build, but it causes glitchy behaviour. 02.58.54 # the glitch is that alternating sublines are changing amazingly fast for a while after the screens turns on, but no artifacts or something 02.58.58 # kugel: Didn't you use svn diff? 02.59.27 # kugel: have you done any battery benches to see if it actually improves things then? 02.59.30 # LambdaCalculus37: I use a plugin for geany, my text editor. It obviously uses absolute pathes 03.00.01 # Llorean: No, but I could do one 03.00.38 Quit culture (Read error: 110 (Connection timed out)) 03.01.54 # I want to see the battery bench on a gigabeat with 24 band EQ! 03.02.39 # LambdaCalculus37: did you managed to find a fitting -p parameter? 03.02.39 # * LambdaCalculus37 usually sticks to svn diff 03.03.06 # kugel: I edited the patch to fix the paths instead. 03.03.23 # well, something like patch -p5 < patch.diff would've done it too 03.03.28 # Big reason why... just in case. ;) 03.04.03 # LambdaCalculus37: the plugin is supposed to use svn diff. I don't know exactly though 03.08.33 # anyone ever shut off a rockboxed ipod video and not able to turn it on? 03.08.40 Quit krazykit ("later tater") 03.08.44 # i had to hold menu and select to clear it out and turn it on 03.08.45 Join mmadia [0] (n=chatzill@pool-138-89-96-141.mad.east.verizon.net) 03.08.57 # i tried plugging it in and everything it was like a dead rock 03.09.16 # happens to me about 5-10% of the time. 03.09.22 # really? 03.09.35 # u just hold menu and select to turn it on right? 03.09.36 # it is the famous apple bootloader bug. 03.09.45 # yes... 03.09.56 # that doesnt erase anything tho right? 03.10.03 # it erases nothing. 03.10.07 # ah ok 03.10.07 # LambdaCalculus37: Indeed, -p5 was a decent guess 03.10.09 # kugel: Now it applied clean. 03.10.21 # i remember holding some sequence to format it long time ago 03.10.31 # sounds good 03.10.34 # kugel: I fixed the paths anyway, because I wanted to have one that's Flyspray-ready. 03.10.34 # the Apple bootloader appears to believe there is a super-low battery condition and refuses to power on until the battery trickle (?) charges up. 03.10.49 # lol 03.11.16 # is it possible to install rockbox on a pc/laptop with linux/unix/bsd? 03.11.21 # I know of no format sequence. Menu + Select is the hardware reset, just like a push-pin in the back of a H3x0, or long press of "power" on an e2x0 03.11.24 # LambdaCalculus37: Is it a guideline to only update "-p0" patches? I've read it's preferred but not necessary 03.11.32 # s/update/upload 03.11.55 # kugel: And in return, here's the FS-ready patch: Index: firmware/export/config-c200.h 03.11.55 # =================================================================== 03.11.55 # --- firmware/export/config-c200.h (Revision 18669) 03.11.55 DBUG Sent KICK LambdaCalculus37 to server 03.11.55 # +++ firmware/export/config-c200.h (Working copy) 03.11.55 # @@ -32,6 +32,9 @@ 03.11.55 *** Alert Mode level 1 03.11.55 DBUG sent MODE #rockbox +b *!*n=Lambda*@*.hsd1.nj.comcast.net 03.11.55 # /* define this if you have a light associated with the buttons */ 03.11.55 Kick (#rockbox LambdaCalculus37 :No flooding!) by logbot!n=bjst@gateway/web/cgi-irc/labb.contactor.se/x-507a9318582de8ba 03.11.55 *** Alert Mode level 2 03.11.55 Mode "#rockbox +b *!*n=Lambda*@*.hsd1.nj.comcast.net " by logbot (n=bjst@gateway/web/cgi-irc/labb.contactor.se/x-507a9318582de8ba) 03.12.02 # ouch 03.12.11 # doh 03.12.29 # * Bawitdaba slaps logbot around a bit with a large trout 03.12.52 # good to know that devs are handled equally :P 03.12.59 # lmao 03.13.40 # hm 03.13.45 # will he come back? 03.14.01 Mode "#rockbox +o Llorean " by ChanServ (ChanServ@services.) 03.14.11 Quit MethoS- (Remote closed the connection) 03.14.12 # when he gets unbanned 03.15.33 # i have a really old sony vaio mini laptop that was designed for windows me i want to format it and use it for a mp3 player in my car 03.15.43 # so i dont have to take my ipod with me 03.15.47 Mode "#rockbox -b *!*n=Lambda*@*.hsd1.nj.comcast.net " by Llorean (n=DarkkOne@rockbox/administrator/Llorean) 03.16.02 # can rockbox be installed on a pc or has anyone tried? 03.16.24 # from the source i mean 03.16.30 # Bawitdaba: There's the approach of "rockbox-as-an-app" 03.16.37 Join LambdaCalculus37 [0] (n=LambdaCa@c-24-0-218-198.hsd1.nj.comcast.net) 03.16.37 # there is the simulator 03.16.51 # but it's not finished yet, so for the time being you can use one of the several ui simulators 03.16.52 # right 03.16.58 Join pabs [0] (n=pabs@xor.pablotron.org) 03.17.08 # even though using them will just be a pain, especially in the car 03.17.23 # but technically it is sort of possible 03.17.35 Mode "#rockbox -o Llorean " by ChanServ (ChanServ@services.) 03.17.38 # it might just not be as fully functional as normally 03.17.46 # kugel: Does the patch look good? 03.18.40 # jup 03.19.09 # but better use the -pX parameter and do "svn diff" after if I happen to hand such a patch out again. it's safer 03.20.12 # Yes. 03.21.57 *** Alert Mode OFF 03.22.34 # But a -p0 is the best way to go, as I said before. 03.24.28 # LambdaCalculus37: sure, I'm just looking into the source of the plugin to fix it 03.24.31 Join beaner [0] (n=43d902de@gateway/web/cgi-irc/labb.contactor.se/x-5dab893967e00986) 03.26.31 *** Saving seen data "./dancer.seen" 03.27.48 Join nickwb [0] (n=nickwb@ppp118-208-93-218.lns2.bne4.internode.on.net) 03.29.29 Quit beaner ("CGI:IRC (Ping timeout)") 03.34.44 Join User__ [0] (n=chatzill@67.217.2.222) 03.34.59 Nick User__ is now known as Beaner (n=chatzill@67.217.2.222) 03.35.30 # now all i need to do is get some new ear buds 03.35.58 # the ones that come with ipod suck so bad 03.36.05 # can't believe ive used them for this long 03.36.36 # Bawitdaba: That's off-topic talk here. 03.36.56 # lies 03.39.36 # Bawitdaba, read the topic 03.41.05 # LambdaCalculus37: any updates? 03.41.22 # I think the manual needs to be less afraid of Rockboxc Utility, if we're going to call it the recommended install method. The wording clearly scares some people off of it, I know it did for me. 03.43.33 # MarcGuay: I think it just really hasn't been adjusted yet from when it was the experimental install process 03.45.15 # kugel: Sorry, watching TV. I left another Gigabeast build compiling in the meantime. 03.46.50 # kugel: No warnings thus far. 03.48.37 # I installed the rockbox software on my 30gb ipod 5g, everything worked tits for a handful of days, then last night I was showing it off to a friend, noticed the battery was getting low, shut it down, and later threw it on my wall charger. Once I hooked it to the charger it fired up and went into the standard ipod format, I left it charging overnight, then in the morning pulled it off, it... 03.48.39 # ...shut down and now will not fire up at all. I get zero response from any button mashing, zero response hookin it to my computer, zero response putting it back on the wall charger, nothing at all, its acting like a fancy paper weight now! 03.49.49 # any ideas would be greatly appreciated, thank you, and nothing in the forums matches my problems, i believe the software i used was the current build as of a few days ago 03.50.45 # You used the OF to charge. So, any damage is unlikely to be caused by rockbox 03.51.05 # Have you tried hard-resetting your ipod? 03.52.39 # what is the hard reset combo again, 03.52.52 # lock unlock, then menu and ? 03.53.17 # sorry i can find it on apples site 03.53.24 # can't help you on that one. i don't own an ipod 03.53.38 # Does the Gigabeat S charging patch only charge via AC? Leaving it connected through USB seems to let it die... 03.53.45 # MENU+SELECT. 03.53.57 # ok thank you ill try that, 03.54.19 # MarcGuay: IIRC yes, only through AC. 03.54.34 Quit Beaner ("ChatZilla 0.9.83 [Firefox 3.0.3/2008092417]") 03.55.09 # LambdaCalculus37: That explains a lot, thanks. :) I'm going to re-read the task now because I swear I read that it charges through both... 03.56.12 # MarcGuay: Me too, but it's good to double check. :) 03.57.10 Join davidfg4 [0] (n=david@69.51.95.200) 03.58.20 # LambdaCalculus37: ping :) 03.58.33 # kugel: Pong :) 03.58.35 # Still here. 03.58.42 Quit webguest91 ("CGI:IRC (Ping timeout)") 03.58.42 # good. 03.59.20 # still building? 03.59.29 # It's done. Let me install. 03.59.46 # I would even do it for you, if I could! 04.02.37 Join feyd2blak [0] (n=83ac630f@gateway/web/cgi-irc/labb.contactor.se/x-a734d16a9df347fa) 04.04.27 Quit mmadia ("ChatZilla 0.9.83 [Firefox 3.0.3/2008092417]") 04.05.02 # kugel: The brightness is goofed up. 04.05.15 # Hi All...just a quick question....I have just installed rockbox 3.0 from file (not using the GUI) and the theme settings, images etc, are not displaying, any ideas??? gigabeat F20 04.05.37 # LambdaCalculus37: how do you mean? 04.05.39 # feyd2blak: The themes that came with it should work. 04.05.59 # in the play screen that is, the menu displays the background and the menu items OK... 04.06.15 # Are you loading them through Settings->Theme Settings? 04.06.17 # yeh thats what I thought 04.06.26 # kugel: I have the brightness setting at 20 on the backlight. But it's much darker than it should be. 04.06.44 # hm ok 04.06.47 # Plus, the backlight fading is very erratic. The backlight brigtens to max before turning off. 04.06.53 # I extracted the .rockbox file across same as I used to do and now have the issue 04.07.01 # feyd2blak: Themes that came from elsewhere may not work as expected, try ones from the WPS gallery in the wiki with recent modification dates. 04.07.02 # does changing it the backlight do anything? 04.07.19 # feyd2blak: There were changes to the WPS syntax. 04.07.27 # cool, Ill be back 04.07.40 # thanks MarcGuay 04.07.50 # kugel: Nope. 04.07.54 # but the fading is generally working? not bad for untested & experimental code I suppose :P 04.08.15 # kugel: The fading works, but the backlight handling is very poor. 04.08.32 # * LambdaCalculus37 reverts the patch and builds once more without it 04.08.42 # feyd2blak: The font naming scheme also changed, you may need to re-install the font pack as well. Lots of action on the theme front recently. 04.09.00 Join miepchen^schlaf_ [0] (n=miepchen@p579ECD96.dip.t-dialin.net) 04.09.29 # LambdaCalculus37: so to sum up, it's a) dark, b) independent of of the setting and c) before fading down it goes to max brightness 04.09.57 # kugel: Correctamundo. 04.10.00 # LambdaCalculus37: Re: GigS charging. After re-reading, I understand that it does pull a charge via USB but the fact that the disk is always spinning negates it. 04.10.15 # Hm. ok, that needs further investigation 04.10.18 # MarcGuay: Ahh. 04.11.25 # LambdaCalculus37: how's fading up? should be unchanged 04.11.48 # kugel: Fading up doesn't fade up to proper brightness. 04.11.57 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-548bfde4287503d5) 04.12.08 # well, to the dark level I suppose 04.12.17 # kugel: Yes. 04.12.32 # MarcGuay: Thanks...thats my issue, using only themes with the new rockbox...what can I do about getting the old themes to work 04.12.35 # soap: I haven't tested it, but I would expect most of the gain from disabling cabbie/WPS graphics to go away if you're using the MP3 on COP patch 04.12.37 # and going to the settings and changing doesn't do anything? 04.12.41 # kinda weird 04.13.16 # kugel: I tried setting the brightness setting to both max and min... didn't change anything. 04.13.21 Join Darksair [0] (n=user@221.221.144.56) 04.13.49 # I think I need to play a bit with the variables then. The code is generally working 04.14.13 # feyd2blak: http://forums.rockbox.org/index.php?topic=17507.0 04.14.45 # kugel: The best people to ask about this would be whoever did the LCD code for the Gigabeat S, or perhaps jhMikeS or amiconn. 04.14.52 # * LambdaCalculus37 yawns 04.15.42 # well, as far as I see it's not a driver issue 04.16.53 # or, it's a driver issue :P 04.17.16 # kugel: Very observant. ;) 04.17.38 Quit davidfg4 ("Bye") 04.17.57 Quit MarcGuay ("ChatZilla 0.9.83 [Firefox 3.0.1/2008070208]") 04.18.06 # current_brightness doesn't get incremented in the way it should be on fading up, since we're using hardware fading 04.18.49 # which is probably also the reason it'll never go for anything else then the default brightness value 04.19.14 Quit nickwb ("Gotta Go") 04.19.43 # kugel: I'm going to start turning in for the night soon. If you'd like, let me know how the backlight fading fixes go, and I'll check the logs tomorrow morning (my time). 04.19.46 # Good night! 04.20.02 # good night 04.20.25 Quit LambdaCalculus37 ("Ka-chunka") 04.22.16 Quit joetoo (Read error: 104 (Connection reset by peer)) 04.23.13 Join coatman [0] (n=coatman@r01jvgmb7.device.mst.edu) 04.23.47 Quit miepchen^schlaf (Read error: 110 (Connection timed out)) 04.24.22 Join ameyer [0] (n=ameyer17@adsl-75-57-180-230.dsl.emhril.sbcglobal.net) 04.26.37 # MarcGuay: Thanks again will give it a whirl.... 04.27.46 Quit saratoga ("CGI:IRC (EOF)") 04.27.53 Quit feyd2blak ("CGI:IRC") 04.30.32 Quit neddy ("Leaving.") 04.32.02 Join neddy [0] (n=john@nat/sun/x-c165d36e37ceab88) 04.35.01 Join SETH_HIKARU [0] (n=SETH_HIK@host-158-176-3-96.midco.net) 04.46.49 # wpyh: Generally speaking, what are your goals with reorganizing the menu? 04.46.56 # Less depth? Less categories? Different names? 04.47.44 # hm... actually more of those 04.47.56 # more categories, and some different names 04.48.01 Join blkhawk- [0] (n=blkhawk@g229212180.adsl.alicedsl.de) 04.48.14 Quit tvelocity (Remote closed the connection) 04.48.44 # More categories tends to mean a person needs to look in more places to find an option, unless it's *really* obvious from the category name what options are under it. 04.48.45 # the reason is that I find the settings menu too technical. 04.49.01 # What would be some example new categories, then? 04.50.01 # well, in "Sound Settings", I would add "Advanced Sound Settings" and put "Bass Cutoff", "Treble Cutoff", "Balance", "Channel Configuration", "Stereo Width", "Crossfeed" and "Dithering" in it 04.50.08 Join massiveH [0] (n=massiveH@ool-44c48a1e.dyn.optonline.net) 04.50.28 # So "Sound Settings" will consist of "Bass", "Treble", "Volume, "Equalizer" and "Advanced Sound Settings" 04.50.49 # All that does is mean people need to click more things to get to them, though... 04.51.02 # How does having it in another level make Rockbox easier to use? 04.51.05 # I have done that, but I would still like to change the menu in other places, so I don't have a patch ready right now 04.51.38 Join webguest96 [0] (n=47a20b8b@gateway/web/cgi-irc/labb.contactor.se/x-5a2120cac14ecfe3) 04.51.59 # Yes, to get to the advanced sound settings, more clicks have to be made. But it makes Rockbox easier to use by not cluttering up the Sound Settings menu with options that people don 04.52.06 # *don't often use 04.52.27 # how does that make it easier to use? 04.52.30 # is there any way to run rockbox on a sansa view 04.52.36 # Are their eyes going to wear out from seeing additional options? 04.52.42 # webguest96: No. 04.53.59 # It is more difficult to find a specific option in the Sound Settings menu if there are too many options there. Of course, one could look at the option names one by one, but in general people don't do that. 04.53.59 Quit webguest96 (Client Quit) 04.54.29 # Now I don't condone laziness, but I think a more intuitive and user-friendly approach would be better. 04.54.49 # They have to read them anyway, at least until they get to the one they want. 04.55.03 # Assuming they look from the top down, having extras at the bottom wouldn't exactly get in the way. 04.55.32 # Yes, that would also be another option: put the most common options at the top, and the less common ones at the bottom. 04.55.32 # Not to mention it's more difficult to find the option once, while having to go through an extra menu is something you'd have to do every single time you want to change one of those values. 04.56.16 # Yes, but the settings in "Advanced Sound Settings" are not often changed. 04.57.03 # They are the settings that most people don't use on a regular basis. On the other hand, bass, treble, volume and eq are the things people usually want to change often. 04.57.25 Nick Darksair is now known as iSuck (n=user@221.221.144.56) 04.57.25 # wpyh: People don't often change Volume. 04.57.28 # Or Bass/Treble. 04.57.46 # Heck, even the Equalizer should really only be changed when the output hardware is changed. 04.58.21 # All of that category are infrequently used options. 04.58.40 # Yeah, I have to admit that volume is actually not changed so often. But bass, treble and eq are very frequently changed, by most users. 04.59.24 # Why would they constantly change them? 04.59.35 Join webguest49 [0] (n=47a20b8b@gateway/web/cgi-irc/labb.contactor.se/x-15de0b0e7fd9171f) 04.59.38 # Are you sure you're not thinking "I change them frequently, so most users probably do"? 04.59.42 # Well, in theory the eq should be changed when the output hardware is changed, as you said. I myself don't use the eq (I set it to off), but people like to change the eq depending on the music. 05.00.17 # will rockbox work with the ipod nano 05.00.19 # wpyh: I'd think people change volume a lot more than eq 05.00.32 # webguest49: which generation? 05.00.35 # ameyer: But almost never through the menu. 05.00.40 # A lot of users (at least those I see in other forums) like to get a different "experience" each time. 05.00.46 # Llorean: true 05.01.31 # webguest49: 1st generation works, 2nd through 4th doesn't and may never work due to Apple being evil and encrypting their firmware 05.01.46 # will it work with the ipod classic 05.01.50 # wpyh: So basically, they don't want to hear the same song when they hear the same song? 05.02.09 # webguest49: same situation as the 2nd through 4th gen nanos 05.02.14 # wpyh: Most of the users I've read about in the forums tend to just pick a value and stick with it for bass/treble, and might change EQ based on genre if there's one named for their genre. 05.02.37 # apple IS evil, thx 05.02.40 Quit webguest49 (Client Quit) 05.02.48 # wpyh: As it stands though, I don't think you can definitively say those options are frequently used, and even if they are, having the other options merely be visible does not in any way make it more difficult to use them. 05.02.55 # Llorean: they want to set the eq to something today, and to something else tomorrow 05.03.33 Quit blkhawk (Read error: 113 (No route to host)) 05.03.46 # I don't think things need to be optimized for uses other than they're intended. 05.03.49 # Llorean: so you're saying we are making it difficult for users by adding another level of menu? 05.03.59 Nick blkhawk- is now known as blkhawk (n=blkhawk@g229212180.adsl.alicedsl.de) 05.04.00 # The expectation is that Sound Settings are intended as a "alter occasionally, most often when you switch outputs" 05.04.37 # wpyh: I'm saying that you make it difficult for users who want to make use of all the options if you add another layer, while leaving them on the same layer doesn't actually increase difficulty. 05.04.59 # Hiding it just makes it less likely people will even know the options exist. 05.05.08 # Some people won't consider "Balance" an advanced option, since it's offered by many devices. 05.05.17 # So they'll assume it's missing before even checking. etc, etc. 05.06.28 Quit |AhIoRoS| ("Abandonando, see you http://ahioros.vidao2.com") 05.07.36 Join Seed [0] (n=ben@bzq-84-108-232-45.cablep.bezeqint.net) 05.07.40 # Hm... I think it's more of a tie here, and depending on where you look. For the more advanced users, I think having all those options available is good; for the regular user (like the regular PC user), they would only want to see Bass, Treble, Volume, and EQ. 05.07.54 # stupid question, if I got an iPod mini with a broken HD and did the CF mod on it, would I have any need for the OF? 05.08.22 # or is disk mode actually implemented in hardware? 05.08.32 # ameyer: It's implemented in software stored in ROM. 05.08.41 # wpyh: Rockbox is aimed at advanced users.... 05.09.01 # wpyh: You're pretty much advanced by default if you're flashing alternative firmwares on your consumer electronics. 05.09.16 # I don't consider it hiding, because the "Advanced Sound Settings" menu is right there. You do have a point in saying that leaving them on the same layer doesn't increase difficulty though, so we can also have them in the same layer but rearrange them. 05.09.24 # hm... 05.09.49 # I'm trying to make more people use Rockbox (WORLD DOMINATION) 05.10.11 # So you think people will see extra settings, say "oh no, it offers me more options than I expected" and not use it at all? 05.10.24 # I do understand that it would attract 1users though... 05.10.35 # How would hiding settings attract users, exactly? 05.10.42 # They won't know the settings are hidden until they've already installed it. 05.10.57 # Do you honestly believe people will then see extra settings and choose to stop using Rockbox because of them? 05.11.09 # no, that's not that I'm thinking. I'm thinking that the users would say "wow, it's too complicated. and ugly. I'll switch back to the OF". 05.11.32 # Yes, I think they would think the settings are too complicated, and stop using Rockbox because of it. 05.11.55 # If someone thinks it's complicated to *not use* options they don't know what do, they'll probably not get along well with Rockbox anyway. 05.12.33 # On the other hand, if we put the less often used settings in "Advanced Sound Settings", the average user would say "nah, that's too complicated for me. I'll just use the ones in the Sound Settings instead." 05.12.50 # Instead of "nah, those are too complicated for me, I'll just use the ones I know the name of"? 05.12.57 # Having them visible doesn't force anyone to try to use them. 05.13.03 # Llorean: you're probably alienating some people... 05.13.46 # You honestly believe we've turned people away because they were too stupid to say "Oh, there are options here I don't know about, I'll just ignore them." 05.13.56 # And instead got confused by them, and quit using the software? 05.14.32 # Llorean: no and yes. Yes: having them visible does not force anyone to try use them, but might scare them away. No: they would most likely see it as being non-user-friendly nad turn away from Rockbox altogether. 05.14.43 # Yes... 05.14.46 Quit goffa_ (Read error: 60 (Operation timed out)) 05.15.15 # See, I can't rightfully make myself believe there are people who can't see a list of options, and then choose to only use the ones they want to use. 05.15.29 # More options isn't less user friendly as long as they can still easily find the options they DO want. 05.15.43 # It would be less user friendly if the "normal" options were hard to get to because of the advanced ones, sure. 05.15.47 # My goal is to retain all the advanced settings, because that's one of the things that makes Rockbox superior to the OF. But I would do it in a way that makes people feel right at home, in a way that's comfortable to them. 05.15.49 # But they're right there. 05.16.34 # wpyh: Your goal is to make Rockbox harder to use for intelligent people, while trying to attract people who'd apparently be happy enough with the original firmware anyway. 05.17.01 # If having extra options drives them away, I can't imagine they actually _wanted_ to use Rockbox in the first place. 05.17.30 # Yes, you're right about more options is not less user friendly, but they are mixed with the frequently-used options, so users who want to use the more frequently-used options would have to find the right option. They would have to scroll more, and it's not intuitive. 05.17.42 Part SETH_HIKARU 05.17.54 # "Here's a list of options, let me scroll through to read it" isn't intuitive? 05.18.08 # Tell me, when you have a list of options, what does YOUR intuition tell you to do instead of looking at it? 05.18.17 Quit n17ikh|Lappy () 05.18.46 # hm... my goal is not to make Rockbox harder to use for intelligent people. Yes, I would like to attact people who would be happy enough with the OF. I would like to be inclusive instead of exclusive. 05.18.52 Join goffa [0] (n=goffa@216.220.23.105) 05.19.08 # You didn't answer my question about intuition. 05.19.27 # If you're going to call Rockbox "not intuitive" I really expect you to be able to explain what your intuition would have you do instead of what we have you do. 05.20.08 # Well, my intuition would be to scroll through it and see if anything interests me, or if anything might be useful to me. I do understand that more advanced users would want to think about (and actually use) each option. OTOH, less advanced users would think it's all too complicated to use. 05.20.14 # hey, I have slow fingers :p 05.20.47 # So, your intuition is to scroll through the list. 05.20.50 # yep 05.20.51 # We expect you to scroll through the list. 05.20.54 # How is that not intuitive? 05.21.15 # It's not un-intuitive for me. But it would be, for the average user. 05.21.39 # The average user would do what instead of scrolling, then? 05.22.10 # the average user would think it's all too complicated to use. then they would like Rockbox less. 05.22.22 # So their intuition, when given 8 options, is to give up? 05.22.26 # Not "read them"? 05.22.40 # I think if "read a few lines" is too difficult for them, they won't get past the install steps. 05.23.48 # I think it's like Linux. (forgive me for making an analogy) I used Slackware, and now I'm using my homegrown distro with an even more primitive package manager. I would never use Ubuntu. But I see that lots of Linux users (I wouldn't say most) use Ubuntu, Fedora, etc because they are more user-friendly and desktop-friendly. 05.24.21 # What does that have to do with "asking users to read 8 options"? 05.24.34 # Llorean: yes. and actually the install steps are too difficult to follow... but that's another topic. and I have never used rbutil, so I don't know how difficult it is to use. 05.24.39 Join n17ikh|Lappy [0] (n=n17ikh@130-127-73-84.lightsey.resnet.clemson.edu) 05.25.15 # wpyh: What kind of person would install an alternative firmware, then be overwhelmed by having 8 options instead of 4? 05.25.27 # I mean I'm thinking the person has to be nearly illiterate it 8 options is too much a strain to read... 05.25.35 # about the analogy? see, slackware gives you all the options you want, and you can and should use a text editor to edit those. No GUI configuration tools. Ubuntu hides them behind a GUI. 05.26.02 # * wpyh is actually seeing 12 options, but that's just a numbers issue 05.26.34 *** Saving seen data "./dancer.seen" 05.26.36 # Bass Cutoff and Treble Cutoff, at least, aren't on most targets. 05.26.39 # Basically, by adding another level, we can separate the rough controls and the fine controls + advanced controls 05.26.40 # So, 10ish 05.26.49 Join reacocard [0] (n=reacocar@WL-431.CINE.HMC.Edu) 05.26.52 # Yes, making it harder for a normal user to use. 05.26.53 # yeah 05.26.59 # uh? 05.27.01 # Separating the levels just adds complication 05.27.20 # yes, I do understand your argument about the extra level 05.27.57 # so I'm open to ideas... an alternative is to display the 4 basic sound settings, then display a separator line, then display the advanced settings. How about that? 05.28.03 # So your goal is to make the project less advanced-user / developer friendly and more "clueless user" friendly? 05.28.24 # A separator line doesn't do anything functional either. Why do they need to be distinguished at all? 05.28.46 Quit massiveH ("Leaving") 05.29.22 # Partially true. My goal is to make it more "clueless user" friendly, but not less "advanced user" friendly. The advanced user would be intelligent enough to open the submenu ;) 05.29.38 # Yes, but it takes him more time. 05.29.48 # A separator line would tell people that "The settings below this are advanced settings" 05.30.00 # No, it would tell a user "the settings below this are settings below this" 05.30.14 # If your users are too dumb to be able to read a full list of settings names, I doubt they'll instantly realize that's the "Advanced Settings" line. 05.30.18 # Llorean: depends on how you look at it. 05.30.36 # You seem to assume your users cannot read, but can fathom the intention of an apparently random line. 05.30.40 # Llorean: yes, so I'm still open to ideas, as I said. 05.30.46 # Meanwhile, all that line will do is make the screen _more_ full 05.30.52 Join FRiZzO [0] (n=frank@74.13.73.175) 05.30.53 # Which, by your logic, should make it more overwhelming, not less. 05.31.13 # Here's an idea "don't add submenus, they're unnecessary and make the entire firmware harder to use" 05.31.32 # People can, at most, be overwhelmed the first time they enter the screen. 05.31.34 # Llorean: the line there would signal some kind of separator. and the user seeing the weird setting names under it would immediately realize they are in the wrong zone 05.31.41 # Submenus demand a cost every single time someone wishes to access those options. 05.32.04 # wpyh: If the user is intelligent enough to do that, they're intelligent enough to just not click on options they don't want to click on... 05.33.07 # Yes, it demands a cost. Since they are not that frequently used, they would entail a smaller cost than to have the average user read the whole list. 05.33.29 # I don't understand your statement there. 05.33.32 # Llorean: not all users are as smart as you think. Maybe what we perceive as "users" are different? 05.33.35 # The average user needs to read the list _once_ 05.33.50 # Then they know which options are there, and which ones they want to use. 05.34.01 # Meanwhile, the advanced user needs to go into that menu many times over the life of their player. 05.34.33 # So, how is the cost higher to the average user. If the list overwhelms them every single time they read it, I'd be impressed. 05.34.58 # wpyh: My basis for an "average" user is my mother. She has difficulty using computers, period, but is not afraid of an options menu. 05.35.06 # Yes: the average user would know which options are there. But that's beside the point. The long list would make it harder to scroll to the option they want. 05.35.19 # Not if it were sorted. 05.35.28 # Sorted according to what? 05.35.59 # Advanced options in the middle-ish, more common ones at the top and bottom (least clicks from starting point) 05.36.08 # :O 05.36.29 # (that's an emoticon of an astonished person, sorry) 05.36.45 # This benefits advanced users too, since overall they're most likely to use the same options and these technology-terrified users you seem to be targeting. 05.36.50 Quit fdinel ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 05.38.02 # More common ones at the top and the advanced ones at the bottom would be more intuitive. Having common options at both ends is counter-intuitive, even though it is technically nearer to the top if you count the clicks 05.38.32 # You have to assume your clueless users will learn to use Rockbox after a short time 05.38.48 # Rockbox should be aimed at being easier to use once you learn how, even if that takes a small cost in making it harder to learn. 05.38.59 # Since, ideally, people will be using it for a very long time. 05.40.10 Join flosco [0] (n=ad10b19f@gateway/web/cgi-irc/labb.contactor.se/x-ce1ed4fc41fbf2ff) 05.40.11 # I think I can't assume that. I don't want to make people learn something like this. Instead, I want people to use Rockbox and find that it feels "easy to use, intuitive and feels just like my OF, but it has more advanced options should I ever need them. that's what makes it cool." 05.40.14 # Lowering the barrier of entry at the cost of total usability is a bad design choice, especially considering "get more users" is not a significant project goal. The intended audience is "people who can contribute" since that's what makes the project grow, and "people who can contribute" tend to be advanced users anyway. 05.40.25 Quit flosco (Client Quit) 05.40.26 # hm... ok 05.40.32 # I can see that our premises are different 05.41.21 # Yes, but mine's the one that's actually set for the project. 05.42.05 # Yes, which is why I can't just make someone apply my patches... 05.42.47 # Maybe you should consider writing the patch in a way that accomplishes your goals _without_ sacrificing the goals of the project? 05.42.52 # I can only persuade people. If that fails, then I would have to accept that :) 05.43.28 # Instead of fighting against the project direction, why not try to work with it? 05.43.33 # Yes, that would be a good thing. I don't have any other ideas right now though... 05.44.06 # Llorean: I'm actually trying to work with it. However, all my ideas seem to be against the project direction you described. 05.46.39 # I didn't do it on purpose :P 05.46.58 # Just remember, the target audience is "more developers to help further improve things" not "masses of every day users" 05.47.07 # We'd like them, but not at the cost of what we consider usability. 05.47.30 # That's a very delicate balance. 05.47.50 # There's not much to balance. 05.47.57 # and I would actually have to learn what you consider usability. 05.48.00 # If we have to make a choice, we pick the one we think works best for us. 05.48.41 # the balance is "we'd like average users, but not at the cost of what we consder usability" 05.48.46 # OK 05.54.43 Join bmbl [0] (n=Miranda@unaffiliated/bmbl) 05.54.49 # I think I would have to learn from the Linux menuconfig... they changed the organization significantly from 2.4 to 2.6, and I find 2.6's menuconfig a lot more easier to use. 05.57.06 Join lol3izer [0] (i=lol3@72.2.63.189) 05.59.40 Join Zarggg_ [0] (n=zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 06.01.03 # seems some rb-related chat leaked into -community 06.01.04 Quit Zarggg (Nick collision from services.) 06.01.12 Nick Zarggg_ is now known as zarggg (n=zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 06.01.17 # the problem with rb's usb is that it's unstable on my ipod video (and nano) 06.01.22 Nick zarggg is now known as Zarggg (n=zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 06.01.40 # define "unstable 06.01.58 # for some unknown reason, sometimes it would happen that plugging in the usb cable would only charge. this is not easily reproducible. 06.02.27 Join ajonat [0] (n=ajonat@190.48.120.169) 06.02.51 # some other problems: 1) file transfer is slower than with the OF, 2) charging time is longer, 3) I don't remember exactly when, but I think I encountered a file transfer error once 06.03.52 Quit Zarggg (Client Quit) 06.04.02 # None of those, except maybe #3, are stability issues. 06.04.15 # And I'm pretty sure you can get the OF to only charge if you plug in the cable too slowly too. 06.04.56 # hm... I'll try thta 06.04.57 # *that 06.06.13 # Llorean: I'm saying that: 06.06.13 # 1. plugging in the usb cable is a stability issue 06.06.13 # 2. slow file transfer is a problem, but I didn't say it's a stability issue 06.06.13 DBUG Sent KICK wpyh to server 06.06.13 # 3. long charging time is a problem but it's not a stability issue either 06.06.13 # 4. a file transfer error is a problem 06.06.14 Kick (#rockbox wpyh :No flooding!) by logbot!n=bjst@gateway/web/cgi-irc/labb.contactor.se/x-507a9318582de8ba 06.06.46 Join wpyh [0] (n=william@123.151.132.200) 06.11.00 # the rockbox wiki doesnt specifically say what the default or ideal albumart size is it hints at 100x100 tho or is that too big? 06.11.13 # ideal is 100x100 06.11.23 # SOME wpses can handle 200x200 06.11.35 # what if its like 128x128 06.11.41 # no it will be clipped 06.11.49 # hrm ok 06.11.50 # just use the methods it suggests to generate them 06.11.52 # its very easy 06.12.06 # lol3izer: Ask what player he has first. 06.12.12 # there is a patch to allow scaled album art 06.12.23 # lol its an ipod video 80g 06.12.25 # doesn't seem to like to apply cleanly, though 06.12.33 # Llorean, sorry, i was assuming a larger screen model 06.12.44 # or I'm horrible at patching 06.12.57 Join Skail [0] (n=user@static24-72-51-82.regina.accesscomm.ca) 06.13.20 Quit bmbl ("Woah!") 06.13.35 # well i dont have coverart for everything i was going to use a 3rd party app like cover art downloader but i want to make sure its sized right 06.14.37 Quit lol3izer_ (Read error: 110 (Connection timed out)) 06.16.27 # Bawitdaba: The right album art size to use depends entirely on the WPS you choose, each one has a different expected maximum size. 06.16.50 # hrm ok 06.16.54 # most wps's on the ipod 5.5 expect 100x100 06.16.59 # some are at 200x200 06.17.04 # other sizes are rare 06.17.18 # yeah and even if i could prolly change the wps to 100x100 06.17.19 # just pick one you like and work from that 06.17.21 # lol3izer: Still, he should simply check what the WPS expects rather than trying randomly 06.17.34 # Llorean, lol ;) 06.17.50 # we both said the same thing at the same time :P 06.19.09 # %Cl|0|0|s100|s100| 06.19.12 # :P 06.19.38 # 100 by 100, as you can see, then. 06.19.56 # yeah the manual is nice 06.24.37 Join webguest49 [0] (n=430aeeaf@gateway/web/cgi-irc/labb.contactor.se/x-8f5a90373fb57424) 06.32.27 Join hasmind [0] (n=hasmind@ppp-39-9.grapevine.net.au) 06.33.26 Part kugel 06.36.06 Quit Skail (Read error: 110 (Connection timed out)) 06.36.11 Join m0f0x [0] (n=m0f0x@189-47-54-149.dsl.telesp.net.br) 06.36.38 Join Skail [0] (n=user@static24-72-51-82.regina.accesscomm.ca) 06.38.56 # what are my chances of being able to build with gcc3.4.5 ? 06.39.45 # Skail: You're not mentioning what target you're building for. 06.39.57 # And why don't you just use the right version? 06.40.26 # Llorean: for arm-elf (sansa c200).. and because I can't seem to get a working gcc4 cross compiler 06.40.34 # Skail: the rockboxdev.sh script makes getting the cross compilers installed very easy 06.41.17 Quit Wictor_ (Read error: 104 (Connection reset by peer)) 06.41.23 # scorche: I'd prefer to stick with the gentoo tools.. sometimes "3rd party" things don't play nice with portage 06.41.28 Join Wictor [0] (n=Wictor@0x57366a52.bynxx19.dynamic.dsl.tele.dk) 06.41.42 # but then, they aren't currently building me a crosscompiler, so.... 06.41.51 # Skail: better than nothing? 06.42.16 # Skail: If your linux distro won't allow you to build your own copies of things from source, you might consider picking one that offers you a little more flexibility and freedom... 06.43.06 # you can do custom ebuilds pretty easily 06.43.12 # Llorean: uhh...... it most certainly WILL allow me to, but I prefer to do things like that within portage, because it tracks things for me... easy uninstall and easy to know what is and isn't on my system 06.44.04 # Skail, you might want to consider LD_PRELOD_PATH and the fact that all unix software is naturally portable 06.44.06 # Skail: Well, Rockbox more or less requires specific GCC versions to work reliably. 06.44.14 # in the sense it dosent matter where it is running from 06.44.39 # Skail: and if portage wont do the job, but a "third party tool" which is an open perl script does? 06.44.41 # you could even do a chroot if you dont wanna muck around alot 06.44.57 # s/perl// 06.45.29 # lol3izer: yeah, chroot might be the way to go.. I dunno what LD_PRELOAD_PATH is, though 06.46.36 # Skail, it allows you to speficy an alternate place to load libaries from 06.47.02 # lol3izer: I don't really grok gcc well enough to use that effectively. 06.47.03 # so if the gcc 4 version requires conflicting libraries 06.47.04 # or something 06.49.53 Join Dhraakellian [0] (n=ntryon@cpe-69-207-147-61.rochester.res.rr.com) 06.50.23 Quit hasmind ("Leaving") 06.50.36 # meh, I guess I'll bite the bullet and use the rockboxdev script.... not like its going to clobber anything existing.. 06.50.54 # just saw the news on fsdaily. congrats on the release! 06.51.06 # Skail: in fact, it doesnt even add anything to your path ;) 06.51.58 # ...a week late seeing the news 06.52.05 # I wonder if it might confuse the gcc-config tool 06.52.45 # theres a lot of album art programs on the rb wiki, but is there any that you guys know of that will download and resize art to a cover.bmp recursively for each folder/album 06.52.49 # I don't even want to build rockbox itself - just need to write a plugin :) 06.53.21 # Skail: all it does is build the crosscompilers for you...what you do with them after (typically people just add to their PATH) is up to you 07.01.40 Join devslashnull [0] (n=delvslas@pool-71-104-112-69.lsanca.dsl-w.verizon.net) 07.02.33 # oh, for the love of........... 07.03.14 # joy.... turns out the past 3 hours I've spent fighting with the crosscompiler were wasted.. 07.03.33 # I already had it set up 07.03.52 # just forgot where it was... probably because it was non-portage 07.04.05 # gentoo ftw 07.04.12 # d'oh 07.04.23 # Bawitdaba: and why is that necessary? 07.19.33 Quit Skail ("Concoction recent by Pier.") 07.19.35 Join blueorblack [0] (n=42ce560a@gateway/web/cgi-irc/labb.contactor.se/x-97a117ba94e11e76) 07.20.52 Quit BHSPitMonkey (Remote closed the connection) 07.20.58 Quit jhulst (Remote closed the connection) 07.21.49 # I'm having a bit of an issue with my ipod, wmp isn't seeing it as a sync device 07.21.58 Part Dhraakellian ("Meddle not in the affairs of ircops, for they are (not so) subtle, and quick to anger.") 07.22.31 # i've enabled disk use and all and i can see it in explorer but not in wmp 07.22.54 # blueorblack: That's a question to ask those who provide support for WMP 07.23.04 # blueorblack: that sint really a rockbox issue 07.23.05 # Your iPod is still an iPod, and WMP probably chooses not to sync with them. 07.23.26 Quit goffa (Remote closed the connection) 07.25.17 Quit blueorblack ("CGI:IRC (EOF)") 07.26.37 *** Saving seen data "./dancer.seen" 07.29.10 Join SoulSeeker [0] (n=SoulSeek@c-98-220-230-79.hsd1.il.comcast.net) 07.29.37 Quit webguest49 ("CGI:IRC 0.5.9 (2006/06/06)") 07.31.18 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 07.32.41 # hi anyone with sansa e200 series mp3 player? 07.33.15 # I just did a headphone repair.. I broke off a resistor on the lower left, put a glob of solder, and now stereo works again.. 07.33.36 # is there anything i can do to improve rockbox's speed when going thru the menu system. i get lags pretty often 07.33.52 # devslashnull: i take it that you have an ipod video? 07.34.04 # yea 07.34.04 # SoulSeeker: did you have a question? 07.34.10 # is that a known issue ? 07.34.21 # yes. it seems sansa e200 has very unreliable headphone jack.. 07.34.28 # the soldering point seems to come off.. 07.34.34 Join goffa [0] (n=goffa@216.220.23.105) 07.34.40 # there are a lot on ebay with broken headjack.. 07.34.41 # scorche ? 07.34.57 # SoulSeeker: yup...many DAPs have this issue, though sansas seem especially fragile 07.35.10 # I am glad I somehow fixed the one I bought on ebay for $15... but I was wondering what was that small resistor that I broke off accidentally 07.35.50 # devslashnull: well, the ipod videos are not very fast due to its screen (lots of overhead)...do you notice a large improvement when playing music? 07.36.03 # it was nearly accidental i fixed thsi thing... but any idea what was that resistor connected to the headphone jack pin? 07.36.10 # scorcheno not really 07.36.33 # scorche in fact theres a lag when pausig a song or exiting the "now playing" screen 07.37.32 # anyone? I was surprised to see that mp3 player still working without a resistor... :-? 07.42.57 # anyways, I also own another sansa e260.. very cheap, good sound, compatible with rockbox.. 07.43.42 # but the screen is very fragile, the battery doesn't last long, and the proporiety cable is very hard to replace (the ones sold in Ebay stop working after few months)... 07.44.08 # i guess I will be getting iriver next time. :( 07.46.23 Join AndyI [0] (i=AndyI@212.14.205.32) 07.46.46 Join spiorf [0] (n=spiorf@host203-213-dynamic.20-79-r.retail.telecomitalia.it) 07.49.23 Quit jhulst (Remote closed the connection) 07.55.27 Quit miepchen^schlaf_ () 07.57.27 Quit AndyIL (Read error: 110 (Connection timed out)) 07.59.12 Join austriancoder [0] (n=austrian@rockbox/developer/austriancoder) 08.05.39 Quit Seed ("cu, Andre") 08.09.34 Part toffe82 08.18.49 Quit spiorf (Remote closed the connection) 08.19.24 Join happosade [0] (n=happosad@cs181163186.pp.htv.fi) 08.19.47 # Hello 08.21.49 Quit tessarakt ("Client exiting") 08.33.46 Quit Nibbler (Read error: 110 (Connection timed out)) 08.34.09 Join Nibbler [0] (n=Nibbler@e181073043.adsl.alicedsl.de) 08.35.18 # lord this 3.0 release has brought some clots :) 08.35.30 Quit BigBambi (Read error: 60 (Operation timed out)) 08.38.53 Part devslashnull ("Leaving") 08.44.42 Join Rob2222 [0] (n=Miranda@p4FDCC548.dip.t-dialin.net) 08.46.20 Quit at0m|c (Read error: 104 (Connection reset by peer)) 08.46.32 Join at0m|c [0] (n=at0m@78-20-136-118.access.telenet.be) 08.48.28 Join n1s [0] (n=nils@rockbox/developer/n1s) 08.49.33 Join ender` [0] (i=krneki@foo.eternallybored.org) 08.52.39 Quit pixelma2 ("-") 08.52.57 Join pixelma [50] (i=pixelma@rockbox/staff/pixelma) 08.55.03 Quit Nimdae (Read error: 104 (Connection reset by peer)) 08.56.57 Join Nimdae [0] (n=nimmeh@static-71-164-213-195.dllstx.fios.verizon.net) 09.00.00 Join Bagderr [241] (n=daniel@rockbox/developer/bagder) 09.02.04 Quit Rob2223 (Read error: 110 (Connection timed out)) 09.02.44 Nick Bagderr is now known as B4gder (n=daniel@rockbox/developer/bagder) 09.04.35 Join petur [50] (n=petur@rockbox/developer/petur) 09.05.03 Quit gevaerts (Nick collision from services.) 09.05.15 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 09.16.07 Join Acky [0] (n=omgwtfbb@cpc2-stok5-0-0-cust754.bagu.cable.ntl.com) 09.16.12 # another rockbox article from lifehacker http://lifehacker.com/5056370/breathe-new-life-into-your-aging-mp3-player-with-rockbox 09.17.00 # seen it 09.17.58 # * Llorean is glad the default made it into his list of favorite themes. 09.18.33 Join LinusN [0] (n=linus@rockbox/developer/LinusN) 09.18.56 # I am using Rockbox 3.0 on my sansa.. good job. 09.19.21 # the windows installer was easy to use (though the skin downloading doesn't work yet) 09.19.43 # SoulSeeker: it isnt meant to 09.19.55 # ic. 09.20.09 # anyways, no one had broken headjack problem with sansa? 09.20.19 # lots of people have... 09.20.44 # how do people usually fix it? 09.21.00 # it depends on what is broken, but i thought you already fixed it 09.21.05 # also, any idea what was the resistor connected to the headphone jack pin? 09.21.16 # just curious. 09.21.26 # i ordered another broken E200 from ebay. :) 09.22.11 # it could be a few things 09.22.23 Quit happosade (Read error: 104 (Connection reset by peer)) 09.24.21 # thus far, no apparent negative effect. i wonder if the resistor is to prevent battery train through head phones.. 09.24.33 # petur: YOur commit still won't work, if I don't overlook something 09.24.46 # Iiuc the #ifdefs introduced in pcm-pp.c also need fixing 09.24.50 # * petur sighs 09.25.13 # SoulSeeker: no apparent difference in volume?...resistors are cheap anyway 09.25.15 Quit Acksaw (Read error: 60 (Operation timed out)) 09.25.44 # scorche, it's extremely tiny. 1.5mm.. my soldering skill isn't good enough :( oh well. 09.25.52 # amiconn: well spotted :/ 09.26.14 # i wouldnt call that extremely tiny, but /shrug 09.26.38 *** Saving seen data "./dancer.seen" 09.26.52 # Soulseeker: might be one of these http://hackaday.com/2008/09/29/parts-01uf-decoupling-capacitors/ 09.27.18 # homielowe: why did you link that? 09.28.13 # homielowe, that looks like it.. the tiny ones.. 09.28.20 # homielowe: you do know that is talking about power supply regulation, right? 09.28.35 # SoulSeeker: it looks like any other SMD resistors 09.28.43 # homielowe: that is even a capacitor...not a resistor.. 09.29.16 # heh.. not much skills here. :( 09.29.41 # * homielowe goes to the corner 09.30.31 # soap: What's up with your build server? 09.32.17 # ruining our nice greenness =/ 09.32.38 Join fragilematter [0] (n=barbu_do@92.81.250.158) 09.34.04 # I guess I should disable sims on his host until resolved 09.35.23 # wow... we have 20 buildservers already... 09.35.26 # the new host by Nimdae seems to run fine 09.36.16 # yeah, 20 working hosts 09.36.24 # I think there are a few currently unavailable too 09.37.18 # xen is fast =/ 09.39.19 # I think I'll try disabling lostlogix's host 09.39.37 # at least for sims 09.40.17 # oh god, tell me interix comes with a bash shell somewhere 09.42.56 Join klos [0] (i=hans@60-241-220-105.static.tpgi.com.au) 09.43.09 # are there screenshots availabe for the new version 3.0 09.43.10 # ? 09.43.26 # klos: all the way through the WpsGallery 09.43.26 # amiconn: I got gcc4.3.0 to build a working rockbox for h300, it required a couple of tweaks to the rockbox code and some linker scripts though, and had a few issues. 1) it didn't like the inline asm in libmad when using O2, worked with O1 though, In tremor a wrong assembler bug was triggered (which i reported but it hasn't been fixed yet, it is probably present but latent in earlier versions too) 09.43.33 # klos: the manual? 09.43.49 # havent checked it :) 09.45.23 Join DerDome [0] (n=DerDome@dslb-082-083-248-198.pools.arcor-ip.net) 09.45.27 # ah ok thx, do you guys think it will be possible someday to use .cue files along with mp3 for live sets or mixes ? 09.45.43 # klos: rockbox supports cue files 09.45.51 # ah really 09.45.57 # haha i havent checked rockbox for ages 09.46.00 # sweet :) 09.46.07 # thx 09.46.08 # preliminary tests with gcc4.3 showed about no performance change in mad, a sizable regression in Tremor and a major speedup i aac (this was before the mdct unification so might not apply anymore) 09.51.03 Join tucoz [0] (i=528612c1@gateway/web/ajax/mibbit.com/x-641ffab3d9f6bc89) 09.51.11 # (if anyone is interested the wrong asm bug is #35018 in gcc bugzilla) 09.52.30 # Bagder: hi. shouldn't there be a link to the 3.0 manual from the manual page linked from the side menu? 09.53.28 # probably, yes 09.54.11 # the site is in svn you know ;-) 09.54.21 # * B4gder fixes 09.54.33 # aha. how cool. didn't know that 09.55.53 # it just doesn't update automatically 09.56.25 # B4gder: I have to congratulate you for being persistent in getting this release out. feels great now, and with very positive response overall. 09.56.51 # yeah, I think that despite the problems it has it was a good thing to get out 09.57.00 # yep. for sure 09.58.02 # i guess it makes further releases less intimidating... 09.58.35 # back to work. see you 09.58.37 Part tucoz 09.58.53 # I think we should make a checklist for the next release 09.59.13 # of things to have fixed and done before we announce it 09.59.30 # great idea 09.59.38 # * GodEater volunteers B4gder to make such a list 09.59.43 # yay! 09.59.48 # * B4gder feels selected 10.00.45 # it would be nice to have the themes site up for 3.1 10.01.44 # now, all we need is that *someone* to do the work ;) 10.02.07 # * B4gder looks around for someone 10.02.26 # I thought I saw him hiding around the corner a while back 10.04.14 # soo, on a slightly related matter what would be the correct version to use for the new ipod bootloaders, and what is the clean way to set APPSVERSION? (ipods seem by far the most cf modded targets so I think we/I should focus on getting these up on the download site soon, very little interest in the bootloaders though :( 10.05.19 # * scorche peeks out from around his corner 10.05.26 # n1s: co-incidentally, I think it's "v3" according to http://svn.rockbox.org/viewvc.cgi/tags/ 10.05.49 # linuxstb: aha!, nice :) 10.07.01 # I _think_ you just do "VERSION=v3 make" 10.07.36 # Or maybe "make VERSION=v3"... (or maybe they are equivalent...) 10.08.32 Quit DerDome ("Leaving.") 10.08.52 Nick fxb__ is now known as fxb (n=felixbru@h1252615.stratoserver.net) 10.09.17 Quit at0m|c (Read error: 110 (Connection timed out)) 10.12.38 # Llorean gevaerts: original firmware doesnt hold up to 10h :/ 10.12.48 # morning first :) 10.13.31 # linuxstb: I think they are equivalent 10.14.50 Quit m0f0x (Read error: 104 (Connection reset by peer)) 10.14.57 Part fragilematter 10.16.27 # B4gder, linuxstb: interestingly 'make VERSION=v3' seems to have worked, the r18xxx-3.0-08xxxx string was replaced by v3 but 'VERSION=v3 make' didn't, anyways, I'm building a batch now :) 10.17.16 # cool, do you have a script to build the entire set? 10.17.23 # no... 10.17.29 # n1s: I _think_ this is the script I used to build the last set of ipod bootloaders - note that I used "VERSION=2.0". http://www.pastebin.ca/1214531 10.18.16 # linuxstb: thanks, will go with 3.0 then, even nicer match :) 10.18.42 Join culture [0] (n=none@cpc1-bele3-0-0-cust658.belf.cable.ntl.com) 10.19.06 # RyoS: So you've either got a bad battery, or a bad player. 10.19.54 Join m0f0x [0] (n=m0f0x@189-47-54-149.dsl.telesp.net.br) 10.20.32 # Llorean: soudns like the players fault.. 10.20.50 # i wonder if cowon could have a look at it "now".. 10.20.52 Part Llorean 10.21.04 Join Llorean [0] (n=DarkkOne@rockbox/administrator/Llorean) 10.23.31 Quit jeffdameth1 (Read error: 110 (Connection timed out)) 10.24.42 Join jeffdameth [0] (n=jeff@dyndsl-091-096-063-239.ewe-ip-backbone.de) 10.27.48 Join lasser [0] (n=chatzill@Wa291.w.pppool.de) 10.28.21 # linuxstb: worked very nicely :) 10.29.21 # should they be retested (after amiconn's changes on the branch) or are we confident they will work? :) 10.29.30 Join Twisty [0] (n=mhesten@242.80-202-24.nextgentel.com) 10.29.35 # I would say they definitely need testing... 10.29.40 # It's easy to break bootloaders 10.30.00 Part pixelma 10.30.23 Join pixelma2 [0] (n=marianne@rockbox/staff/pixelma) 10.32.16 # ok, uploaded new ipod bootloaders in FS#9369 10.43.13 Quit Twst (Read error: 110 (Connection timed out)) 10.44.41 Quit lasser (brown.freenode.net irc.freenode.net) 10.44.41 NSplit brown.freenode.net irc.freenode.net 10.44.41 Quit ajonat (brown.freenode.net irc.freenode.net) 10.44.41 Quit lol3izer (brown.freenode.net irc.freenode.net) 10.44.41 Quit ameyer (brown.freenode.net irc.freenode.net) 10.44.41 Quit avis (brown.freenode.net irc.freenode.net) 10.44.41 Quit tchan (brown.freenode.net irc.freenode.net) 10.44.41 Quit ryanakca (brown.freenode.net irc.freenode.net) 10.44.41 Quit Zom (brown.freenode.net irc.freenode.net) 10.44.41 Quit Galois (brown.freenode.net irc.freenode.net) 10.44.41 Quit GodEater_ (brown.freenode.net irc.freenode.net) 10.44.41 Quit funky (brown.freenode.net irc.freenode.net) 10.44.41 Quit B4gder (brown.freenode.net irc.freenode.net) 10.44.41 Quit crashd (brown.freenode.net irc.freenode.net) 10.44.42 Quit Gareth (brown.freenode.net irc.freenode.net) 10.45.06 Quit ChanServ (brown.freenode.net irc.freenode.net) 10.45.06 Quit jeffdameth (brown.freenode.net irc.freenode.net) 10.45.06 Quit m0f0x (brown.freenode.net irc.freenode.net) 10.45.06 Quit Wictor (brown.freenode.net irc.freenode.net) 10.45.06 Quit pabs (brown.freenode.net irc.freenode.net) 10.45.06 Quit Nevtus (brown.freenode.net irc.freenode.net) 10.45.06 Quit SUSaiyan` (brown.freenode.net irc.freenode.net) 10.45.06 Quit Kopfgeldjaeger (brown.freenode.net irc.freenode.net) 10.45.06 Quit basti (brown.freenode.net irc.freenode.net) 10.45.06 Quit shodanX (brown.freenode.net irc.freenode.net) 10.45.06 Quit rvvs89 (brown.freenode.net irc.freenode.net) 10.45.06 Quit Nimdae (brown.freenode.net irc.freenode.net) 10.45.06 Quit neddy (brown.freenode.net irc.freenode.net) 10.45.06 Quit BlakeJohnson86 (brown.freenode.net irc.freenode.net) 10.45.06 Quit Llorean (brown.freenode.net irc.freenode.net) 10.45.06 Quit linuxstb (brown.freenode.net irc.freenode.net) 10.45.06 Quit TMM (brown.freenode.net irc.freenode.net) 10.45.06 Quit Dieterbe (brown.freenode.net irc.freenode.net) 10.45.06 Quit HellDragon (brown.freenode.net irc.freenode.net) 10.45.06 Quit ze (brown.freenode.net irc.freenode.net) 10.45.06 Quit maddler (brown.freenode.net irc.freenode.net) 10.45.06 Quit culture (brown.freenode.net irc.freenode.net) 10.45.06 Quit petur (brown.freenode.net irc.freenode.net) 10.45.06 Quit SoulSeeker (brown.freenode.net irc.freenode.net) 10.45.06 Quit nplus (brown.freenode.net irc.freenode.net) 10.45.06 Quit wpyh (brown.freenode.net irc.freenode.net) 10.45.06 Quit fyrestorm (brown.freenode.net irc.freenode.net) 10.45.06 Quit havien (brown.freenode.net irc.freenode.net) 10.45.06 Quit midkay (brown.freenode.net irc.freenode.net) 10.45.06 Quit dereine (brown.freenode.net irc.freenode.net) 10.45.06 Quit lacrstech (brown.freenode.net irc.freenode.net) 10.45.06 Quit Bagder (brown.freenode.net irc.freenode.net) 10.45.06 Quit Unhelpful (brown.freenode.net irc.freenode.net) 10.45.06 Quit idshark (brown.freenode.net irc.freenode.net) 10.45.06 Quit plus_M (brown.freenode.net irc.freenode.net) 10.47.50 NHeal brown.freenode.net irc.freenode.net 10.47.50 NJoin ChanServ [0] (ChanServ@services.) 10.47.50 NJoin jeffdameth [0] (n=jeff@dyndsl-091-096-063-239.ewe-ip-backbone.de) 10.47.50 NJoin Llorean [0] (n=DarkkOne@rockbox/administrator/Llorean) 10.47.50 NJoin m0f0x [0] (n=m0f0x@189-47-54-149.dsl.telesp.net.br) 10.47.50 NJoin culture [0] (n=none@cpc1-bele3-0-0-cust658.belf.cable.ntl.com) 10.47.50 NJoin petur [50] (n=petur@rockbox/developer/petur) 10.47.50 NJoin Nimdae [0] (n=nimmeh@static-71-164-213-195.dllstx.fios.verizon.net) 10.47.50 NJoin SoulSeeker [0] (n=SoulSeek@c-98-220-230-79.hsd1.il.comcast.net) 10.47.50 NJoin Wictor [0] (n=Wictor@0x57366a52.bynxx19.dynamic.dsl.tele.dk) 10.47.50 NJoin wpyh [0] (n=william@123.151.132.200) 10.47.50 NJoin neddy [0] (n=john@nat/sun/x-c165d36e37ceab88) 10.47.50 NJoin pabs [0] (n=pabs@xor.pablotron.org) 10.47.50 Join Nevtus [0] (n=Nevtus@unaffiliated/nevtus) 10.47.50 NJoin BlakeJohnson86 [0] (n=bjohnson@c-24-118-162-123.hsd1.mn.comcast.net) 10.47.50 NJoin SUSaiyan` [0] (n=SUSaiyan@cc84863-b.zwoll1.ov.home.nl) 10.47.50 NJoin nplus [0] (n=nplus@141.25.Globcom.Net) 10.47.50 NJoin fyrestorm [0] (n=fyre@cpe-68-173-168-94.nyc.res.rr.com) 10.47.50 NJoin havien [0] (n=none@68-189-143-101.dhcp.wlwl.wa.charter.com) 10.47.50 NJoin linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 10.47.50 NJoin TMM [0] (n=hp@5ED10264.cable.ziggo.nl) 10.47.50 NJoin Dieterbe [0] (n=Dieterbe@213.219.168.211.adsl.dyn.edpnet.net) 10.47.50 Join HellDragon [0] (n=jd@Wikipedia/HellDragon) 10.47.50 NJoin Kopfgeldjaeger [0] (n=nicolai@monitor-mode-enabled-on-mon0.phy0.de) 10.47.50 NJoin dereine [0] (n=dereine@217-20-118-50.internetserviceteam.com) 10.47.50 NJoin midkay [0] (n=midkay@rockbox/developer/midkay) 10.47.50 NJoin basti [0] (n=basti@85.214.109.173) 10.47.50 NJoin lacrstech [0] (n=lacrstec@209.216.196.2) 10.47.50 NJoin shodanX [0] (n=shodanX@arie.informatik.uni-erlangen.de) 10.47.50 NJoin Bagder [241] (n=daniel@rockbox/developer/bagder) 10.47.50 NJoin ze [0] (i=ze@cpe-75-82-143-231.socal.res.rr.com) 10.47.50 NJoin Unhelpful [0] (n=Militant@pool-98-117-9-134.hrbgpa.fios.verizon.net) 10.47.50 NJoin rvvs89 [0] (n=rvvs89@pdpc/supporter/active/rvvs89) 10.47.50 NJoin idshark [0] (i=chainsaw@i.will.tell.u.some.hotstories.de) 10.47.50 NJoin plus_M [0] (n=plus@li26-205.members.linode.com) 10.47.50 NJoin maddler [0] (n=maddler@cabbage.komputika.net) 10.47.50 Mode "#rockbox +o ChanServ " by irc.freenode.net 10.56.53 Join spiorf [0] (n=spiorf@host203-213-dynamic.20-79-r.retail.telecomitalia.it) 10.57.38 NJoin lasser [0] (n=chatzill@Wa291.w.pppool.de) 10.57.38 NJoin B4gder [241] (n=daniel@rockbox/developer/bagder) 10.57.38 NJoin ajonat [0] (n=ajonat@190.48.120.169) 10.57.38 NJoin lol3izer [0] (i=lol3@72.2.63.189) 10.57.38 NJoin ameyer [0] (n=ameyer17@adsl-75-57-180-230.dsl.emhril.sbcglobal.net) 10.57.38 NJoin avis [0] (n=ident@pdpc/supporter/student/avis) 10.57.38 NJoin tchan [0] (n=tchan@lunar-linux/developer/tchan) 10.57.38 NJoin ryanakca [0] (n=ryan@ubuntu/member/ryanakca) 10.57.38 Join Zom [0] (n=zom@reactos/tester/Zom) 10.57.38 NJoin funky [0] (n=repulse@unaffiliated/funky) 10.57.38 NJoin Gareth [0] (i=gareth@www.wiked.org) 10.57.38 NJoin Galois [0] (i=djao@efnet-math.org) 10.57.38 NJoin GodEater_ [0] (n=ge@rockbox/staff/GodEater) 10.57.38 NJoin crashd [0] (i=foobar@lostnode.org) 11.01.32 Quit GodEater (Remote closed the connection) 11.01.32 Quit perrikwp (Remote closed the connection) 11.04.48 Quit freqmod_qu (brown.freenode.net irc.freenode.net) 11.04.48 Quit RyoS (brown.freenode.net irc.freenode.net) 11.04.48 Quit suom1 (brown.freenode.net irc.freenode.net) 11.04.48 Quit preglow (brown.freenode.net irc.freenode.net) 11.04.48 Quit Zambezi (brown.freenode.net irc.freenode.net) 11.04.48 Quit pixelma2 (brown.freenode.net irc.freenode.net) 11.04.48 Quit blkhawk (brown.freenode.net irc.freenode.net) 11.04.48 Quit HBK (brown.freenode.net irc.freenode.net) 11.04.48 Quit thegeek (brown.freenode.net irc.freenode.net) 11.04.48 Quit jfc (brown.freenode.net irc.freenode.net) 11.04.48 Quit ch4os (brown.freenode.net irc.freenode.net) 11.04.48 Quit lostlogic (brown.freenode.net irc.freenode.net) 11.04.48 Quit maraz (brown.freenode.net irc.freenode.net) 11.04.48 Quit liiwi (brown.freenode.net irc.freenode.net) 11.04.48 Quit scorche|sh (brown.freenode.net irc.freenode.net) 11.04.48 Quit courtc (brown.freenode.net irc.freenode.net) 11.04.48 Quit Neovanglist (brown.freenode.net irc.freenode.net) 11.04.48 Quit gevaerts (brown.freenode.net irc.freenode.net) 11.04.48 Quit XavierGr (brown.freenode.net irc.freenode.net) 11.04.48 Quit Hillshum (brown.freenode.net irc.freenode.net) 11.04.48 Quit Dementio (brown.freenode.net irc.freenode.net) 11.04.48 Quit Lambdumb (brown.freenode.net irc.freenode.net) 11.04.48 Quit Xerion (brown.freenode.net irc.freenode.net) 11.04.48 Quit [omni] (brown.freenode.net irc.freenode.net) 11.04.48 Quit scorche (brown.freenode.net irc.freenode.net) 11.04.48 Quit ruskie (brown.freenode.net irc.freenode.net) 11.04.48 Quit rasher (brown.freenode.net irc.freenode.net) 11.04.48 Quit Winkie (brown.freenode.net irc.freenode.net) 11.04.48 Quit jon-kha (brown.freenode.net irc.freenode.net) 11.04.48 Quit Slasheri (brown.freenode.net irc.freenode.net) 11.04.48 Quit Rob2222 (brown.freenode.net irc.freenode.net) 11.04.48 Quit FRiZzO (brown.freenode.net irc.freenode.net) 11.04.48 Quit reacocard (brown.freenode.net irc.freenode.net) 11.04.48 Quit iSuck (brown.freenode.net irc.freenode.net) 11.04.48 Quit homielowe (brown.freenode.net irc.freenode.net) 11.04.48 Quit nuonguy (brown.freenode.net irc.freenode.net) 11.04.48 Quit lastebil (brown.freenode.net irc.freenode.net) 11.04.48 Quit parafin (brown.freenode.net irc.freenode.net) 11.04.48 Quit Saucisson (brown.freenode.net irc.freenode.net) 11.04.48 Quit Naked (brown.freenode.net irc.freenode.net) 11.04.48 Quit blithe (brown.freenode.net irc.freenode.net) 11.04.48 Quit markun (brown.freenode.net irc.freenode.net) 11.04.48 Quit lids (brown.freenode.net irc.freenode.net) 11.04.48 Quit Haudrauf (brown.freenode.net irc.freenode.net) 11.04.48 Quit sbhsu (brown.freenode.net irc.freenode.net) 11.04.48 Quit LinusN (brown.freenode.net irc.freenode.net) 11.04.48 Quit andrew__ (brown.freenode.net irc.freenode.net) 11.04.48 Quit crwl (brown.freenode.net irc.freenode.net) 11.04.48 Quit flux (brown.freenode.net irc.freenode.net) 11.04.48 Quit dionoea (brown.freenode.net irc.freenode.net) 11.04.48 Quit wurscht (brown.freenode.net irc.freenode.net) 11.04.48 Quit Bjoern-Erik (brown.freenode.net irc.freenode.net) 11.04.48 Quit robotgeek (brown.freenode.net irc.freenode.net) 11.04.48 Quit fred_2 (brown.freenode.net irc.freenode.net) 11.06.05 Quit Horscht ("We don't make mistakes, we just have happy little accidents") 11.06.07 Join Horscht [0] (n=Horscht@p4FD4EBF8.dip.t-dialin.net) 11.06.34 Quit ender` (Read error: 104 (Connection reset by peer)) 11.07.08 Join ender` [0] (i=krneki@foo.eternallybored.org) 11.07.30 Quit Nevtus (Read error: 60 (Operation timed out)) 11.08.59 Quit lol3izer (Read error: 104 (Connection reset by peer)) 11.13.22 Quit SoulSeeker ("Leaving") 11.16.08 Join moos [0] (i=moos@81-66-128-18.rev.numericable.fr) 11.16.08 Join pixelma2 [0] (n=marianne@rockbox/staff/pixelma) 11.16.08 Join LinusN [0] (n=linus@rockbox/developer/LinusN) 11.16.08 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 11.16.08 Join Rob2222 [0] (n=Miranda@p4FDCC548.dip.t-dialin.net) 11.16.08 Join FRiZzO [0] (n=frank@74.13.73.175) 11.16.08 Join reacocard [0] (n=reacocar@WL-431.CINE.HMC.Edu) 11.16.08 Join blkhawk [0] (n=blkhawk@g229212180.adsl.alicedsl.de) 11.16.08 Join iSuck [0] (n=user@221.221.144.56) 11.16.08 Join RyoS [0] (n=ryo@cl-1804.ham-01.de.sixxs.net) 11.16.08 Join freqmod_qu [0] (i=quassel@2001:700:300:1800:213:d3ff:fee9:5ed0) 11.16.08 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 11.16.08 Join HBK [0] (i=hbk@pool-71-96-74-73.dfw.dsl-w.verizon.net) 11.16.08 Join thegeek [0] (n=nnscript@s080a.studby.ntnu.no) 11.16.08 Join Hillshum [0] (n=chatzill@75-165-239-6.slkc.qwest.net) 11.16.08 Join Dementio [0] (n=dementio@211.45.234.45) 11.16.08 Join rasher [50] (n=rasher@rockbox/developer/rasher) 11.16.08 Join jfc [0] (n=john@dpc691978010.direcpc.com) 11.16.08 Join Lambdumb [0] (n=Lambda@12-203-112-233.client.mchsi.com) 11.16.08 Join homielowe [0] (n=homielow@unaffiliated/homielowe) 11.16.08 Join nuonguy [0] (n=john@c-71-198-1-139.hsd1.ca.comcast.net) 11.16.08 Join lastebil [0] (n=truck@cube.lomal.la) 11.16.08 Join Winkie [0] (n=urmom@ur.fa.gs) 11.16.08 Join [omni] [0] (n=omni@undecided.bestii.com) 11.16.08 Join parafin [0] (i=parafin@paraf.in) 11.16.08 Join Saucisson [0] (n=miaou@ks351860.kimsufi.com) 11.16.08 Join Xerion [0] (n=xerion@cp198589-d.landg1.lb.home.nl) 11.16.08 Join suom1 [0] (i=markus@viitamaki.net) 11.16.08 Join jon-kha [0] (i=jon-kha@kahvi.eu.org) 11.16.08 Join Naked [0] (i=naked@naked.iki.fi) 11.16.08 Join ch4os [0] (n=ch4os@unaffiliated/ch4os/x-059673) 11.16.08 Join lostlogic [50] (n=lostlogi@rockbox/developer/lostlogic) 11.16.08 Join maraz [0] (i=maraz@xob.kapsi.fi) 11.16.08 Join liiwi [0] (i=liiwi@idle.fi) 11.16.08 Join courtc [0] (n=court@c-24-99-230-218.hsd1.ga.comcast.net) 11.16.08 Join Neovanglist [0] (i=Neovangl@69.31.129.33) 11.16.08 Join scorche|sh [50] (n=scorche@rockbox/administrator/scorche) 11.16.08 Join markun [50] (n=markun@rockbox/developer/markun) 11.16.08 Join scorche [0] (i=Blah@rockbox/administrator/scorche) 11.16.08 Join Haudrauf [0] (n=hau@HSI-KBW-091-089-008-100.hsi2.kabelbw.de) 11.16.08 Join sbhsu [0] (n=a6530466@Zion.dorm.au.edu.tw) 11.16.08 Join ruskie [0] (i=ruskie@sourcemage/mage/ruskie) 11.16.08 Join Slasheri [0] (i=miipekk@xen.ihme.org) 11.16.08 Join crwl [0] (n=crawlie@a91-154-18-71.elisa-laajakaista.fi) 11.16.08 Join dionoea [0] (n=dionoea@videolan/developer/dionoea) 11.16.08 Join flux [0] (i=flux@jolt.modeemi.cs.tut.fi) 11.16.08 Join andrew__ [0] (n=andrew@stjhnf0124w-142162076195.pppoe-dynamic.nl.aliant.net) 11.16.08 Join Bjoern-Erik [0] (n=Bjoern@173.80-202-110.nextgentel.com) 11.16.08 Join robotgeek [0] (n=robotgee@ubuntu/member/robotgeek) 11.16.08 Join wurscht [0] (i=wurst@telia.ffm.us-dialin.net) 11.16.08 Join fred_2 [0] (i=fred@hpc-cluster.hamburgnet.de) 11.16.08 Join Zambezi [0] (i=stolgfor@itslyna.se) 11.16.08 Join preglow [0] (i=thomj@rockbox/developer/preglow) 11.16.08 Join lids [0] (n=lds@piggledy.org) 11.16.08 Join blithe [0] (n=blithe@li35-144.members.linode.com) 11.16.24 Quit Horscht (brown.freenode.net irc.freenode.net) 11.16.24 NSplit brown.freenode.net irc.freenode.net 11.16.24 Quit lasser (brown.freenode.net irc.freenode.net) 11.16.24 Quit ameyer (brown.freenode.net irc.freenode.net) 11.16.24 Quit GodEater_ (brown.freenode.net irc.freenode.net) 11.16.24 Quit Galois (brown.freenode.net irc.freenode.net) 11.16.24 Quit ajonat (brown.freenode.net irc.freenode.net) 11.16.24 Quit B4gder (brown.freenode.net irc.freenode.net) 11.16.24 Quit tchan (brown.freenode.net irc.freenode.net) 11.16.24 Quit crashd (brown.freenode.net irc.freenode.net) 11.16.24 Quit avis (brown.freenode.net irc.freenode.net) 11.16.24 Quit funky (brown.freenode.net irc.freenode.net) 11.16.24 Quit ryanakca (brown.freenode.net irc.freenode.net) 11.16.24 Quit Zom (brown.freenode.net irc.freenode.net) 11.16.24 Quit Gareth (brown.freenode.net irc.freenode.net) 11.20.07 Quit culture (Connection timed out) 11.20.12 Join Nevtus [0] (n=Nevtus@unaffiliated/nevtus) 11.22.06 Quit ender` (brown.freenode.net irc.freenode.net) 11.22.06 Quit shodanX (brown.freenode.net irc.freenode.net) 11.22.06 Quit Wictor (brown.freenode.net irc.freenode.net) 11.22.06 Quit Kopfgeldjaeger (brown.freenode.net irc.freenode.net) 11.22.06 Quit basti (brown.freenode.net irc.freenode.net) 11.22.06 Quit SUSaiyan` (brown.freenode.net irc.freenode.net) 11.22.06 Quit pabs (brown.freenode.net irc.freenode.net) 11.22.06 Quit rvvs89 (brown.freenode.net irc.freenode.net) 11.22.06 Quit m0f0x (brown.freenode.net irc.freenode.net) 11.22.06 Quit jeffdameth (brown.freenode.net irc.freenode.net) 11.23.20 NHeal brown.freenode.net irc.freenode.net 11.23.20 NJoin ender` [0] (i=krneki@foo.eternallybored.org) 11.23.20 NJoin jeffdameth [0] (n=jeff@dyndsl-091-096-063-239.ewe-ip-backbone.de) 11.23.20 NJoin m0f0x [0] (n=m0f0x@189-47-54-149.dsl.telesp.net.br) 11.23.20 NJoin Wictor [0] (n=Wictor@0x57366a52.bynxx19.dynamic.dsl.tele.dk) 11.23.20 NJoin pabs [0] (n=pabs@xor.pablotron.org) 11.23.20 NJoin SUSaiyan` [0] (n=SUSaiyan@cc84863-b.zwoll1.ov.home.nl) 11.23.20 NJoin Kopfgeldjaeger [0] (n=nicolai@monitor-mode-enabled-on-mon0.phy0.de) 11.23.20 NJoin basti [0] (n=basti@85.214.109.173) 11.23.20 NJoin shodanX [0] (n=shodanX@arie.informatik.uni-erlangen.de) 11.23.20 NJoin rvvs89 [0] (n=rvvs89@pdpc/supporter/active/rvvs89) 11.26.42 *** Saving seen data "./dancer.seen" 11.42.40 Quit spiorf (Remote closed the connection) 11.50.54 Join orly_owl [0] (n=DavoDink@c122-108-109-84.sunsh1.vic.optusnet.com.au) 11.51.17 Quit advcomp2019 (Read error: 104 (Connection reset by peer)) 11.51.30 Join advcomp2019 [0] (n=advcomp2@unaffiliated/advcomp2019) 11.53.40 NJoin B4gder [241] (n=daniel@rockbox/developer/bagder) 11.53.40 NJoin Horscht [0] (n=Horscht@p4FD4EBF8.dip.t-dialin.net) 11.53.40 NJoin lasser [0] (n=chatzill@Wa291.w.pppool.de) 11.53.40 NJoin ajonat [0] (n=ajonat@190.48.120.169) 11.53.40 NJoin ameyer [0] (n=ameyer17@adsl-75-57-180-230.dsl.emhril.sbcglobal.net) 11.53.40 NJoin avis [0] (n=ident@pdpc/supporter/student/avis) 11.53.40 NJoin tchan [0] (n=tchan@lunar-linux/developer/tchan) 11.53.40 NJoin ryanakca [0] (n=ryan@ubuntu/member/ryanakca) 11.53.40 NJoin Zom [0] (n=zom@reactos/tester/Zom) 11.53.40 NJoin funky [0] (n=repulse@unaffiliated/funky) 11.53.40 NJoin Gareth [0] (i=gareth@www.wiked.org) 11.53.40 NJoin Galois [0] (i=djao@efnet-math.org) 11.53.40 NJoin GodEater_ [0] (n=ge@rockbox/staff/GodEater) 11.53.40 NJoin crashd [0] (i=foobar@lostnode.org) 11.54.53 Nick fxb is now known as fxb__ (n=felixbru@h1252615.stratoserver.net) 11.56.00 Join webguest60 [0] (n=c2cbc962@gateway/web/cgi-irc/labb.contactor.se/session) 11.56.02 Quit Horscht (Client Quit) 12.00.32 Quit ajonat () 12.03.11 # What's the biggest memory card the Ondio can take? 12.05.53 Quit linuxstb (Read error: 110 (Connection timed out)) 12.08.09 Join webguest44 [0] (n=c2cbc962@gateway/web/cgi-irc/labb.contactor.se/x-86a19d474f6abade) 12.08.31 Quit webguest44 (Client Quit) 12.09.12 Quit webguest60 ("CGI:IRC") 12.09.18 Quit lasser (brown.freenode.net irc.freenode.net) 12.09.18 NSplit brown.freenode.net irc.freenode.net 12.09.18 Quit ameyer (brown.freenode.net irc.freenode.net) 12.09.18 Quit GodEater_ (brown.freenode.net irc.freenode.net) 12.09.18 Quit Galois (brown.freenode.net irc.freenode.net) 12.09.18 Quit tchan (brown.freenode.net irc.freenode.net) 12.09.18 Quit crashd (brown.freenode.net irc.freenode.net) 12.09.18 Quit avis (brown.freenode.net irc.freenode.net) 12.09.18 Quit funky (brown.freenode.net irc.freenode.net) 12.09.18 Quit ryanakca (brown.freenode.net irc.freenode.net) 12.09.18 Quit Zom (brown.freenode.net irc.freenode.net) 12.09.18 Quit Gareth (brown.freenode.net irc.freenode.net) 12.09.18 Quit B4gder (brown.freenode.net irc.freenode.net) 12.10.54 Nick Naked is now known as Hadaka (i=naked@naked.iki.fi) 12.20.01 Join webguest24 [0] (n=548d59c4@gateway/web/cgi-irc/labb.contactor.se/x-cae516badeafcb26) 12.20.35 Quit webguest24 (Client Quit) 12.22.43 Join vitja [0] (n=vitja@79.120.98.174) 12.23.10 Join Horscht [0] (n=Horscht@xbmc/user/horscht) 12.23.44 Join funman [0] (n=fun@AAnnecy-257-1-67-132.w90-36.abo.wanadoo.fr) 12.23.44 NHeal brown.freenode.net irc.freenode.net 12.23.44 NJoin B4gder [241] (n=daniel@rockbox/developer/bagder) 12.23.44 NJoin lasser [0] (n=chatzill@Wa291.w.pppool.de) 12.23.44 NJoin ameyer [0] (n=ameyer17@adsl-75-57-180-230.dsl.emhril.sbcglobal.net) 12.23.44 NJoin avis [0] (n=ident@pdpc/supporter/student/avis) 12.23.44 NJoin tchan [0] (n=tchan@lunar-linux/developer/tchan) 12.23.44 NJoin ryanakca [0] (n=ryan@ubuntu/member/ryanakca) 12.23.44 NJoin Zom [0] (n=zom@reactos/tester/Zom) 12.23.44 NJoin funky [0] (n=repulse@unaffiliated/funky) 12.23.44 NJoin Gareth [0] (i=gareth@www.wiked.org) 12.23.44 NJoin Galois [0] (i=djao@efnet-math.org) 12.23.44 NJoin GodEater_ [0] (n=ge@rockbox/staff/GodEater) 12.23.44 NJoin crashd [0] (i=foobar@lostnode.org) 12.26.23 Join mf0102 [0] (n=michi@85-127-39-81.dynamic.xdsl-line.inode.at) 12.32.21 Quit XavierGr (Read error: 104 (Connection reset by peer)) 12.33.00 Join at0m|c [0] (n=at0m@78-20-136-118.access.telenet.be) 12.34.56 # does it make any sense to compile gcc 4.x for m68k targets? 12.38.26 Join DerDome [0] (n=DerDome@141.71.76.39) 12.41.23 # gevaerts: hi. can you take a look at patch, that tries to solve ep problem ftp://localhost/vitja/xx.diff? 12.42.25 Join GodEater [0] (i=c2cbc962@gateway/web/ajax/mibbit.com/x-2ee2936ad5de20ad) 12.43.05 Join linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 12.43.06 Quit Lambdumb (Read error: 104 (Connection reset by peer)) 12.43.26 Join Lambdumb [0] (n=Lambda@12-203-112-233.client.mchsi.com) 12.43.30 # do you mean ftp://79.120.98.174/vitja/xx.diff ? :) 12.44.05 # yeah, sorry 12.44.49 # $ echo 79.120.98.174 localhost >> /etc/hosts 12.45.44 # hmm I just tested link with lftp and copy-pasted path 12.55.02 Join tvelocity [0] (n=tony@195.167.65.108) 12.59.31 # vitja: I've got the file. I'll have a look later today (promise!) 13.01.30 # where are the interrupts handled in rockbox code ? 13.06.04 Quit vitja (Read error: 54 (Connection reset by peer)) 13.06.53 Join vitja [0] (n=vitja@wn1nat26.beelinegprs.ru) 13.09.23 Quit gromit` (Read error: 104 (Connection reset by peer)) 13.09.58 Quit tvelocity (Remote closed the connection) 13.12.39 Join gromit` [0] (n=gromit@ALagny-154-1-84-124.w81-48.abo.wanadoo.fr) 13.13.26 Join kugel [0] (n=chatzill@unaffiliated/kugel) 13.17.11 Join vitja_ [0] (n=vitja@79.120.98.174) 13.20.29 # gevaerts: are you here? 13.25.40 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 13.25.53 Quit mf0102 ("Ex-Chat") 13.26.42 Quit vitja (Read error: 104 (Connection reset by peer)) 13.26.44 *** Saving seen data "./dancer.seen" 13.29.21 Quit avis (Read error: 104 (Connection reset by peer)) 13.29.57 Join avis [0] (n=ident@pdpc/supporter/student/avis) 13.30.24 Quit avis (Read error: 104 (Connection reset by peer)) 13.30.28 Join MarcGuay [0] (n=chatzill@ip216-239-88-51.vif.net) 13.41.33 # vitja_: yes 13.41.44 # gevaerts: have you seen patch? 13.42.07 # vitja: I've got the file. I'll have a look later today 13.42.57 # vitja_: beware, the promise he made when you were offline is now gone ! 13.43.08 # ok 13.43.37 # funman: bertrik told me to tell you about sg3-utils 13.44.03 # thanks, I'm looking what it is about 13.44.25 Join Schmogel [0] (n=Miranda@p3EE21737.dip0.t-ipconnect.de) 13.44.26 # tools for working with generic scsi devices 13.45.33 # yes. You may be able to use them to send data to a scsi/usb block device even if it reports wrong numbers of blocks 13.45.50 # oh, that's for my bricked clip then 13.49.02 Quit n1s () 13.49.50 Join J-23 [0] (n=aldwulf@a105.net128.okay.pl) 13.53.21 Quit Bawitdaba (Read error: 110 (Connection timed out)) 14.01.21 Quit vitja_ ("Ex-Chat") 14.03.22 Join einhirn [0] (n=Miranda@w1634.wlan.rz.tu-bs.de) 14.06.19 # funman: bricked clip???? 14.06.27 # thought you have a new one 14.06.33 # or do you have both? 14.06.58 # I only replaced the 2nd one i bricked 14.07.11 # ah ok 14.07.11 # the first one is opened, battery removed, and I just copied a firmware to it with sg_dd 14.07.21 # now let's plug back the lcd and pray ! 14.08.36 # you didn't pray hard enough :/ 14.08.49 # sorry :( 14.13.24 # anyone with a gigabeat s online? 14.15.11 # J-23: what do you mean with 'direct access' ? 14.19.25 # s/*/access the on-board ROM via USB/ 14.19.31 # no 14.19.49 # we can only write to it when doing a firmware upgrade 14.20.33 # how does recovery mode work on v2's? 14.21.19 # on e200 you can access (read/write) the whole firmware file by usb if you disable manually the NAND (shorting 2 pins together) 14.21.56 # on other models, we implement recovery in the very first stages of the software we execute (resume OF is a button is pressed or usb connection is detected) 14.23.10 # I'm now trying some scsi generic tools as suggested by bertrik but with limited hope 14.23.16 Join tvelocity [0] (n=tony@195.167.65.108) 14.23.40 # interestingly, I hadn't noticed that my clip is detected as 2 usb mass storage devices (0 blocks each) 14.26.54 # funman: afair my previous fuze was deteced as 2 devices, 1 of which was 0 block 14.27.11 # when I shorted the nand that is 14.27.14 # the 2nd device's block size is not listed in dmesg 14.30.18 Quit einhirn (Read error: 104 (Connection reset by peer)) 14.30.40 # funman: do you know how far atomic came with his sd investiigation? 14.30.49 # which one? 14.30.53 # sd interface 14.30.59 # to access the nand 14.31.00 # disassembly 14.31.02 Part LinusN 14.31.31 Join Seed [0] (n=ben@bzq-84-108-232-45.cablep.bezeqint.net) 14.35.05 # kugel: do you run windows ? 14.36.34 # funman: How do you mean? 14.36.39 # I run it on my pc 14.37.13 # that's what I asked - could you try shorting the nand pins and running the official sansa firmware updater ? 14.37.33 # I don't remember if I used it on my clip when it was bricked - and now I deleted the virtual machine I used 14.37.33 # uh 14.37.53 # amiconn: Do you know how Interix compares in speed to Linux in a vm? 14.38.21 # the fuze has a very sensible connection between the wheel and the board. It's likely I break it again when I open my fuze 14.38.35 # kugel: ah right I remember you broke it - then forget about it :) 14.38.49 # I have a new one 14.38.55 # fully working 14.40.22 # still, I don't really want to open it again. And I'm really doubtful that the updater can see it (and do something useful with it?) 14.40.29 # s/?// 14.41.27 # I'll ask atomicpunk 14.41.38 # I also doubt that it does anything 14.43.06 Part B4gder 14.48.12 # most of the scsi commands I try fail, but I can make the device hang, so it has some effect at least ;) 14.48.41 Join kushal_12_27_200 [0] (n=kushal@12.169.180.178) 14.52.29 # Llorean: ping 14.57.53 Quit kushal_12_27_200 ("Leaving") 15.06.34 Quit freqmod_qu (Read error: 113 (No route to host)) 15.06.42 Join LambdaCalculus37 [0] (i=44a04303@gateway/web/ajax/mibbit.com/x-e037c8671fde8ea6) 15.07.46 # linuxstb: the problem with vm in a multicore system is that it doesn't use all the available cores, so if interix is 2x-5x faster than cygwin it should be faster than linux in a vm 15.10.30 Join Wictor_ [0] (n=Wictor@0x57366a52.bynxx19.dynamic.dsl.tele.dk) 15.10.43 # kugel: only the first device seems to be really a mass storage (sg_readcap fails on the 2nd) 15.11.22 # well the 2nd device reports that it's not ready 15.11.45 # XavierGr: I'm on single core though (and VMware can use 2 cores in one VM if you tell it to) 15.13.03 # amiconn: that was my problem, I have a 4 core cpu and I couldn't make vmware to use them all 15.13.26 # amiconn: so can someone use interix to compile rockbox now? 15.13.36 # what about separate networked VMs and distcc ? 15.13.57 Quit tvelocity (Read error: 110 (Connection timed out)) 15.15.05 Quit Wictor (Read error: 60 (Operation timed out)) 15.15.05 # amiconn: also did you get interix downloading the entire SFU that microsoft provides or did you find it separately 15.22.05 Join meven [0] (n=meven@lav35-1-82-236-137-162.fbx.proxad.net) 15.25.11 # nothing meaningful with sg_utils 15.25.38 # LambdaCalculus37: hey! :) 15.26.06 # kugel: Good morning (or afternoon)! :) 15.26.37 # afternoon, rather 15.26.45 # What's the good word on your Gigabeast backlight fading? 15.26.48 *** Saving seen data "./dancer.seen" 15.28.21 # funman: does sg_dd check the device capacity before writing? If so, you could try changing it to really only do the writes 15.28.35 # it doesn't 15.28.47 # * funman hopes 15.29.29 # LambdaCalculus37: well, I've done a bit. It could work now 15.29.37 # a linux bug(?) makes it report device's blocks number as 1 minimum even if the device said 0, and the 1st block isn't even copied 15.30.02 # kugel: Want to post it to Flyspray? It'll get more exposure that way. 15.30.19 # Plus, I can't do anything from work. :( 15.30.40 # oh 15.31.05 # what can you do if I build for you? 15.31.43 Quit iSuck (Client Quit) 15.32.09 Join Darksair [0] (n=user@221.221.144.56) 15.32.24 Join Bawitdaba [0] (n=Sphinx@cpe-72-224-114-36.nycap.res.rr.com) 15.32.48 # kugel: Won't be able to do much right now. 15.33.07 # kugel: Post the patch on FS, and I'll go and get it when I can get a little free time. 15.34.01 # so, you can't extract a zip on your player and take 2 min to see if backlight is working? sad 15.34.08 # funman: are you using /dev/sdX or /dev/sgX? I think sg_dd still goes through the kernel for /dev/sdX 15.34.33 # sg 15.35.04 # and I explicit the device file 15.35.11 # kugel: Tell you what.. make the build and email me the zip. 15.35.31 # some (very little) information is correctly reported, load/start commands are successful, the device is ready 15.35.40 # LambdaCalculus37: how about uploading to my webspace? 15.35.45 # but I can't read/copy anything 15.36.00 # I think sandisk somehow disabled that feature 15.36.01 # kugel: Okay. 15.36.06 Join jgarvey [0] (n=jgarvey@cpe-098-026-069-229.nc.res.rr.com) 15.38.49 # hum the sansaV2 OF enables the "timer2 clock" 15.39.01 # LambdaCalculus37: http://www.alice-dsl.net/simonemartitz/forlambda/rockbox.zip 15.39.13 # and now that I read the code handling interrupts, it seems that we have to handle interrupts for said 'timer2' 15.39.45 # in order to? 15.40.01 # so maybe the interrupts are handled by the OF, and since it's in an uninitialized state, the interrupt handler may return without actually handling it 15.40.02 Quit Dementio (Read error: 104 (Connection reset by peer)) 15.40.07 # kugel: no idea 15.40.57 # XavierGr: The full thing, plus a few hotfixes, plus another big package from suacommunity.com 15.40.57 Join fragilematter [0] (n=barbu_do@92.83.226.58) 15.41.22 # And no, it is not yet possible to use Interix for building rockbox, but I'm working on it 15.43.03 # kugel: firmware/target/arm/system-pp502x.c line 47/48 15.43.21 # XavierGr: why not use VirtualBox? I think it uses all CPUs... 15.44.13 # TIMER2_VAL; /* ACK interrupt */ 15.44.26 # does it mean to acknowledge the interrupt, one just has to read said register ? 15.45.56 # kugel: Still independent of the brightness setting. I can't do much else right now because my beast needs a charging... again. 15.45.58 # petur: it didn't when I used it (v1.6) 15.46.08 # oh? 15.46.27 # well the manual says nothing about it... 15.46.29 # LambdaCalculus37: does it still go to max brightness on fading down? 15.46.54 # petur: unfortunately cygwin in the end is less hassle than any virtual machine 15.47.02 # petur: the vm didn't even see the second core, so... 15.47.05 # kugel: I didn't notice because my beast shut off while I was testing. 15.47.15 # :( 15.47.20 # * petur gets the latest version and tries 15.48.14 # and if a virtual machine doesn't use all the cores I could just use cygwin and loose a little speed 15.48.35 # funman: This is correct for PP. Other SoCs probably most behave differently, mabye very differently 15.48.54 # I remember cygwin at 4 cores vs vmware at 2 cores was significant due to ccache but in the end I opted for cygwin once again 15.49.10 # XavierGr: A little? Building the crosscompilers on Interix was 2times...7times (!) faster than on cygwin... 15.49.17 # (and I am not compiling all the time so waiting 30 seconds more is not the end of the world) 15.49.29 # amiconnn: I am talking about cygwin vs vmware 15.49.53 # I haven't tryid interix yet, it sounds promising and I wait impatiently for your work :P 15.50.01 # amiconn: yes, for as3525 it seems we have to write in a specific register 15.50.09 # Yes, and I think Interix and VMware+linux will be about the same speed on the same hardware 15.50.53 # from a hardware point of view, I understand that I would just have to clear the interrupt. 15.51.21 # hm I'll read the datasheet in details before making assumptions :) 15.52.50 # kugel: The other reason why I wanted you to post the patch on Flyspray is so I can take a look at it as well. 15.53.24 Part J-23 15.53.26 # I really didn't change much 15.53.52 # * kugel doesn't want to upload a known-to-not-work patch :S 15.53.58 # kugel: VirtualBox shows the guest only one CPU but schedules its execution across all CPU's (so says http://forums.virtualbox.org/viewtopic.php?t=2435 ) 15.54.28 # jugel: erm, use all cores for its I/O tasks 15.54.33 # *kugel 15.54.45 # petur: I used make -j, and never got above 50% cpu usage in the host (XP) 15.55.06 # only for IO 15.55.42 # kugel: Just tell people that it's still rather kludgey. 15.55.52 # Besides, someone with a beast can help work on it. 15.56.32 Join J-23 [0] (i=aldwulf@a187.net131.okay.pl) 15.56.37 # ah no, reading further shows that it should use all cores 15.58.28 Join Dementio [0] (n=dementio@211.45.234.45) 15.58.35 # No virtualiser can magically combine cores 15.59.44 # So if the guest sees only one core, it effectively uses only one core. It can use further cores for asynchronous tasks like I/O though 16.00.49 # LambdaCalculus37: okokok 16.03.03 Join webguest16 [0] (n=ca6c12a3@gateway/web/cgi-irc/labb.contactor.se/x-41c1aca1384ca640) 16.05.19 Quit webguest16 (Client Quit) 16.06.58 Nick fxb__ is now known as fxb (n=felixbru@h1252615.stratoserver.net) 16.09.04 # LambdaCalculus37: did 16.09.39 # kugel: I'll take a look through the patch and see if maybe I can zero in on the problem. 16.11.18 # LambdaCalculus37: I don't understand why it's still ignoring the backlight setting. backlight_brightness initialized with the default brightness, but always modified within _backlight_set_brightness (which is supposed to be called when you change the setting) 16.13.16 # apart from that, beast should be able to use real pwn fading 16.19.37 # beast bl fading? I tried to use that but the HW fading really kind of well, sucks. it doesn't reverse the cycle in the middle of a fade. 16.20.28 # jhMikeS: Hey there! Want to take a look at FS#6800? 16.20.30 # I could have done something wrong of course but I wasn't too encouraged. 16.20.44 # #6800? That's sounds rather ancient. 16.21.08 # kugel was working on a newer version of it, and I also made a version of the patch synced to recent SVN. 16.22.10 # jhMikeS: ancient yes, due to rotting 16.22.22 # it's a nice patch 16.23.26 # jhMikeS: you might want to take a look at the latest version I just uploaded some minutes ago 16.23.42 # to start with we can disable the HW fade though 16.24.25 # can we? is "fading in software" preferable over hw fading? 16.24.46 Quit orly_owl (Connection reset by peer) 16.24.46 # not if the HW fading could actually be made to work how we need it to of course 16.25.35 # well, it seems that fading up works, but fading down not 16.25.57 # in hardware 16.26.24 # that's where the problem was. the datasheet tells how to do it. like I said, the ramp doesn't seem to be interruptable. 16.26.51 # jhMikeS: Is the datasheet up in the wiki? 16.27.02 # so, software fade is preferable over a mix of both? 16.27.04 # no, it's NDA crap 16.27.23 # Crap. :( 16.27.44 # does anyone here use his ipod throuhg a dockstation? it doesn't work 16.28.06 # kugel: As long as it doesn't hamper performance, I suppose. 16.28.06 # of course we just got handed a copy from freescale without signing anything. I think they just don't want it on the web. 16.28.26 # * LambdaCalculus37 puts on his pirate hat and eye patch 16.28.36 Join Peter15 [0] (n=peter151@dslb-084-058-175-208.pools.arcor-ip.net) 16.29.46 # kugel: well, if you can poke at it to get HW to work, my view is that is better 16.30.38 # jhMikeS, LambdaCalculus37: the patch at fs#6800 is performing well. it uses the backlight thread and can be interrupted while fading 16.31.21 # I don't think I get the hardware to work. I haven't messed with beast at all, as I don't own it 16.31.40 # * jhMikeS just wants to think about committing the charging code and then doing and powermgmt reworking 16.32.56 # doesn't SW fading cause little flashes of extra brightness betwee steps? 16.32.56 # jhMikeS: I heard the beast cannot really charge on a usb connection because of the disk spinning all the time. can this be fixed (I doubt it's intended) 16.33.14 # jhMikeS: not this one 16.33.26 # kugel: I should be fixable if the disk will spin down while connected 16.34.09 # kugel: Getting all those levels was sort of a hack. I think it is only happens when ramping brigtness up. 16.34.31 # feel free to try the patch. I've added basic (not really working) support for gigabeat s, but it works just fine on c200&e200 16.35.02 # kugel: okiedokie. how many levels hath the e200? 16.35.28 # 12, I'm using 5 though and it still looks great 16.37.53 # * jhMikeS 's e200 is being charged for now 16.38.17 # in fact timer2 isn't used by the hardware, it is used by the software for its own timing management 16.40.21 # jhMikeS: you can safely disconnect your sansa in the middle of charging :) 16.41.25 Join bmbl [0] (n=Miranda@unaffiliated/bmbl) 16.42.49 Quit pixelma2 (Nick collision from services.) 16.42.59 Join pixelma2_ [0] (n=marianne@rockbox/staff/pixelma) 16.43.16 Quit amiconn (Nick collision from services.) 16.43.23 Join amiconn [50] (n=jens@rockbox/developer/amiconn) 16.44.19 Join DrMoos [0] (i=moos@81-66-128-18.rev.numericable.fr) 16.44.21 Quit moos (Read error: 104 (Connection reset by peer)) 16.44.35 Nick DrMoos is now known as moos (i=moos@81-66-128-18.rev.numericable.fr) 16.45.23 # jhMikeS: do you have an idea how to disable the hardware fading up? 16.47.40 Join webguest07 [0] (n=c652409f@gateway/web/cgi-irc/labb.contactor.se/x-3060388d2b77f978) 16.48.38 Quit webguest07 (Client Quit) 16.48.57 # jhMikeS: The SW fading did cause the brightness on my Gigbeast LCD to max out before fading down. 16.49.05 Join toffe82 [0] (n=chatzill@h-74-0-180-178.snvacaid.covad.net) 16.49.40 # LambdaCalculus37: that was the version as of yesterday though, wasn't it? 16.50.30 # kugel: Yes. Like I said, my battery ran out before I could try the new version. 16.51.45 # sounded like it's still preset 16.51.49 # present* 16.54.57 # * funman notices he forgot to enable a clock in its sd code 16.55.17 # * funman is filled by a sudden hope 16.58.34 Join Administrator [0] (n=chatzill@cpe-90793.ip.primehome.com) 16.58.43 Nick Administrator is now known as netmis (n=chatzill@cpe-90793.ip.primehome.com) 16.58.50 # hello 16.59.05 # i saw that onda players are wip 16.59.16 # what is the current status? 16.59.37 # is rockchip going to be supported? 16.59.41 Quit Seed (Read error: 113 (No route to host)) 16.59.46 # 2706 am interested in 17.00.24 Nick netmis is now known as temis (n=chatzill@cpe-90793.ip.primehome.com) 17.00.34 Nick temis is now known as ntemis (n=chatzill@cpe-90793.ip.primehome.com) 17.00.35 Quit BlakeJohnson86 ("Leaving.") 17.00.45 Join BlakeJohnson86 [0] (n=bjohnson@c-24-118-162-123.hsd1.mn.comcast.net) 17.00.51 Join bughunter2 [0] (n=Jelle@77.164.66.126) 17.01.06 # anyone? 17.03.38 # Onda VX747 17.03.52 # ntemis: http://www.rockbox.org/twiki/bin/view/Main/OndaVX747 17.03.59 # what are i saw it 17.04.04 # i saw it 17.04.10 # not ready yet 17.04.13 # :) 17.04.37 # what are the advantages of using this firmware instead of the original one? 17.04.49 # http://www.rockbox.org/twiki/bin/view/Main/WhyRockbox 17.05.27 # every question has its wiki answer :) 17.06.46 # funman: What encryption is used on the newer ipods, and what are the keys? 17.07.23 # what about rockchip? 17.07.27 # linuxstb: 42 17.07.31 # i have a lot of these 17.07.43 # can anything done on them? 17.08.01 # rockchip 2706 17.08.02 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-e947fd3c54a34b19) 17.09.04 # ntemis: it seems nobody did write the support for it 17.09.30 # i have onda 17.09.38 # when ready i will test out 17.10.07 # but is good to see a port for rockchip because i have a lot and onda only one 17.10.08 # you can check/subscribe to the forum thread to know the progress 17.10.46 # for rockchip the only thing you can do is write it yourself 17.10.52 # can i have subtitles with *.srt being payed automaticaly? 17.11.04 # can subs be supported? 17.11.14 # srt am interested in 17.11.26 # on onda 17.11.43 # that would be great addon 17.11.44 # ntemis: this would be intertesting 17.11.51 # stop using enter as punctuation 17.11.52 # and really convenient 17.11.59 # yeap 17.12.02 # funman: any hope I can run some more code on my fuze? 17.12.03 # much! 17.12.49 # kugel: yes, write some ! 17.12.59 Join makicar [0] (n=maki1908@89-201-144-244.dsl.optinet.hr) 17.13.08 # and also codepage 1253 will be needed 17.13.22 # for subttiles to show ok on me 17.13.31 # or else will see chinese 17.13.31 # kugel: or did you mean how to higher the size limit ? 17.13.37 # yep 17.13.58 # like I told you, we need to test on e200 first 17.14.13 # any srt support on avis? 17.14.22 # Hillshum has a e200 afaik, and he's probably willing to test 17.15.28 # funman: does the e200v2 not have this small size limit? the features of fuze and e200v2 are about the same 17.16.15 # ntemis: Rockbox doesn't play AVI files. Only MPEG 1/2 videos. 17.16.26 # it plays 17.16.35 # flawlessly 17.16.35 # kugel: the limit is on the file format currently, but we can try what we want on e200 and still be able to recover it 17.17.02 # rockchip 2706 17.17.08 # kugel: i got a fuze finally 17.17.11 # how hard is it to open 17.17.14 # funman: Have you thought about using something like UCL to compress the OF? 17.17.24 Join webguest85 [0] (n=479013c8@gateway/web/cgi-irc/labb.contactor.se/x-88aeff8b26926da1) 17.17.55 # saratoga: quite hard. Use a knife 17.17.57 # kugel: one moment on the disable stuff 17.18.35 # saratoga: just pay extra intention on the connection cable of the scrollwheel. it turned out to be extra sensible 17.18.44 # attention* 17.19.24 # * linuxstb tests how much UCL would compress the Clip's OF... 17.19.38 # kugel: remove the MC13783_LEDMDRAMPUP/DOWN bits and that does it iirc 17.20.00 # ...in _backlight_init() 17.20.17 # ok, will do. 17.21.37 # funman: UCL compresses the 119336 byte Clip firmware (v1.1.17a) to 77964 bytes, so would give us a fair amount of space for a bootloader... 17.22.10 # funman: That's if I understand the process correctly - that you can copy the firmware from ROM to RAM, and then run it... 17.24.51 # LambdaCalculus37: can you remember how it faded down exactly? 17.25.31 # LambdaCalculus37: was it a) fading down to nearly-off, then max brightness shortly, then really off or b) max brightness, then fading down to off 17.26.44 # kugel: It was b). 17.26.50 *** Saving seen data "./dancer.seen" 17.26.53 # ok 17.27.19 # tell me when you're ready for a new test build 17.29.32 # kugel: In about 20 minutes, upload a new build and give me the signal when it's up. 17.29.51 # I want to make sure the battery's got enough charge. 17.29.53 # I'm trying to make the settings menu more user-friendly by moving things around. Here is a preliminary patch: http://pastebin.ca/1214352 17.31.00 # so far, some concerns have been raised: the patch makes it easy for regular users, while making it more difficult/complicated for advanced users to change sound settings 17.32.08 # the reason is that I'm hiding seldom-used settings under a new submenu "Advanced Sound Settings", advanced users who want to modify advanced settings would have to make a few more clicks than they have to with the current state. 17.32.58 # Does anyone have any idea how to make the menu simpler for regular users to use (to not scare them away), but not more complicated for advanced users? 17.37.09 # what's the benifit of putting stuff simply into a submenu? 17.37.22 Quit webguest85 ("CGI:IRC (EOF)") 17.38.04 # I'm all for some rearrangement, but that's not what I would call beneficial 17.39.02 # kugel: the benefit is that the Sound Settings menu would become less cluttered. 17.39.19 # Although I see that devs don't like it... 17.39.29 # if it's too complicated for the users, they'll ignore it. What makes you think they're scared and what's the result of the scare 17.40.01 # I'm not a dev and I don't like it very much either 17.40.43 # it's basically just hiding some options for some people and making ways longer for the other people 17.41.05 # I think it scares users away because it's too complicated -- the menu is full of options that people seldom use 17.41.14 # and new users tend to click on advanced at least once anyway, which kills the "they're scared" argument 17.43.48 # kugel: How many people have probably clicked on "Debug (Keep Out!)" as well? 17.44.15 # kugel: yes, but they will realize that "ah, this is not the place for me" and will never go there again 17.44.16 # masses 17.44.32 # especially since the "keep out" only appears in english.lang 17.45.14 # wpyh: so you actually intend to keep users away from the settings which make rockbox to what it is? 17.45.37 Quit austriancoder ("Lost terminal") 17.45.38 # LambdaCalculus37: updated the build, link is the same 17.45.43 # kugel: No, the "keep out" is in a few of the other languages... I know it's in Tagalog. 17.45.56 # kugel: Okay, going to download now. 17.46.51 # LambdaCalculus37: oh, how could I forget about tagalog! :S 17.47.07 # yeah 17.47.28 # anyway, I correct my self to "not appearing in most languages" 17.47.47 # linuxstb: indeed sounds like a very good idea 17.47.54 # kugel: I would not view those settings as "which make rockbox what it is", but yes, I intend to hide regular users from the more advanced settings 17.48.23 # funman: Does the OF copy itself from ROM to RAM? 17.48.36 # I think we should work out some solution that does not make it difficult for advanced users... 17.48.48 # I don't really know but I can search a copy routine 17.48.51 # wpyh: But it's also a matter of knowing exactly what's a "more advanced setting" to average users. Some people may enjoy the more complicated settings. 17.49.04 # well, I mainly use rockbox because of it's advanced audio features and costumizability of audio experience (and UI ofc). Also, that's what it's designed fo 17.49.49 # * kugel adds adds a r 17.49.52 # wpyh: I think the best way to do this is to post a patch to Flyspray, and (if you're up to it) maybe offering a unofficial build on the forum that has the patch applied. 17.50.04 # funman: Because if it does, I think we may need patch the firmware remove that feature... 17.50.04 # Then people can try it and give you feedback on what they do and don't like. 17.50.18 # yes, and for those people, they can always open the advanced settings menu. of course, another option would be to put the basic settings on top and the advanced settings belw 17.50.20 # *below 17.50.34 # linuxstb: can you rephrase ? 17.50.48 # LambdaCalculus37: it was said earlier today that this kind of patch should not go into flyspray... 17.51.08 # funman: If there is a copy loop, I think we will need to patch the OF to remove that copy 17.51.32 # why that ? what if we want to boot the OF ? 17.51.58 # oh I understand 17.52.01 # funman: The bootloader uncompresses the OF into RAM 17.52.02 # wpyh: I agree that it should. 17.52.07 Join mf0102 [0] (n=michi@85-127-39-81.dynamic.xdsl-line.inode.at) 17.52.33 # LambdaCalculus37: how about offering an alternative repository with unofficial patches? 17.52.37 # wpyh: What is it else? A patch that goes directly into svn? 17.53.01 # wpyh: Where do you think most of the unofficial patches are? ;0 17.53.10 # s/;0/;) 17.53.46 # LambdaCalculus37: flyspray :p but it's been said that flyspray is not meant for such code... 17.53.57 # kugel: I don't quite understand your last sentence... 17.54.02 Join DrMoos [0] (i=moos@81-66-128-18.rev.numericable.fr) 17.54.25 # you said it's not suitable for flyspray 17.55.05 # ah 17.55.17 # you don't want to put it there, but you want it in svn. that makes no sense 17.55.26 Quit moos (Read error: 104 (Connection reset by peer)) 17.55.28 Nick DrMoos is now known as moos (i=moos@81-66-128-18.rev.numericable.fr) 17.55.44 # LambdaCalculus37: updates on backlight fade please :) 17.55.57 # quote from #rockbox-community: (12:00:30) Llorean: wpyh: If you're doing work you don't intend to be committed into SVN, it shouldn't be on flyspray. 17.56.11 # kugel: Oh, right! :P 17.56.25 # * LambdaCalculus37 gets his Gigabeast off the charger 17.56.25 Join bill2or3 [0] (i=bill@cloudburst.xmission.com) 17.56.38 # because this patch won't ever make it to svn, I should not be putting it on flyspray 17.57.05 # well, I'd just drop the idea if I wouldn't see a chance to get it into svn 17.57.47 # kugel: I did that before, but it's getting uneasy. I would like to adapt my idea so devs (and advanced users) aren't put off by it. 17.57.52 # and I wouldn't even work on patches I don't want to have in svn (where the sense in that anyway?) 17.58.38 # and another quote: (11:58:08) Llorean: scorche: That patch isn't suited for Rockbox anyway. It's more or less the beginning of doing exactly what I said he shouldn't have it do (hiding things in "Advanced" menus) 17.59.19 Join setkeh [0] (n=setkeh@CPE-124-181-6-74.vic.bigpond.net.au) 17.59.20 # kugel: I actually want it to be in svn, but it seems that the patch is not good enough... which is why I'm thinking of how to improve it to make it good enough to go into svn. 17.59.48 # I've narrowed down my non-booting H340 problem. It'll boot Rockbox if I'm in the bootloader-USB-mode and pull the usb cable out, but wont boot Rockbox directly from power-up, giving a "ATA Error: -1" message. Does anyone have any ideas on how those two boots may differ, in the bootloader code? 18.00.15 # kugel: Ready? 18.00.54 Join perrikwp [0] (i=d1a8d351@gateway/web/ajax/mibbit.com/x-101e8502510effb9) 18.01.06 # kugel: Backlight brightness is still not matching to the setting I have it at. The backlight fades, but it raises the backlight to max brightness just before fading out. 18.01.16 Quit petur ("gonne") 18.01.47 # grr 18.01.48 # If I try turning the backlight on with a button press, it comes back on, but very dim. If I touch any button when the backlight raises to max brightness, the backlight gets "stuck" at that brightness. 18.02.21 # does setting the backlight in the settings do anything now at least? 18.02.51 # LambdaCalculus37: ahh wait 18.02.55 # kugel: Nope. Still nothing. 18.03.01 # Seems I haven't uploaded the build! 18.04.37 # LambdaCalculus37: now, redownload please :S 18.05.02 # * kugel didn't press the red button to overwrite 18.07.57 # * LambdaCalculus37 had to go into the logs to get the link again 18.09.19 # kugel: Updating now. 18.10.16 Quit setkeh ("Leaving") 18.10.42 # linuxstb: no I can't find a copy routine in the OF 18.11.03 Quit perrikwp ("http://www.mibbit.com ajax IRC Client") 18.11.15 # in fact it seems to assume it's already in RAM (after changing the coprocessor register cp15) 18.11.56 # while during my tests, I couldn't write to the memory below 128kB, unless I had remapped the RAM at offset 0 (which is done by a special register, unused in the OF) 18.12.55 # weirdly, in my first test, I remapped the RAM at offset 0 but didn't copy the full OF first, which led me think that the AS3525 already had copied the ROM content into RAM 18.13.11 # kugel: Now the backlight fades, but if I let it fade entirely, no amount of button pressing makes it snap back on. 18.13.22 # If I catch it in the middle of fading, it raises to max brightness. 18.13.28 # but now looking at the code I think when it boots it's already in RAM and I did a wrong test back then 18.13.37 # I'll check exactly what it changes in cp15 18.13.53 # LambdaCalculus37: so it goes back on after fading? 18.14.14 # funman: So maybe there is a first-level bootloader that copies the contents of the ROM to RAM? 18.14.18 # kugel: No, it doesn't. 18.14.25 # * linuxstb checks the datasheet 18.14.33 # ah you mean you can't turn it on anymore? 18.14.34 # It's almost like the LCD turns off entirely. 18.14.55 # kugel: Right! 18.15.40 # ok, I think what's causing it 18.15.52 # but you can get it on by restarting? 18.16.16 # if possible, do a quick check if the backlight setting is working now 18.16.34 # kugel: The backlight setting still doesn't do anything. 18.16.52 # * kugel can't explain that 18.17.23 # does it still go to max brightness before fading down? 18.17.45 # funman: Have you tested (for example), writing to a PC-relative address in the bootloader code, and then reading the value back? This would tell us if we're running from ROM or RAM. 18.18.10 # kugel: Still does, and I can still press a button and "catch" that setting. 18.21.55 Join MethoS- [0] (n=clemens@host-091-097-241-015.ewe-ip-backbone.de) 18.24.36 Join bertrik [0] (n=bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 18.26.17 Join perrikwp [0] (i=9821361e@gateway/web/ajax/mibbit.com/x-85809d4e73479fa2) 18.26.59 # jhMikeS: can you explain why LCD_ENABLE is defined for beast, but not actually used? 18.27.26 Quit J-23 () 18.27.29 Quit Bawitdaba (Read error: 110 (Connection timed out)) 18.27.30 # HAVE_LCD_ENABLE rather 18.27.51 # funman: So you don't think the OF writes to CCU_MEMMAP ? 18.28.01 # LambdaCalculus37: next version up in a minute 18.28.01 # linuxstb: I tested an absolute value back then 18.28.18 # I see no cross reference in IDA, I looked for all the CCU registers 18.29.06 # because sometimes it loads a register, and sub/add a few offsets from it 18.30.14 # after modifying cp15, the OF clears memory, descending from SP to the end of firmware block (hence, below 128kB) 18.30.31 # gtg, I'll be back later this evening 18.30.45 # you can highlight me if needed 18.30.57 # LambdaCalculus37: I now used almost exactly the same code as in e200 18.31.18 # funman: OK, so you think it's likely that RAM has already been remapped to 0x0 when the OF is started? 18.31.30 # If so, then I think this UCL trick will work... 18.31.47 Join BigBambi [0] (n=Alex@rockbox/staff/BigBambi) 18.34.36 Join mcuelenaere [0] (n=mcuelena@rockbox/developer/mcuelenaere) 18.35.05 # LambdaCalculus37: are you already installing? :P 18.37.05 Join perplexity [0] (i=heh5739@dxb-as80576.alshamil.net.ae) 18.38.02 Join nplus_ [0] (n=nplus@141.25.globcom.net) 18.38.46 # kugel: Eating lunch. Two minutes and I'll install. 18.38.52 # nice 18.39.37 Join Seed [0] (n=ben@bzq-84-108-232-45.cablep.bezeqint.net) 18.40.05 # linuxstb: if there's anything to test on a v2 device let me know 18.40.19 # kugel: You _really_ don't want to test this idea... 18.40.33 Quit DerDome ("Leaving.") 18.41.31 Quit nplus (Read error: 110 (Connection timed out)) 18.42.39 # kugel: Cross your fingers. :) 18.42.41 # hm 18.42.48 # will do 18.43.07 # * LambdaCalculus37 updates 18.45.34 # my fingers begin to hurt 18.45.53 # You can relax your fingers. :) 18.46.52 # The backlight brightness setting works now, *but*!... the backlight still doesn't come back on after it fades out. 18.47.05 # duh 18.47.11 # the setting at least works 18.47.16 Join ompaul [0] (n=ompaul@gnewsense/friend/ompaul) 18.47.22 # and I guess it 18.47.36 # But now you have to figure out how to get the backlight to snap back on after it fades out. 18.47.37 # 's still going for max brightness before fading down 18.48.09 # kugel: Actually, it's not going for max brightness anymore. It's using the setting it's at. 18.48.32 # Also, the fadeout is kind of clunky looking. 18.48.51 # clunky looking? explain please 18.49.21 # as in, not fluently? 18.49.49 # kugel: It's not fluid, if that's what you're asking. 18.49.53 Join Hillshum_ [0] (n=Hillshum@75-165-239-6.slkc.qwest.net) 18.49.53 # if yes, that's possibly caused by the pwn table 18.50.42 # kugel: I've gotta run for a little bit, so I'll check the logs. 18.50.45 # * kugel sets this assumption to true and focuses on the remaining bug 18.50.55 # oh noes! 18.50.58 Join funman_ [0] (n=fun@AAnnecy-257-1-67-132.w90-36.abo.wanadoo.fr) 18.51.04 Join setkeh [0] (n=setkeh@CPE-124-181-6-74.vic.bigpond.net.au) 18.51.17 Quit funman ("leaving") 18.51.32 Nick funman_ is now known as funman (n=fun@AAnnecy-257-1-67-132.w90-36.abo.wanadoo.fr) 18.51.43 # kugul: test? 18.51.48 # kugel 18.53.13 # Hillshum_: I told funman that you're possibly available to test some e200v2 code 18.53.18 Join Nico_P [50] (n=nicolas@rockbox/developer/NicoP) 18.53.28 # does he have a patch? 18.53.29 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 18.53.36 Join culture [0] (n=none@cpc1-bele3-0-0-cust658.belf.cable.ntl.com) 18.53.41 # no, no patch 18.56.27 # funman, you did some sg3-utils experiments already? 18.57.19 # I noticed in the forum thread that the id of the clip recovery device could not be read, but it could read the capacity 18.57.30 # * Hillshum_ just got a 500 internal server error when submitting a wiki edit 18.57.52 # bertrik: yes but nothing interesting, the device fails to answer to most queries 18.58.07 # what about a scsi inquiry? 18.58.25 # in fact it reports 0 blocks, but Linux doesn't handle such devices and report 1 block (of 512 bytes) 18.59.28 # it would at least be interesting to find out which scsi commands are supported and which ones are not (and which sense data they return for those commands if any) 19.00.03 # the idea is to bypass the linux block device layer, so how linux interprets things is mostly irrelevant 19.00.58 Quit setkeh (Remote closed the connection) 19.02.49 Join domonoky [0] (n=Domonoky@rockbox/developer/domonoky) 19.03.16 # http://paste.ubuntu.com/52524/ 19.04.30 # http://paste.ubuntu.com/52525/ < weird dynamic answers 19.05.37 # hmm, can you do a hex dump of the raw data? 19.06.13 # add -H to the sg_inq command IIRC 19.06.16 # it's the same data reported by sg0 19.06.19 # ah for inq 19.07.03 # http://paste.ubuntu.com/52527/ 19.08.10 # linuxstb: I'll try again writing to the memory 19.08.40 # funman: Do you know what those bits in CP15 do? 19.08.49 # jhMikeS: can you tell my why HAVE_LCD_ENABLE is defined for the beast even though lcd_enable is not implemented? 19.08.59 # yes, among others it "disables the MMU" 19.09.51 # it clears bits 31, 30, 12, 2, and 0 of the control register of cp15 19.09.54 # interesting, the "UNDEF" vendor is apparently actually sent in the inquiry date (I assumed it was just reported as an unknown string by linux/sg3-utils) 19.10.20 # bertrik: it's reported as well by the linux mass storage driver 19.10.45 # funman: Hmm, I'm just looking at the ARM tech reference now... 19.13.54 Join Thundercloud [0] (n=thunderc@cpc1-hem18-0-0-cust660.lutn.cable.ntl.com) 19.14.03 # funman: Hmm, so it seems like it's definitely not remapping RAM before it zeros the BSS and stacks. So I would say it's already copied to RAM... 19.14.27 Join miepchen^schlaf [0] (n=miepchen@p579ECD96.dip.t-dialin.net) 19.15.29 Join DerDome [0] (n=DerDome@dslb-082-083-248-198.pools.arcor-ip.net) 19.19.42 Join Lear [0] (i=chatzill@rockbox/developer/lear) 19.21.19 # funman: I think we're being stupid - the internal *ROM* is ROM, and I think that just stores a standard AMS bootloader, which will load the main firmware image from the NAND flash disk (or external NOR flash if it exists in the device) 19.21.50 Quit Rob2222 () 19.22.04 # funman: So this trick should work fine... 19.22.42 Join Rob2222 [0] (n=Miranda@p4FDCC548.dip.t-dialin.net) 19.22.51 Quit lasser ("ChatZilla 0.9.83 [Firefox 2.0.0.16/2008070200]") 19.23.23 # LambdaCalculus37: alert me when you're back 19.24.15 # linuxstb: very possible, let me do some tests later this evening/night - right now my brother's girl friend is screaming after me to cook for her :o 19.24.29 # funman: OK, I'm leaving to go home now as well. Speak to you later... 19.26.55 *** Saving seen data "./dancer.seen" 19.28.16 Quit rasher ("leaving") 19.28.19 # kugel: Back! 19.31.52 # kugel: Is it? I wasn't aware of that. 19.32.03 # LambdaCalculus37: I've got a new build 19.33.00 # kugel: Up in the same link? 19.33.02 # jhMikeS: config-gigabeat-s.h line 76 19.33.08 # LambdaCalculus37: sure 19.33.23 # kugel: I'll get the link in the logs. 19.33.52 # kugel: there is no reason for it now until the commands can be sent or if we just wish to have the screen not refresh with no backligh 19.34.04 # LambdaCalculus37: http://www.alice-dsl.net/simonemartitz/forlambda/rockbox.zip 19.37.25 # not #defining it saves 100bytes 19.37.32 # binsize 19.39.05 Quit MethoS- (Read error: 104 (Connection reset by peer)) 19.39.19 # kugel: Here goes nothing! :) 19.39.31 # what? 19.41.29 # kugel: Backlight settings are broken again, clicking a button during fadeout brings the backlight to the setting defined in Backlight Settings, and if the backlight fades out completely, it doesn't come back on. 19.42.09 # the second "issue" is intended 19.42.46 Join {phoenix} [0] (n=dirk@p54B44B39.dip.t-dialin.net) 19.43.37 Quit Hillshum_ ("*puts nose in thick book*") 19.44.07 Quit linuxstb (Read error: 110 (Connection timed out)) 19.45.45 # LambdaCalculus37: While do you smile? :( 19.46.23 # * gevaerts tries to think about how to organize usb endpoints 19.47.02 Quit Darksair ("ERC Version 5.3 (IRC client for Emacs)") 19.48.08 Quit Horscht (Read error: 110 (Connection timed out)) 19.48.35 Join Horscht [0] (n=Horscht@p4FD4BD90.dip.t-dialin.net) 19.48.50 # LambdaCalculus37: next attempt is online 19.50.58 # * LambdaCalculus37 wonders if his Gigabeast is enjoying all of this constant updating the build business 19.51.58 # Crap! 19.52.00 # of course, it's pure joy for him 19.52.13 # * LambdaCalculus37 hooked up the Gigabeast in MTP mode! 19.52.49 Part fragilematter 19.52.49 # will it explode now? 19.56.34 Join shotofadds [0] (n=rob@rockbox/developer/shotofadds) 19.56.47 # kugel: Good news... backlight fade out and fade in are working! 19.56.49 Quit shotofadds (Client Quit) 19.57.05 # what's not working? 19.57.08 Join shotofadds [0] (n=rob@rockbox/developer/shotofadds) 19.57.14 # Backlight settings. 19.57.18 # ok 19.57.39 # kugel: So once you get the entire thing working, make a new patch for Flyspray. 19.59.13 # LambdaCalculus37: next attempt up in a few seconds 19.59.58 # * gevaerts summons vitja 20.05.02 # LambdaCalculus37: now 20.05.50 Quit shotofadds (Read error: 104 (Connection reset by peer)) 20.10.53 Quit Wictor_ (Read error: 104 (Connection reset by peer)) 20.11.04 Join Wictor [0] (n=Wictor@0x57366a52.bynxx19.dynamic.dsl.tele.dk) 20.12.01 Join shotofadds [0] (n=rob@rockbox/developer/shotofadds) 20.12.03 # kugel: "Great success!" :) 20.12.16 Quit perrikwp ("http://www.mibbit.com ajax IRC Client") 20.13.20 Quit moos ("Rockbox rules the DAP world") 20.14.12 # working properly? try with different settings 20.14.23 # also, still clunky? 20.14.55 # kugel: The fading is smoother now. 20.15.13 # Backlight settings work now. 20.15.23 # And it's fading in and out properly. 20.15.33 # I say you've got yourself a patch for Flyspray! :) 20.15.50 # hoi 20.15.51 # it could possibly getting clunky with higher backlight settings. The backlight pwm table gets inconsistent above 15 20.16.08 # kugel: I have my setting at 20. 20.16.25 # play a bit more around please 20.16.26 # spricht hier jemand deutsch?? 20.16.42 # Peter15: not in this channel 20.16.51 # Peter15: English only. 20.17.05 Join saratoga2 [0] (n=9803c264@gateway/web/cgi-irc/labb.contactor.se/x-c253ec83b511a910) 20.17.07 # german channel?? 20.17.27 Quit shotofadds (Connection reset by peer) 20.17.49 Join shotofadds [0] (n=rob@rockbox/developer/shotofadds) 20.18.02 # german channel?? for rockbox problem 20.19.08 Join linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 20.19.13 # kugel: Nope, it's fine through all of the settings above 15. 20.19.18 # Peter15: there's a german forum: www.rockbox-lounge.com 20.19.30 # thx 20.19.40 Join webguest38 [0] (n=2663a552@gateway/web/cgi-irc/labb.contactor.se/x-112ebfa019299c7d) 20.19.49 # LambdaCalculus37: sounds great. How about low settings, how about interrupting it while fading? 20.20.06 # kugel: Let me play around with it. 20.24.01 # kugel: Interrupting it while fading makes the fade in just a wee bit clunky. Other than that, it's working very well. 20.24.12 # * LambdaCalculus37 gives kugel a pizza 20.24.36 Quit webguest38 (Client Quit) 20.24.36 # \o/ now I'm happy! 20.25.25 # LambdaCalculus37: give me a beer instead. I'm already eating mussels 20.25.57 # kugel: http://upload.wikimedia.org/wikipedia/commons/thumb/b/b3/Chimays.jpg/800px-Chimays.jpg 20.26.16 # <3 thanks 20.26.18 # kugel: Flyspray time? 20.26.23 # soon 20.30.31 # Let me know when. 20.34.43 Join faemir [0] (n=quassel@88-106-209-242.dynamic.dsl.as9105.com) 20.36.19 Quit faemir (SendQ exceeded) 20.36.33 Join faemir [0] (n=quassel@88-106-209-242.dynamic.dsl.as9105.com) 20.37.12 Join x1jmp [0] (n=x1jmp@frbg-5d84c0d5.pool.einsundeins.de) 20.38.07 Quit faemir (SendQ exceeded) 20.38.18 # Just discovered that NIN released a new album as CC :) 20.38.21 Join faemir [0] (n=quassel@88-106-209-242.dynamic.dsl.as9105.com) 20.39.05 # they provide FLAC with 24/96, any chance to play them back with rockbox or does it make sense at all to play these files on an iriver? 20.39.56 Quit faemir (SendQ exceeded) 20.40.09 Join faemir [0] (n=quassel@88-106-209-242.dynamic.dsl.as9105.com) 20.40.20 # LambdaCalculus37: it's up 20.40.34 # x1jmp: 24/96? 20.40.35 # LambdaCalculus37: thanks a lot for your testing. Really, you made it possible :) 20.40.41 # x1jmp: you sure? 20.40.59 # ze: 24bit and 96khz, yes I’m sure :) 20.41.12 # kugel: You're welcome. :) 20.41.29 # x1jmp: you talking about ghosts i-iv or another new one? 20.41.40 # cause i bought that in flac and its only 16/44.1 :/ 20.41.52 # ze: the new one is called "The Slip" 20.41.57 # ah 20.42.28 # i guess ghosts i-iv must've done well if they're already doing another and CC'ing it too 20.42.54 Join herrwaldo [0] (n=waldo@ip-81-11-216-181.dsl.scarlet.be) 20.43.03 # are there other CCs released by NIN? 20.43.20 # just ghosts afaik 20.43.38 # btw you can finde the slip there: http://dl.nin.com/theslip/download?token=Tn2bofkq&submit.x=46&submit.y=14&submit=1 20.43.41 # x1jmp: That's off-topic for this channel. 20.44.11 # LambdaCalculus37: sorry 20.44.34 # so can Rockbox play file with 24bit? 20.45.22 # amiconn: Do you know anything about "in-place" UCL decompression? Looking at firmware/decompressor/decompressor.c, that code appears to copy the compressed image to the end of RAM before uncompressing it, but the UCL docs claim the format can be decompressed in-place... 20.45.26 # i saw someone a while back talking about a particular unit being technically capable of it... no idea if it even panned out to be usable as such, or which unit it was, etc 20.45.36 # x1jmp: I'm not sure if it can, but it will have to downsample it to 16 bit 44.1kHz anyway, as that's what the hardware handles 20.46.04 # So it doesn't make much sense to put higher quality files on the player 20.46.34 Quit makicar () 20.46.42 # linuxstb: I have no idea. The thinned-out decompressor definitely doesn't support in-place decompression. And the code does not just appear to copy, it does copy ;) 20.47.14 # amiconn: OK, I'll search the UCL source... 20.47.25 # linuxstb: Btw, I think it would make sense to use thumb on the logicdax for most things (if not all..) 20.47.35 # gevaerts: ah, thanks for that information, that answers my question... 20.48.21 # is the source for the (iRiver) bootloader patch available? I have a wierd problem booting my H340 and I think seeing that source would help me debug it. 20.50.50 Quit Peter15 () 20.51.28 # amiconn: Seems that for in-place decompression, you just put the compressed image at the end of the "output buffer" and use the same decompress function. 20.52.06 Join hannesd [0] (n=light@p5B163307.dip0.t-ipconnect.de) 20.52.42 # Ah, so you have to move the data anyway (if it's not yet where it has to be) 20.52.52 # Yes, not what I would have called "in-place"... 20.53.21 # And in case of decompressor.c it's just not worth calculating the necessary position. We don't lose any ram by putting it at the end. It's temporary anyway 20.56.20 # I think it will be needed in the case of the Sansa V2 bootloaders though - we don't (yet) know what's in the rest of RAM, so it's risky to write to it. So this means we can stay completely in the part of RAM the OF is loaded to. 20.56.23 # * amiconn thinks that this in-place decompression is only useful when loading compressed data from disk 20.58.08 Quit miepchen^schlaf () 21.01.50 Join miepchen^schlaf [0] (n=miepchen@p579ECD96.dip.t-dialin.net) 21.04.38 Join perrikwp [0] (i=d1a8d351@gateway/web/ajax/mibbit.com/x-177d267e56cd3d44) 21.04.41 Join dabujo [0] (i=xx@p4FDB0B17.dip0.t-ipconnect.de) 21.11.40 Quit pixelma2_ ("-") 21.11.54 Join pixelma [50] (i=pixelma@rockbox/staff/pixelma) 21.11.59 Join vcardenas [0] (n=c9f469b4@gateway/web/cgi-irc/labb.contactor.se/x-bac283ad26c51795) 21.13.38 # well... I guess I'm not as bad as some of you guys but I just purchased an iPod mini to CF mod... 21.15.45 Quit saratoga2 ("CGI:IRC (EOF)") 21.21.26 Join bluebrother [0] (n=dom@rockbox/staff/bluebrother) 21.26.24 Quit Nibbler ("Ex-Chat") 21.26.58 *** Saving seen data "./dancer.seen" 21.37.02 Quit saratoga ("CGI:IRC (EOF)") 21.38.58 Quit {phoenix} (Remote closed the connection) 21.39.09 Quit nplus_ (Remote closed the connection) 21.41.02 Join gp_g [0] (n=gp_g@sighthound.demon.co.uk) 21.43.25 Join Siku [0] (n=Siku@e212-246-66-148.elisa-laajakaista.fi) 21.44.18 Join vitja [0] (n=vitja@79.120.98.174) 21.44.31 Join {phoenix} [0] (n=dirk@p54B44B39.dip.t-dialin.net) 21.50.22 Join joecrush [0] (n=42c3f5e2@gateway/web/cgi-irc/labb.contactor.se/x-4e5f5f7d2359d73f) 21.52.00 Join miepchen^schlaf_ [0] (n=miepchen@p579ECD96.dip.t-dialin.net) 21.52.45 # Hi, I was looking for a particular Rockbox build that incorporates a hardware patch that was being worked on 21.54.05 Quit Schmogel ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 21.54.18 # joecrush: We don't really track or provide support for unsupported builds 21.54.20 Join Schmogel [0] (n=Miranda@p3EE21737.dip0.t-ipconnect.de) 21.54.59 # joecrush: telling us what this patch is might also help... 21.55.34 # Unfortunately I don't remember the name, it was one that was attempting to make Rockbox work with some hardware such as car iPod players and such 21.55.44 Quit gp_g ("Leaving") 21.56.07 # ah, you want soap's apple accessory protocol build. See the unsupported build section on the forums 21.56.36 # * gevaerts hopes that Llorean will grant an exception for this particular build 21.57.44 Join petur [50] (n=petur@rockbox/developer/petur) 21.57.52 # Ah, that's it, thanks a lot 21.58.16 # gevaerts: I didn't say we couldn't tell him about it. Just said we don't really track them. 21.58.39 Quit LambdaCalculus37 ("http://www.mibbit.com ajax IRC Client") 21.58.39 # Llorean: indeed you didn't :) 21.59.48 Quit BlakeJohnson86 (Read error: 110 (Connection timed out)) 22.02.05 Quit jhulst (Read error: 110 (Connection timed out)) 22.03.22 Quit ompaul (No route to host) 22.03.32 # petur: could http://forums.rockbox.org/index.php?topic=18809 have to do with the patch you committed? There are two reports, both are on Ipod Mini (as I remember there were issues with the Minis and it reminded me of the first reports of midiplayer on PP targets where the midis where played twice as fast because it used 22.05kHz sample rate so maybe if their files are lower sample rate too...). Just a guess though 22.03.55 Join ompaul [0] (n=ompaul@gnewsense/friend/ompaul) 22.04.31 # pixelma: yes, I made an error there that I still have to fix 22.04.40 Join joe2371 [0] (n=joe@c-69-138-250-166.hsd1.md.comcast.net) 22.07.28 # ok, was just wondering if this wrong playback could be the result of that 22.08.07 # amiconn already pointed me at my error :/ 22.08.27 Join jeffdameth1 [0] (n=jeff@dyndsl-091-096-051-023.ewe-ip-backbone.de) 22.09.33 # MarcGuay: I wouldn't go saying "Unprovoked" right off the bat without knowing how he's been using the player, etc, or really commenting on it at all without first checking if the OF has the same sort of thing happen to it occasionally. 22.09.39 Quit jeffdameth (Read error: 60 (Operation timed out)) 22.11.22 # * linuxstb finds a UCL decompress function in 178 bytes of hand-written thumb code, compared to about 1500 bytes of gcc generated ARM code... 22.11.57 Join avis [0] (n=ident@pdpc/supporter/student/avis) 22.12.56 # When upgrading to r18670, do I need to rebuild the bootloader as well? Or can I use the one from r18529? 22.13.32 Quit joecrush ("CGI:IRC (EOF)") 22.13.41 # joecrush: bootloaders are only updated very rarely 22.14.09 # gevaerts: ok, thanks. 22.17.28 Quit miepchen^schlaf (Read error: 110 (Connection timed out)) 22.20.10 Quit {phoenix} (Remote closed the connection) 22.21.03 Quit miepchen^schlaf_ (Connection timed out) 22.31.11 Join miepchen^schlaf [0] (n=miepchen@p579ECD96.dip.t-dialin.net) 22.31.22 # linuxstb: do we still want to experiment with thumb some day? 22.32.52 # markun: Yes, I think so. The Clip for example only has 320KB of RAM... Some of the telechips flash-based targets (DAX, M200) have 2MB, but even there, thumb will probably be useful. 22.33.14 Quit Lear ("ChatZilla 0.9.83 [Firefox 3.0.3/2008092417]") 22.35.15 # anybody with a mini 1g/2g here that could test if playback works again now? 22.35.41 # petur: I'm on it. Current revision and just before? 22.35.47 # Also, what sort of files? 22.35.50 # latest 22.36.11 # gevaerts: Should be any, but reported on MP3 and FLAC. 22.36.21 # I'm just thinking that reproducing with a slightly older revision first would be useful 22.37.15 # the current 'daily' probably has the bug 22.40.23 # How does the version in svn typically compare to the latest release? Obviously, there is a greater chance of breakage in the svn version... but mostly in parts of the tree under heavy development. I should think there would also be more chances of... "fixage" (to coin a term) in svn as well, at least in parts of the tree that are not under heavy development at the moment, but that have seen a good bit of development since the last rel 22.40.23 Quit hannesd (Read error: 113 (No route to host)) 22.40.24 # * gevaerts builds builds 22.40.43 # downloading would have worked too ;) 22.40.53 # true :) 22.41.02 # downloading binaries is for squares 22.41.14 # * gevaerts looks at funman 22.41.24 # joe2371: generally speaking, the svn builds are rather stable but if you're unlucky you may hit one that is bad 22.41.46 # Bagder: how unlucky? Like bricked, unlucky? Or just pita unlucky? 22.41.48 # joe2371: the main thing about running the release is that the bugs are (mostly) known 22.41.55 # gotcha 22.42.12 # joe2371: just unlucky to the extent you may need to get another build to get a working rockbox again 22.42.51 # Bagder: or revert to last release so you can listen to music while you wait for commits? 22.43.00 # yeps 22.43.15 # I am less concerned now. :-) 22.43.21 # * gevaerts likes the effect of petur's bug :) 22.43.26 # most of us here always run svn builds... 22.43.46 # gevaerts: plays at double speed? 22.43.46 # petur: any chance of having that as a setting? 22.43.46 # oic, well that makes hacking.. well... more topical, at least. 22.44.04 # petur: Now building the fixed one 22.44.16 # gevaerts: try the pitch screen for that effect 22.44.32 # Or for the workaround :) 22.46.27 Quit meven (Remote closed the connection) 22.46.58 # petur: r18673 works properly 22.48.03 # http://forums.rockbox.org/index.php?topic=18798.msg135751 looks like a bug to me. That's at least the third one in the last week or so 22.48.48 # gevaerts: thanks 22.52.30 # Could this be caused by JdGordon's playlist cleanup? 22.53.46 # jhMikeS: hey, I got the fading to work, just might want to watch it on your devices 22.54.17 # I have a sansa e2X0 and I have been starting to hack around with it. However, I was dismayed to discover that the Portal Player pp50XX chips are NDA'ed. The modifications I have in mind almost all would use the undocumented hardware registers of these chips. Does anyone know if any documentation of these registers exists within the FLOSS community? Or does (anyone know if) rockbox merely hook(s) into the OEM firmware somehow? 22.54.45 # joe2371: all the PP knowledge we have is 100% reverse engineered 22.54.47 # there is no docs 22.54.48 # I mean, is there a rockbox-sansa-hacking group? 22.55.00 # sure, we're here 22.55.12 # * pixelma hands out the axes 22.55.12 # the rockbox dev group is a single large one 22.55.21 # Ok. 22.55.21 Join MethoS- [0] (n=clemens@host-091-097-242-050.ewe-ip-backbone.de) 22.55.49 # So the PP knowlege we have is entirely contained in the sources? 22.55.50 Quit herrwaldo (Remote closed the connection) 22.55.57 # yes, and in the wiki 22.56.04 # In the sources, the wiki, and some heads 22.56.05 # and some used to be found in the ipl wiki 22.57.08 # and on my sansa pages 22.57.24 # like http://daniel.haxx.se/sansa/e200.html 22.57.35 # Well, fortunately, Portal Player was bought by nVidia, so the full whitepapers ought to be freely available any minute now. ;-) 22.57.40 # ha 22.57.41 # but that's perhaps not so PP but more sansa 22.57.56 # joe2371: yeah right 22.58.13 # nvidia, the frontier of freedom! 22.58.46 Join herrwaldo [0] (n=waldo@ip-81-11-197-92.dsl.scarlet.be) 23.00.14 Join freqmod_qu [0] (i=quassel@iskrembilen.com) 23.00.29 # I don't suppose Linus is here? 23.00.45 # Apparently not 23.01.00 # :-) 23.01.22 # Unless he's undercover, spying on us with a different nick 23.01.26 # I have questions about the iriver bootloader, and I think he'd know. 23.01.36 # I also have an H340 that doesn't boot. :-( 23.01.42 Quit freqmod_qu (Remote closed the connection) 23.01.50 Quit mf0102 ("Ex-Chat") 23.02.23 Join freqmod_qu [0] (i=quassel@iskrembilen.com) 23.02.36 # You could always ask. Maybe someone else knows 23.04.02 # or maybe LinusN reads the logs? 23.04.03 # ok. I boot my H340, and get "ATA Error: -1." I see from reading iriver_h300.c this indicates a -1 returned from ata_init() 23.04.06 # but.... 23.04.27 Join miepchen^schlaf_ [0] (n=miepchen@p579ECD96.dip.t-dialin.net) 23.04.37 # if I turn it on by inserting the cable, it goes into 'Bootloader USB mode', and when I remove the cable it boots into rockbox properly. 23.05.05 # * funman looks back at gevaerts 23.05.09 # it almost seems like the drive isn't spinning up fast enough to init. (but that's just my uneducated theory) 23.05.17 # if anyone has suggestions, I'm listening. 23.06.22 # damn it 23.06.38 # * gevaerts wonders if funman downloads binaries ;) 23.06.44 # * ameyer gets yet another stkov on his sansa 23.07.50 # bill2or3: could be. Maybe there is a delay you could increase. The problem is that if you get the bootloader wrong on a h300, you have real problems 23.08.18 # yeah, I'm not so anxious to start mucking around with it at random. 23.09.37 Join webguest35 [0] (n=62905a0f@gateway/web/cgi-irc/labb.contactor.se/x-831069032a41a52c) 23.10.06 # hey how can i fix a corrupted version.txt on the sansa e280r? 23.10.31 Quit miepchen^schlaf (Connection timed out) 23.15.06 Quit webguest35 ("CGI:IRC (EOF)") 23.15.52 Join webguest68 [0] (n=62905a0f@gateway/web/cgi-irc/labb.contactor.se/x-c528e45b3b9a407d) 23.17.25 Quit x1jmp (Remote closed the connection) 23.17.54 # webguest68, have you tried the e200tool? 23.18.15 Quit domonoky (Read error: 104 (Connection reset by peer)) 23.18.19 # does the firmware really care about version.txt? 23.18.27 Quit bughunter2 ("bye") 23.19.32 Join tvelocity [0] (n=tony@195.167.65.111) 23.20.24 # Bagder, i have seen the OF check it i think because OF not to boot anymore but recovery mode works 23.21.00 # yes I have, advcomp 23.21.17 # I found a thread where the version.txt fixed the problem 23.21.42 # but i that was with an e250 23.23.03 Join SpaceTraveler [0] (n=hatherg@host86-136-157-251.range86-136.btcentralplus.com) 23.27.00 *** Saving seen data "./dancer.seen" 23.27.03 # Is Rockbox being developed for the Olympus Mrobe i500? 23.27.20 Quit petur ("Zzzz") 23.27.40 Quit maddler ("connection reset by beer!") 23.28.00 # webguest68: it's exactly the same 23.28.14 # the version.txt? 23.28.19 # funman: not entirely. webguest68 has an e200r 23.28.43 # funman: I've just posted my UCL suggestion to the forum thread... 23.28.59 # ah sorry the difference is with rhapsody models 23.29.01 # SpaceTraveler: some progress have been made but it seems to have stalled lately 23.29.07 # true... but i pasted a verion.txt from a e260r over my corrupted one, but it didn't work 23.29.11 # i did it 3 times. 23.29.19 # linuxstb: cool :) 23.29.48 # ok...I'll keep checking back...thanks 23.30.19 # funman: I'm thinking I can use one of my other ARM targets to test this code on. For example, on my Logik DAX I have a very safe "usb boot mode" where I can upload code to RAM and run it, without fear of bricking. 23.31.47 # linuxstb: if you're not in a hurry we can wait for someone to test the code on a e200 23.32.06 # funman: That's no fun ;) 23.32.44 # or wait until tomorrow when I decide to buy an e200 by excitement :P 23.33.30 # funman: you'll get a v1 23.33.49 Join jfb9301 [0] (n=jfb9301@cpe-67-49-143-82.hawaii.res.rr.com) 23.34.05 # funman: BTW, what is the "toolchain" atomicpunk is referring to here? http://forums.rockbox.org/index.php?topic=14064.msg135686#msg135686 23.34.38 # gevaerts: then I'll have rockbox running and my mission will be over ! 23.34.55 # * linuxstb wonders if there is a way to view an entire forum thread on one page 23.35.21 # linuxstb: I don't know, probably the gcc he built with rockbox script on windows 23.35.21 # * linuxstb discovers the "print page" option... 23.35.35 # linuxstb: have you already tried to run such a compressed firmware? 23.35.42 Join perrikwp|work [0] (i=982132ec@gateway/web/ajax/mibbit.com/x-a80b804bb7f7d2b5) 23.36.10 # kugel: No, I haven't built one yet... 23.36.11 # I have a question about using the Peak Meter on the WPS 23.36.28 # kugel: it's actually used for low-size archos : look in firmware/decompressor 23.37.01 # funman: I think linuxstb was refering to another algorithm 23.37.19 # kugel: No, that's the same thing 23.37.39 # is there any way of customizing the peak meter similar to the way you can customize the progress bar on the WPS? 23.37.45 # is this the 180byte one (I haven't looked at it yet) 23.38.30 # kugel: No, the 180-byte thumb version is part of the upx-3.03 source archive. Rockbox currently uses the C version 23.38.56 # And I thought you were referring to this one 23.39.02 # ah upx .. I know this for packing executables, I was googling to get an ucl compressor :) 23.39.45 # the e200v1 should also be safe to test such a firmware, given that the manufactoring mode is basically always available 23.40.01 # and then, there's even the preboot mode 23.40.25 # upx comes with an arm thumb asm decompressor? Nice. 23.40.42 # ;j 23.40.46 # kugel: preboot ? 23.42.12 # funman: the v1 have 4 modes, normal, recovery, manufactoring, preboot. From any of it, you can recover (except the first one maybe ;) ) to a working state 23.42.13 Quit webguest68 ("CGI:IRC (EOF)") 23.42.13 Quit vcardenas ("CGI:IRC (EOF)") 23.42.56 # jfb9301: No, but it's been discussed in the past. So maybe someone will be interested enough to do it at some point... 23.43.27 Quit Hillshum (Read error: 110 (Connection timed out)) 23.43.46 # funman: have you read my answer to linuxstb's post? 23.44.03 # thanks, I sure hope someone does. I was trying to modify a WPS to have both a progress bar and a peak meter that was not the run of the mill monochrome one 23.44.24 # kugel: yes but I am not sure of the right answer 23.44.56 # jfb9301: You can define a viewport with custom colours (and width), and put the peakmeter in there, but I think that's all... 23.45.18 # * pixelma deletes similar suggestion from input line 23.45.39 # the manual also does not mention if rockbox now supports APEv2 tags, I searched the web and it appeared that it did not, yet replaygain seems to function as if rockbox does recognize APEv2 23.46.10 # jfb9301: It supports APEv2 tags for files where it's the native tag format. For MP3 Rockbox only supports id3v1 and id3v2 23.46.27 # custom colors and width? where might i research that? 23.46.39 # jfb9301: Read about viewports in the CustomWPS wiki page 23.46.58 # customwps wiki page, got it 23.47.21 Quit shotofadds (Read error: 60 (Operation timed out)) 23.48.19 Quit dabujo (Read error: 104 (Connection reset by peer)) 23.48.24 # kugel: How do you know that the player doesn't update itself after you dd the new firmware to the NAND? And how do you know you're dd'ing to the NAND, and not a RAM disk (like the e200v1 recovery mode) 23.48.40 # odd about the apev2, when no apev2 was present, 50% of the time my mp3s would clip out. using mp3gain (which only creates APEv2) appeared to make rockbox function in replay gain 23.48.45 # * linuxstb doesn't know about the e200v2's recovery mode... 23.49.06 # jfb9301: are you sure mp3gain writes replaygain tags? 23.49.29 # linuxstb: why using ucl ? we don't need to pack an executable and another algorithm might give use more room, even if the function which decompresses it is longer than the ucl one 23.49.34 # I remember some tool that used ape tags to remember the original amplification and changing it in the files directly 23.49.55 # jfb9301: unless you tell it to do otherwise, it will actually rewrite the files, and record undo data in ape tags... i *think*. 23.49.57 # funman: You're confusing upx and ucl 23.49.59 Join Zarggg [0] (n=zarggg@65-78-69-194.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 23.50.05 Join lasser [0] (n=chatzill@Wa291.w.pppool.de) 23.50.11 # mp3gain writes gain tags as APEv2 tags, but not to the id3 tags 23.50.41 # linuxstb: the firmware is written to the firmware partition. As I said, I might've gotten it wrong, I don't have a e200v2 23.50.42 # Unhelpful: I think you're right. 23.50.42 # funman: The advantage of ucl is that it decompresses very fast, and the decompression code is tiny (180 bytes for thumb) Show me another decompression function that small... 23.50.54 # I made sure I was not rewriting the files, but just gain tags 23.51.08 # linuxstb: right, it presents very good features (no memory for decompression also) 23.51.44 # funman: Yes, that's the other good feature for us - we can do all of this within the space of the original firmware. 23.52.25 # jfb9301: well, if it stores "undo" information as the FAQ says it's not only tags like the ReplayGain Rockbox supports 23.52.50 # also, ReplayGain has two tags: album and track gain 23.54.19 Join hospadar [0] (n=2309286e@gateway/web/cgi-irc/labb.contactor.se/x-5db43b962b068409) 23.54.31 # howdy 23.54.44 Quit culture (Connection timed out) 23.54.58 # So I just canned my zen so I could buy a gigabeat and play with rockbox 23.55.05 # and I'm wondering about developing for it 23.55.20 # Which gigabeat? 23.55.25 # where would I go to find out who needs what written 23.55.29 # an F40 23.55.49 Quit mcuelenaere (Read error: 110 (Connection timed out)) 23.56.06 # There's not that much left that's specific to the F40. The main missing "hardware feature" is I think to flash a Rockbox bootloader to the flash ROM, which kkurbjun is (slowly) working on. 23.56.21 Quit jgarvey ("Leaving") 23.56.30 # well is there general stuff that needs to be worked at all? 23.56.46 # jfb9301: from the wikipedia article it _does_ modify the files, and thus it works differently than the ReplayGain tags Rockbox supports: http://en.wikipedia.org/wiki/MP3Gain 23.56.53 # hospadar: Yes, everything ;) 23.57.36 # bluebrother, what you are saying seems to make things make a little more sense. while my files were no longer clipping, the preamp gain of the replay gain was not funtioning. 23.58.09 # hospadar: You should simply download the source and start fixing things you don't like, or implement new features... The bug/patch tracker could be a good place to start - either fixing bugs, or working on patches to get them to commit-quality. 23.58.16 # sure. I looked at that software a while ago myself when searching for a tool to add replaygain tags to mp3 files. 23.58.27 # fortunately my music is now ogg ;-) 23.58.34 # so, from that maybe mp3gain adjusted the gain of the mp3 and stored the undo in the apev2 tag. like you said. 23.58.48 # so, how do i ad replaygain to the id3 tags?