--- Log for 16.03.109 Server: grisham.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 1 month and 9 days ago 00.00.15 # well, if you want to do hardware it might be a good idea to talk with the people that do the software. Same the other way round -- the only problem is that commercial hardware companies don't come here ;-) 00.02.25 # bluebrother: a long time a ago I started writing on Rockbox wiki about the hardware, and I went here asking about it... 00.03.01 # for example, I remember that at first times I wanted to use AVR32... and I clear remember Bagder explain why we should use ARM... 00.03.19 # I remember and wrote the values of RAM, etc, etc 00.03.21 Quit t0mas ("Leaving") 00.03.47 # well, that was hardware talk, was it? 00.04.05 # gevaerts: Seen FS10026? 00.04.19 # people working on embedded software need to have knowledge about hardware too -- at least to some degree 00.04.29 # bluebrother: that was a talk to define the minimum hardware needed to run Rockbox 00.05.02 # so it's hardware talk. 00.05.04 # Llorean: interesting 00.05.13 # well, I wrote all the links to datasheets of every piece of hardware, including application notes with code 00.05.21 # * bluebrother starts to think this discussion is getting pointless 00.05.22 # gevaerts: It's not saratoga's problem, but it's *an* e200 problem. 00.05.26 # so what? 00.05.37 # bluebrother: sorry, I may not understand you 00.05.55 # please explain, directly 00.05.56 # Llorean: indeed, and moreover one that I hadn't heard about yet... 00.06.03 Join moos [0] (i=Mustapha@rockbox/staff/moos) 00.06.22 # well, talking about hardware is hardware talk, is it? 00.06.22 # I am getting this error while building: make: *** Sem regra para processar o alvo `/home/cas/Documentos/rockbox_player/rockbox/build_firmware/apps/=======', necessário por `/home/cas/Documentos/rockbox_player/rockbox/build_firmware/rockbox.elf'. Pare. 00.06.39 Part AlHaz ("Leaving") 00.06.42 # yes, no? 00.06.47 # gevaerts: Did you also read Toni's comments here this morning? 00.06.48 # * bluebrother suggests LANG=C 00.06.54 # sorry, I don't reallt understand what you mean 00.06.54 # gevaerts: It does seem to indicate there are some (further?) differences between Sansa USB and iPod USB 00.07.10 # Sem regra para processar linguas 00.07.28 # * bluebrother has no idea if that is a valid sentence at all :) 00.07.29 # casainho: That looks like a conflict in a SOURCES file 00.07.29 # casainho: looks like you have a merge conflict in this file... 00.07.48 # 'svn st' tells you 00.07.56 # linuxstb: I saw it, yes. I wanted to ask saratoga to try it when he has a chance 00.08.04 # casainho: set the compiler to use english language. At least I don't understand spanish 00.08.05 # thanks :-) :-) 00.08.24 # bluebrother: hmmm, I don't know how to do it 00.08.28 # while one can guess the meaning at times it's annoying 00.08.34 # export LANG=C 00.08.42 # Llorean: anyway, I'm not convinced that FS#10026 this isn't related to saratoga's problem either 00.08.53 # bluebrother: so, what do you want to talk about that subject of hardware??? 00.09.05 # gevaerts: I was gonna say "there's a part of me that really hopes it's just the same problem, manifesting in different ways" 00.09.54 # well, right now there is nothing to talk about, as far as I can see. 00.10.11 # but if other people have tasks (like creating a patch), why shouldn't they come here? 00.10.42 # Llorean: here too. I know e200 (and to a lesser degree c200) have more retried packets than the ipods and than the OF. I'll check tomorrow if that changes with this patch 00.11.23 # for some curious reason the ipod 5G EDM also has lots of those, but still less than the e200 running rockbox 00.11.49 # bluebrother: well, I can say this to Hector... I don't know if he comes here or not. Since he tolds me he builds is own Rockbox source for his Ipod, I hope he is at least familiar iwth rockbox tools... he talked a bit with me about Rockbox tracker... 00.12.30 # and why does he talk with you instead of the "community"? 00.12.57 # that's the thing I really don't get. Why are you working in you "own space" instead of the public? 00.12.59 # fwiw, #10026 doesn't appear to have adverse effects on an ipod 5g 00.13.07 Quit Conic () 00.13.29 # n1s: FS#10025 would have been a feature request, as far as I understand. 00.14.39 # bluebrother: well, since begin I didn't saw much interest from others on this project 00.14.46 # stripwax: good to know. I still want to look at what the tracer reports for every single target I have available after changing that though 00.14.56 # makes sense 00.15.01 # bluebrother: and we did need our SVN, at least I thought it... 00.15.04 # bluebrother: yes, that's what i guessed. however being _that_ unclear and just ignoring the guidelines... 00.15.30 # bluebrother: you know, I am always here getting help... I got a lot of help here!!! 00.16.16 # I mean, using the tracer I can see every single individual error. Without it, it's just statistics. If you happen to have enough in a short time, you see problems. If they happen to be spread out, it works fine 00.16.28 # bluebrother: and I wasn't seeing using the Rockbox mailing list to comunicate beteewn us, for our project 00.17.02 # bluebrother: Are the list of changes under "svn (upcoming release)" fixed? 00.17.11 # (sorry, I meant in RockboxUtility wiki page) 00.17.14 Quit stripwax ("http://miranda-im.org") 00.18.50 # bluebrother: and there is the guys that bought the development board... since begin I was told from Rockbox developers that the ones that make the Rockbox port are the ones that have, own that hardware. 00.20.41 # linuxstb: the items marked with a ! are still present 00.21.14 Quit barrywardell () 00.21.15 # bluebrother: How about moving them to a "known issues" section? 00.21.43 # I have a patch around for addressing the osx remount issue though it might not work though. 00.22.02 # linuxstb: sounds reasonable to me 00.22.42 # bluebrother: OK, I'll do that. 00.23.04 # I can't figure in what file I have problems:: make: *** No rule to make target `/home/cas/Documentos/rockbox_player/rockbox/build_firmware/apps/=======', needed by `/home/cas/Documentos/rockbox_player/rockbox/build_firmware/rockbox.elf'. Stop. 00.23.33 # casainho: I'd guess apps/SOURCES 00.23.42 # casainho: The ones that own the hardware do the work, yes. But they still do it in communication with the group, posting patches as they go (look at the AMS Sansa port) so that others can become involved quickly and easily. 00.25.04 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-e07c10c1037b0c68) 00.25.04 # I tink is my fault, I want the best, but I am not experiencied... I used SVN here for the first time, I used JTAG debug for first time, diff and patches for first time, etc 00.25.21 Quit domonoky (Read error: 104 (Connection reset by peer)) 00.25.46 # I thought that wrinting information on wiki were good for people follow the project, the idea 00.25.49 # gevaerts: "ipod 5G EDM". EDM=? 00.25.58 # gevaerts: what should I try? 00.26.04 # soap: sorry, "emergency disk mode" 00.27.22 # gevaerts: ok, it was apps/SOURCES :-) thanks 00.27.24 # casainho: Patches, early on and all along, are good. Things like adding it to the build system, getting the simulator running, building the bootloader, building the build (even if it doesn't work) etc. 00.27.27 # casainho: writing documentation to some place is not communicating, it's documenting. But I'll shut up now. 00.27.44 # These allow people to see the code and comment on it (which can help avoid issues like coding style that can result in you needing to rework things later) 00.27.47 # saratoga: http://www.rockbox.org/irc/log-20090315#11:22:38 and FS#10026. Both *may* help. I'd suggest trying without FS#10015 to increase the chances of triggering the problems 00.27.59 Quit amiconn (Nick collision from services.) 00.28.02 Join amiconn_ [50] (n=jens@rockbox/developer/amiconn) 00.28.03 Join pixelma_ [50] (n=pixelma@rockbox/staff/pixelma) 00.28.03 Quit pixelma (Nick collision from services.) 00.28.15 Nick pixelma_ is now known as pixelma (n=pixelma@rockbox/staff/pixelma) 00.28.20 Nick amiconn_ is now known as amiconn (n=jens@rockbox/developer/amiconn) 00.28.20 # saratoga: my bet is that if any of them helps, it's FS#10026 00.28.28 Join jordoex_ [0] (n=quassel@d154-20-29-131.bchsia.telus.net) 00.29.22 Quit jordoex (Nick collision from services.) 00.29.31 Nick jordoex_ is now known as jordoex (n=quassel@d154-20-29-131.bchsia.telus.net) 00.29.48 # Llorean: well, now I know how to do patches, and I am always put them on our SVN, for other can use them... -- and now someone told me that our patch is big and wee need to start making a first one, simple and short, and thats what we are doing now. 00.30.16 Join akur [0] (n=akur@bl7-91-233.dsl.telepac.pt) 00.30.33 Part akur 00.30.36 # Llorean: and as I said in forum, I put a patch on tracker, with the help of Domonoky (If I remember correclt) 00.31.15 # casainho: I'm just trying to explain why it seems like there's not much communication to us. 00.31.38 # casainho: How stable is your hardware design? I mean, is it worth trying to put your code in SVN, or will future designs be completely different (meaning the code is useless...) ? 00.31.55 # Llorean: okok. thanks. 00.32.03 # linuxstb: that's a good question :-) 00.32.48 # linuxstb: at least MCU AT91SAM9260 should be the same... or at least AT91SAM92xx 00.33.24 # OK, then it would seem sensible to try and commit your changes to support that chip. 00.33.31 # LCD, audio DAC, buttons can change, easily, depends on company that will produce 00.33.41 Quit Rondom ("Ex-Chat") 00.34.34 # but do you mean that all the code for the all player should not be on Rockbox SVN? 00.35.56 Quit n1s ("Lämnar") 00.36.19 # casainho: I don't know. If it is just for "temporary" hardware, then maybe not. 00.36.39 Quit ender` (" I will not interrogate my enemies in the inner sanctum -- a small hotel well outside my borders will work just as well. --") 00.37.17 # linuxstb: the question is that we don't know if is temporay or not, or how many temporary... 00.37.42 # But I think code to support a new CPU is useful, so maybe the first thing to do would be to try and produce a nice patch to add the CPU-specific code. 00.38.06 # I would like to have a company producint it... it can hapen quickly or not... -- maybe we will stick with that hardware long time... doing our own borads ans assembling... 00.38.33 # someone told to make a kernel_init() patch... 00.39.32 # but, isn't there code on SVN from unfinished targets? 00.39.41 # and imcomplet? 00.39.57 # Incomplete ports, yes - the hardware is finished... 00.40.07 # at least we hope so :) 00.40.10 Join |ahmina| [0] (n=lymeca@213-213-141-71.xdsl.is) 00.40.28 # someone. Reminds me of MrSomeonesTodoList :P 00.41.25 Quit lymeca (Connection reset by peer) 00.41.28 # * gevaerts is in favour of committing, provided the code is clean 00.41.29 Quit |ahmina| (SendQ exceeded) 00.41.31 # eheh - but the port can stay for all the time unfinished... and with hardware out of market, production... so, finished hardware and "dead" 00.41.57 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is) 00.42.06 # Hardware keeps working for years - it is easy to buy used hardware. 00.42.31 Quit bluebrother ("http://www.mibbit.com ajax IRC Client") 00.43.00 Quit lymeca (SendQ exceeded) 00.43.11 # casainho: I can still buy used versions of the unfinished ports to commercial players. If you discard your prototype, there's nowhere for me to purchase one unless I wish to construct my own. I can't order one from somewhere if it's a discarded prototype 00.43.13 # linuxstb: I don't believe on it... hardware will fade out, not available 00.43.53 *** Saving seen data "./dancer.seen" 00.43.55 # Llorean: at least of have the information to make it, not as a comercial 00.43.56 # Yes, after many years. But by that time, Rockbox has supported newer targets. 00.44.18 # And we've done a pretty good job without documentation for many players... 00.44.19 # and so, on that time, what is that code for on SVN? 00.44.21 # and we _can_ still rip out old rotting code 00.44.46 # I can't imagine there's much of a resale market for used embedded CPUS anyway. 00.44.46 # casainho: no port has reached that state yet 00.44.57 Join sir_yodle [0] (n=theyon@pool-141-152-46-244.rcmdva.btas.verizon.net) 00.45.10 # anyway, I am mainly worried to have all the code and information available on Rockbox SVN... 00.45.12 # While I can hop on ebay or craigslist and find a Jukebox 6000 still, probably. 00.45.40 # so after what I've registered, there's no sound working on the Creative Zen Vision:M port? 00.46.02 # bubsy: how is that related to any registration? 00.46.05 # bubsy: It's not supported yet, so it shouldn't be expected to be in a usable state. 00.46.24 # and I'm sure you can help it become reality! 00.46.26 # Bagder: Hencing "to register" as "to notice" 00.46.34 # oh 00.46.50 # * Bagder tries to blame the time or something 00.47.24 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is) 00.47.27 # Bagder: I wish I could, but I don't have any worthy knowledge on that area :-) 00.47.50 # the creative ports are massively undermanned 00.48.23 # Yeah, makes me want to hang my head and cry sometimes. 00.48.30 # maurus is about the only one, and he's the "only one" for a range of devices 00.48.45 # in fact, he must be nuts! ;-) 00.48.46 # Bagder: Would it be possible for someone (you!) to arrange to rsync the logs from the download servers and produce some nice stats? 00.49.22 # not a bad idea, I'll do a check with the mirror guys 00.49.25 Quit flydutch ("/* empty */") 00.49.49 # they're only two these days 00.50.00 Part sir_yodle 00.52.56 Join midgey [0] (n=tjross@71.238.148.140) 00.53.55 # casainho: Going back to talking about SVN, I would suggest trying to create small patches that add your code a small part at a time. That makes it easier for other people to review and hence more likely that someone will commit. 00.54.45 # linuxstb: okok. We are working on it :-) 00.55.01 # but that task is with other developer, not me. 00.55.09 Join perrikwp [0] (i=4aa794a0@gateway/web/ajax/mibbit.com/x-bba641abdd3b6904) 00.56.13 Quit lymeca (Connection reset by peer) 00.58.01 Quit vmx ("Leaving") 01.00.04 Quit bubsy ("Mrrrrreow!") 01.00.23 # so, I did update my version to actual of SVN, but I am getting the same problem:: http://pastebin.com/m31557ad8 01.00.54 # why on here "int spinup = ata_spinup_time();" PC jumps to a variable on BSS section? 01.01.31 # ata_spinup_time variable... 01.07.08 # can't anyone help me? or give some idea? 01.08.07 Join sir_yodle1 [0] (n=theyon@pool-141-152-46-244.rcmdva.btas.verizon.net) 01.15.01 # casainho: Can you post your rockbox.map file? 01.17.26 # here: http://pastebin.com/m514dfdca 01.17.38 # I were seeing the disassembled file, do you want it? 01.17.45 # do you want the patch? 01.18.29 Quit Thundercloud (Remote closed the connection) 01.19.00 Quit faemir ("Lost terminal") 01.19.09 Quit gregzx ("ChatZilla 0.9.84 [Firefox 3.0.7/2009021910]") 01.20.07 Quit midgey () 01.25.27 # casainho: Have you defined HAVE_FLASH_STORAGE in your config-xxxx.h file? 01.25.50 Join midgey [0] (n=tjross@71.238.148.140) 01.26.26 # no... just SD Card, I think -- I will check 01.27.24 # just this: #define CONFIG_STORAGE STORAGE_SD 01.27.45 # is ok, no?? well, at least I could see the files before... 01.28.00 # You need to #define HAVE_FLASH_STORAGE 01.28.06 # why do you even have ata_spinup_time() then? 01.28.46 # and leave also the #define CONFIG_STORAGE STORAGE_SD ? 01.29.09 # yes 01.30.09 # ok, I will run the code again... 01.35.14 # ok, it's running :-) 01.35.24 # but now it says "Codec failure"... 01.36.11 Join sarixe [0] (n=sarixe@pool-68-239-154-103.nwrk.east.verizon.net) 01.36.26 # and also gave a panicf on SD Card functions.... :-) eheh 01.36.29 # bad code :-) 01.37.43 Quit moos ("good night europe") 01.38.25 # okok, I tested again with an MP3 file and I got to times saying "Codec failure" and after panic on SD Card... I need to verify the drivers for SD Card :-) 01.38.34 # I will go to sllep now :-) 01.38.38 # thanks for all ;-) 01.38.40 Quit casainho ("ChatZilla 0.9.84 [Firefox 3.0.7/2009030422]") 01.46.03 Join curse [0] (n=curse@bitchx/staff/curse) 01.48.55 Quit petur (Read error: 110 (Connection timed out)) 01.53.31 Quit sarixe ("Leaving") 01.53.50 Join MethoS- [0] (n=lem@host-091-096-209-116.ewe-ip-backbone.de) 02.00.14 Join sonar___ [0] (n=sonar@c-67-169-92-39.hsd1.ca.comcast.net) 02.00.37 # Llorean: perhaps FS10026 problem is also applicable to my Gnome non detection well perhaps 1 in 30 detections? 02.01.41 # hows it going everyone, I have a sandisk sansa view, but the second kind of view that was recently released and is based off of the e200 series, not the discontinued one. I was wondering If the e200 firmware would work, or if there were any plans of porting it if not. 02.04.27 # gevaerts: could you make a patch for FS10026 so I can test it on my sansa? 02.05.31 # robin0800: not now, I'm just going to sleep... It looks trivial though 02.05.49 # sonar___: theres only one view and none of them are based off the e200 02.06.04 Quit robin0800 (Remote closed the connection) 02.06.11 Quit perrikwp ("http://www.mibbit.com ajax IRC Client") 02.06.37 Quit tessarakt ("Client exiting") 02.06.51 # saratoga, mine looks like that http://www.straferight.com/photopost/data/716/SanDiskSansaView.jpg 02.07.15 # the discontinued one looks like http://images.google.com/imgres?imgurl=http://www.slipperybrick.com/wp-content/uploads/2007/01/sandisk-sansa-view-player.jpg&imgrefurl=http://www.slipperybrick.com/2007/01/sandisk-sansa-view-video-player/&usg=__yiu3bv3-Lj8F76TK9I8GoAYs1Fo=&h=515&w=500&sz=75&hl=en&start=27&um=1&tbnid=2bNiA8rbOlZKPM:&tbnh=131&tbnw=127&prev=/images%3Fq%3Dsan%2Bdisk%2Bsansa%2Bview%26ndsp%3D20%26hl%3Den%26safe%3Doff%26clien 02.07.16 # t%3Dfirefox-a%26rls%3Dorg.mozilla:en-US:official%26sa%3DN%26start%3D20%26um%3D1 that 02.07.36 # sonar___: tinyurl.com 02.07.41 # sonar___: that second one you linked never actually came out, as far as I know. 02.07.47 # err http://www.slipperybrick.com/wp-content/uploads/2007/01/sandisk-sansa-view-player.jpg 02.08.00 # It wasn't discontinued so much as "a product prototype that never made it to production" 02.08.18 # oh really? 02.08.32 # so there is only one... 02.08.39 # sonar___: But anyway, being "based off" another DAP means that it's different - hence the e200 firmware won't work. 02.09.18 # a lot of the discussions about the sansa view and rockbox seem to be about the first model. 02.09.46 # sonar___: Not in the Rockbox forums. 02.10.54 # its not even based off, theres no common hardware, except for different models of AMS DACs 02.11.07 # its based off in the sense that its based off the iPod 02.11.18 # i.e. an mp3 player with a screen and a wheel 02.11.24 # ok. 02.11.42 # saratoga: I thought the View was the one using the PP/Nvidia chipset anyway? 02.11.58 # Llorean: yeah 02.12.32 # so do you know if anyone is working on a port? It'd be great if they were, but I'm not really leet enough to help. the user interface on this thing is terrible... so I'm hoping. 02.12.38 # Are there any plans for a release of Rockbox for Ipod Classic? 02.12.45 # curse: Plans are not made. 02.13.17 # curse: It's entirely volunteer work. We can't really know if anyone is still working on it, but so far no progress has been reported to us. 02.13.34 # sonar___: So far, nobody's reported significant progress 02.14.27 # I see the point, my question aimed to know if there was any 'reported source contribution' that could bring rockbox near to a release for it. 02.14.41 # Apparently, I'll have to stick with my current software. 02.15.12 # apparently I'll have to learn c and make it work on the sansa view. 02.17.55 # It'd be cool if there were a commercially available mp3 player that utilized open source firmware from the ground up... 02.18.37 Quit dfkt ("-= SysReset 2.53=- Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn.") 02.19.44 # I know C, but I'm already in enough projects that are a PITA 02.20.08 # you may want to chat on rockbox-community, not the on topic channel 02.20.42 Join sarixe [0] (n=sarixe@ool-43540968.dyn.optonline.net) 02.23.29 Join sarixe` [0] (n=sarixe@ool-43540968.dyn.optonline.net) 02.28.22 Quit sarixe (Nick collision from services.) 02.28.29 Nick sarixe` is now known as sarixe (n=sarixe@ool-43540968.dyn.optonline.net) 02.31.39 Quit yhuang_ ("Leaving") 02.32.45 Part curse 02.39.48 # sonar___, yea Llorean was right.. they never released that one.. it was only an idea 02.41.17 Quit efyx (Remote closed the connection) 02.43.55 *** Saving seen data "./dancer.seen" 02.46.02 Quit MethoS- (Remote closed the connection) 03.04.31 Join SUSaiyan [0] (n=SUSaiyan@cc84863-b.zwoll1.ov.home.nl) 03.07.17 Join perrikwp [0] (i=18ac0c41@gateway/web/ajax/mibbit.com/x-12cf29076da690d4) 03.12.59 Join psychohistory [0] (n=aceydawg@ppp-70-244-38-148.dsl.hstntx.swbell.net) 03.15.06 # Newb question. Can you use ipod+rockbox with car stereos? 03.16.33 # Maybe - it depends on what the car stereo does... 03.17.11 # Ok let me rephrase. If I'm looking to buy a car stereo that can use rockbox, what should I be looking for? 03.18.08 # I would look for something with a standard audio-in socket - not one that is designed specifically for ipods. You may not always have an ipod... 03.18.57 Quit taylor_ (Remote closed the connection) 03.18.58 # i would say look for the audio input or one that reads msc mode devices 03.19.46 # Alright. 03.20.37 # well I'll see where that takes me, thanks a lot. 03.21.03 # advcomp2019: A car stereo that reads msc mode devices would be limited to the audio formats it can play itself (and other features). You couldn't take advantage of Rockbox. 03.21.09 Quit timc`` (Remote closed the connection) 03.21.38 # ohh... yeah, I want to use rockbox so I can play lossless formats... 03.22.19 # linuxstb, yea but he was not 100% clear on that.. so yea you are right 03.22.37 # advcomp2019: Well, this is #rockbox ;) 03.23.18 # sorry, should have said. so.... 03.25.04 # from linuxstb's statement, I'm assuming the car stereo decodes the music, not the external player? 03.25.53 Join timc [0] (n=aoeu@124.93.243.83) 03.26.57 # psychohistory: In the case of ones where they treat the MP3 player as an HD, yes. 03.26.58 # psychohistory: In msc mode, yes. It will just treat the DAP as a hard disk and access the files directly. 03.27.08 # That's why you shouldn't look for USB connections, but rather just line-out / audio cable connections. 03.27.30 # ohh, gotcha. 03.28.56 Join akur [0] (n=akur@bl6-150-12.dsl.telepac.pt) 03.29.43 # ok, I think I have an idea now. I'll look for some standard audio-in connection and stay away from "msc mode" stereos. 03.30.34 # thanks for the help. 03.31.05 Part akur 03.34.59 Join DennisCollective [0] (n=sonar@adsl-69-107-3-12.dsl.pltn13.pacbell.net) 03.35.13 Join beta [0] (i=1000@d36-124-26.home1.cgocable.net) 03.35.29 Quit sonar___ (Read error: 113 (No route to host)) 03.36.02 Nick beta is now known as Beta2K (i=1000@d36-124-26.home1.cgocable.net) 03.37.58 # so.... is there any actual interest in my patch which fiddles with how the wps uses its RAM? 03.39.21 Join FlynDice [0] (n=FlynDice@206.82.218.132) 03.39.37 Quit midijunkie ("?(???~•~)?") 03.39.46 Join _lifeless [0] (n=lifeless@90.150.213.83) 03.41.04 Quit xSlack ("Ex-Chat") 03.41.24 Quit nuonguy ("Leaving") 03.43.33 # JdGordon: Is it actually useful yet? I haven't kept track. 03.43.44 Join xSlack [0] (n=brett@173-17-70-78.client.mchsi.com) 03.44.38 # Llorean: depends what you call useful... even the end goal doesnt really change much (from the users perspective)... right now its fubar and might need to be restarted 03.45.06 # I thought the end result would be, generally, more RAM available for the WPS without needing to increase the actual RAM used by Rockbox. 03.45.58 # yes 03.47.31 # I guess how much this affects users will depend on how inefficient we were before. 03.59.48 Quit fdinel ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 04.01.42 Quit DennisCollective (Read error: 110 (Connection timed out)) 04.03.44 Join DennisCollective [0] (n=sonar@c-67-169-92-39.hsd1.ca.comcast.net) 04.12.43 Quit Lss () 04.20.37 Join blkhawk- [0] (n=blkhawk@g226130133.adsl.alicedsl.de) 04.36.44 Quit blkhawk (Read error: 113 (No route to host)) 04.37.35 Nick blkhawk- is now known as blkhawk (n=blkhawk@g226130133.adsl.alicedsl.de) 04.43.59 *** Saving seen data "./dancer.seen" 04.47.07 Join xSlack_ [0] (n=brett@173-17-70-78.client.mchsi.com) 04.49.46 Quit miepchen^schlaf (Read error: 101 (Network is unreachable)) 04.54.08 Quit DennisCollective (Read error: 113 (No route to host)) 04.55.23 Join JdGordon_ [0] (n=jonno@c-98-203-252-78.hsd1.wa.comcast.net) 04.59.10 Part psychohistory 04.59.44 Join JdGordon__ [0] (n=jonno@c-98-203-252-78.hsd1.wa.comcast.net) 05.10.10 Quit JdGordon (Read error: 110 (Connection timed out)) 05.12.50 Quit JdGordon_ (Read error: 110 (Connection timed out)) 05.13.23 Nick JdGordon__ is now known as JdGordon (n=jonno@c-98-203-252-78.hsd1.wa.comcast.net) 05.21.10 Join lynn [0] (n=3a2160cc@gateway/web/cgi-irc/labb.contactor.se/x-2ec0fcbf6ca4a128) 05.21.46 Quit saratoga ("CGI:IRC (EOF)") 05.21.54 Quit lynn (Client Quit) 05.22.42 Quit BUMBACL0T () 05.23.01 Join BUMBACL0T [0] (n=ORF@unaffiliated/bumbacl0t) 05.24.55 Join DennisCollective [0] (n=sonar@adsl-69-107-99-48.dsl.pltn13.pacbell.net) 05.29.25 Quit Horschti ("Verlassend") 05.38.58 Nick fxb is now known as fxb__ (n=felixbru@h1252615.stratoserver.net) 05.41.08 Quit z35 ("Leaving") 05.44.49 Quit JdGordon (Remote closed the connection) 05.46.41 Join JdGordon [0] (n=Miranda@c-98-203-252-78.hsd1.wa.comcast.net) 05.47.34 Quit CaptainKewl (Read error: 110 (Connection timed out)) 05.55.35 Join planetbeing [0] (n=planetbe@c-71-236-164-204.hsd1.or.comcast.net) 06.01.48 Join gartral [0] (n=gareth@adsl-75-33-64-115.dsl.bcvloh.sbcglobal.net) 06.02.22 Part gartral 06.02.47 Quit kushalone ("Leaving. I cannot promise to be back but most likely will.") 06.04.19 Join JdGordon_ [0] (n=jonno@c-98-203-252-78.hsd1.wa.comcast.net) 06.10.06 Quit JdGordon (Read error: 110 (Connection timed out)) 06.18.17 Join Llorean1 [0] (n=DarkkOne@adsl-99-158-46-113.dsl.hstntx.sbcglobal.net) 06.18.38 Quit Llorean (Nick collision from services.) 06.18.52 Nick Llorean1 is now known as Llorean (n=DarkkOne@adsl-99-158-46-113.dsl.hstntx.sbcglobal.net) 06.23.45 Quit planetbeing () 06.26.16 Join homielowe [0] (n=homielow@unaffiliated/homielowe) 06.36.48 Quit StealthyXIIGer (Read error: 110 (Connection timed out)) 06.44.00 *** Saving seen data "./dancer.seen" 07.05.37 Quit Llorean (Read error: 104 (Connection reset by peer)) 07.05.55 Join Llorean [0] (n=DarkkOne@adsl-99-158-46-113.dsl.hstntx.sbcglobal.net) 07.08.29 Quit XavierGr () 07.18.45 Quit Aurix_Lexico (Remote closed the connection) 07.25.44 Join Harryp4 [0] (i=harryp44@59.98.222.197) 07.29.59 Part Harryp4 07.31.12 Join ender` [0] (i=krneki@foo.eternallybored.org) 07.39.13 Quit tyfoo ("Carpe diem") 08.05.45 Quit homielowe () 08.21.33 Join blkhawk- [0] (n=blkhawk@g226130133.adsl.alicedsl.de) 08.25.20 Join Zagor [242] (n=bjorn@rockbox/developer/Zagor) 08.37.14 Join wincent [0] (n=wincent@host-091-097-030-116.ewe-ip-backbone.de) 08.37.24 Quit blkhawk (Read error: 113 (No route to host)) 08.37.32 Nick blkhawk- is now known as blkhawk (n=blkhawk@g226130133.adsl.alicedsl.de) 08.41.12 Join nuonguy [0] (n=john@c-24-6-174-132.hsd1.ca.comcast.net) 08.41.54 Join Rob2222 [0] (n=Miranda@p4FDCD450.dip.t-dialin.net) 08.44.02 *** Saving seen data "./dancer.seen" 08.49.00 Join LinusN [0] (n=linus@rockbox/developer/LinusN) 08.50.52 Quit Seed ("cu, Andre") 08.52.52 Join petur [50] (n=petur@rockbox/developer/petur) 08.54.26 Join efyx [0] (n=efyx@lap34-1-82-224-140-171.fbx.proxad.net) 08.55.59 Quit DennisCollective (Read error: 110 (Connection timed out)) 08.59.31 Quit Rob2223 (Read error: 110 (Connection timed out)) 09.02.59 Join R31D [0] (n=email@hlfxns01bbf-142177228071.pppoe-dynamic.ns.aliant.net) 09.05.14 Join Bagderr [241] (n=daniel@rockbox/developer/bagder) 09.08.10 Quit avis (Read error: 104 (Connection reset by peer)) 09.10.04 Nick Bagderr is now known as B4gder (n=daniel@rockbox/developer/bagder) 09.15.26 Join jordoex_ [0] (n=quassel@d154-20-29-131.bchsia.telus.net) 09.16.47 Quit jordoex_ (Remote closed the connection) 09.21.20 Quit jordoex (Read error: 110 (Connection timed out)) 09.21.50 Join stripwax [0] (n=Miranda@87-194-34-169.bethere.co.uk) 09.31.28 Join Thundercloud [0] (i=thunderc@persistence.flat.devzero.co.uk) 09.37.14 Join robin0800 [0] (n=quassel@cpc3-brig8-0-0-cust436.brig.cable.ntl.com) 09.38.23 # is FS#10026 - E200: Improve USB detection in WinXP applicable to c200's ? 09.42.05 # If there's no comment on the task, then we don't know. 09.47.30 Join n1s [0] (n=n1s@rockbox/developer/n1s) 09.50.19 # do people think FS#10018 should go in before the release? I can whip up a batch of bootloaders that this affects for testing tonight if so 09.51.01 # it is a bugfix for the c200 at least, maybe not high priority 09.51.37 Quit Thundercloud (Remote closed the connection) 10.01.01 Quit midgey () 10.13.26 # robin0800 - gevaerts was looking at running #10026 on all pp targets iirc to confirm if there's any change/improvement in behaviour for all targets running that code 10.13.39 Quit stripwax (Read error: 131 (Connection reset by peer)) 10.13.49 Join pyro_maniac [0] (i=foobar@p57BBA7EF.dip0.t-ipconnect.de) 10.26.53 # n1s: I think so yes - failure to properly install the main build isn't uncommon, especially as that's a known bug in rbutil (on OSX) 10.27.56 # linuxstb: ok, e200, c200 and the h10's are the only release targets using the general pp bootloader, right? 10.28.26 # mrobe100? 10.28.40 # "release targets" 10.28.49 Join AndyIL [0] (i=AndyI@212.14.205.32) 10.28.56 # yes :) 10.28.56 # Ah, we support that? ;) 10.29.12 # * linuxstb thinks we have too many targets now... 10.29.22 Quit AndyI (Read error: 60 (Operation timed out)) 10.29.53 Join wincent_balin [0] (n=wincent@host-091-097-030-116.ewe-ip-backbone.de) 10.30.10 # then i expect the mrobe to have the same bug as the c200 and that should be fixed by this too 10.30.54 # linuxstb: We even have an Olympus installation/removal section of the forums. 10.31.13 # Three whole people have started threads there. 10.31.36 # so all three users started their own threads! ;-P 10.31.55 # B4gder: You can't claim that until we have download mirror stats..... ;) 10.32.13 # that'll only prove that those three users download releases often! 10.32.38 # And from randomly different parts of the internet... 10.32.47 # sneaky persons! 10.33.18 # That's assuming there is at least 3 downloads... 10.34.08 # 100 downloads from build.rockbox.org during March 10.34.19 # that probably doesn't include the at least four developers (I know of) 10.35.04 # recorderv2 13 downloads 10.35.58 # ondiosp is at 13 too 10.36.07 # Those are probably still all on 2.5 10.37.26 # yeah, starting with 3.0 and our new release schedule the look of the build download stats changed as now I think they are more clearly "bleeding edge" people than before 10.37.50 # cowond2 164 downloads 10.39.31 # "It doesn't work, but it's more popular than the Archoses combined!" :) 10.40.10 # ... from the build server 10.44.04 *** Saving seen data "./dancer.seen" 10.45.08 Quit wincent (Read error: 110 (Connection timed out)) 10.50.14 Part wincent_balin ("Kopete 0.12.7 : http://kopete.kde.org") 10.50.23 Join wincent_balin [0] (n=wincent@host-091-097-030-116.ewe-ip-backbone.de) 10.57.29 # * gevaerts points Llorean to FS#10011 10.58.06 Join xandra20_ [0] (n=xandra20@pD95191E9.dip0.t-ipconnect.de) 10.58.24 # hallo 10.58.35 Quit xandra20_ () 11.03.51 Quit robin0800 (Read error: 104 (Connection reset by peer)) 11.05.16 Join PaulJam [0] (n=PaulJam_@p54BEDE54.dip.t-dialin.net) 11.16.19 # hi, is compiling rockbox on cygwin broken again? I'm getting a lot of errors in settings_list.c. 11.19.30 # if it is, you're the first to mention it 11.20.52 # PaulJam: tried the usual make clean and reconfigure, etc? and if you haven't built for a while a semi recent change needs manual cleaning of the build dir 11.21.29 # ok, i'll try that 11.24.40 # thank you, deleting the build dir helped. 11.29.34 Join pondlife [50] (n=Steve@rockbox/developer/pondlife) 11.40.25 Join moos [0] (i=Mustapha@rockbox/staff/moos) 11.42.07 Join bubsy [0] (i=Bubsy@81-31-244-19.net.nc-systems.no) 11.44.51 Quit dmb (Read error: 113 (No route to host)) 11.47.45 Join LambdaCalculus37 [0] (n=rmenes@rockbox/staff/LambdaCalculus37) 11.57.35 # Is it normal for a simulator to have to rebuild dircache on every launch? 11.57.46 # I'd not noticed it in the past 12.00.02 # Happens every time now though 12.01.36 Quit LambdaCalculus37 ("Fwump") 12.03.46 Nick fxb__ is now known as fxb (n=felixbru@h1252615.stratoserver.net) 12.07.28 Join Lss [0] (n=Lss@cm246.delta91.maxonline.com.sg) 12.08.17 Quit Lss (Client Quit) 12.12.44 Join Lss [0] (n=Lss@cm246.delta91.maxonline.com.sg) 12.15.11 Quit Lss (Read error: 104 (Connection reset by peer)) 12.15.34 Join Lss [0] (n=Lss@cm246.delta91.maxonline.com.sg) 12.21.00 Part sir_yodle1 12.33.43 Join midijunkie [0] (n=Miranda@pD954721F.dip0.t-ipconnect.de) 12.35.49 Join robin0800 [0] (n=quassel@cpc3-brig8-0-0-cust436.brig.cable.ntl.com) 12.44.08 *** Saving seen data "./dancer.seen" 12.50.01 Join Casainho [0] (n=chatzill@bl8-155-233.dsl.telepac.pt) 12.50.12 # hello :-) 12.50.55 # I am getting this message "Codec failure" when I try to play files, on Lyre project. Can someone tell me why it happens? can it be because of bad reading of audio files? 12.51.13 # I tried an OGG and MP3 file, with the same result. 12.51.14 # no, it's something wrong with your codec build 12.51.39 # B4gder: ah, because I can clear see the name of files, directories, etc.... 12.52.04 # B4gder: so, where can I look, to discover where I have problems on codecs? 12.52.17 # first make sure you do a full build and install 12.52.26 # then check the codec loader and see why it complains 12.52.55 # a full build is choosing "Normal" and after "make bin", right? 12.53.06 # don't do make bin 12.53.12 # and I am uploading an .elf file, with the JTAG debugger... 12.53.19 # run 'make' 'make zip' and then unzip 12.53.42 Quit jhMikeS (Nick collision from services.) 12.53.48 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 12.53.57 # you can run it however you want, but the codecs must "match" the main binary 12.54.05 # I'm having a compile issue too - having added a new LANG_ to english.lang, I don't get it added to lang.h by a make. 12.54.22 # ! 12.54.56 # B4gder: so, make bin is for what? it don't build the codecs? 12.55.19 # Is lang.h meant to be rebuilt? I'm sure it used to work... 12.56.00 # Casainho: 'make help' is useful 12.56.15 # pondlife: it gets generated in the build 12.56.19 # okok - thanks :-9 12.56.22 # must go now :-) 12.56.23 Quit Casainho ("ChatZilla 0.9.84 [Firefox 3.0.7/2009021910]") 12.56.37 # B4gder: Not here it doesn't ;) 12.56.53 # that sounds like a makefile flaw 12.56.57 # I did a make reconf and make clean, but no new lang.h 12.57.17 # didn't make clean remove it? 12.57.50 # lang.h in the build dir? 12.57.58 # yes 12.58.08 # No, it remains after make clean 12.58.18 # ok, then remove it manually 12.58.28 # is it an old one/ when did you last built there? 12.58.43 # build too 12.59.09 # It is an old one... I guess it should not be there at all, only in build/lang/lang.h... 13.00.39 # Nope - having deleted it, I now get "make: *** No rule to make target `/home/Steve/rockbox/build/lang.h', needed by `/home/Steve/rockbox/build/apps/action.o'" 13.00.42 # the file got moved semi recently, causing make clean to not remove the old one (only cleaning in the new place) 13.01.15 # That's what I'm seeing, but something (here) is still looking for the old file, I think. 13.01.19 # i.e. in the old location 13.02.34 # Just done a make veryclean, will see if that helps 13.04.18 # Yes, looks better now - I just needed to delete the rogue lang.h and make from clean. 13.05.16 Join einhirn [0] (n=Miranda@p4FC60C48.dip0.t-ipconnect.de) 13.10.00 Join Darksair [0] (n=user@125.33.199.50) 13.14.10 Join barrywardell [0] (n=barry@barry-workstation.ucd.ie) 13.17.37 Quit byteframe (Read error: 110 (Connection timed out)) 13.17.51 Join byteframe [0] (n=bytefram@pool-71-174-15-60.bstnma.east.verizon.net) 13.21.21 Join LambdaCalculus37 [0] (n=44a04303@rockbox/staff/LambdaCalculus37) 13.36.51 # Today is supposed to be branching day in preparation for 3.2, right? 13.44.01 Quit deweycooter (Read error: 110 (Connection timed out)) 13.50.32 Quit FlynDice (Remote closed the connection) 13.58.21 Part LinusN 13.59.54 Join CaptainKewl [0] (i=jds@207-237-172-77.c3-0.nyr-ubr4.nyr.ny.cable.rcn.com) 14.00.22 Join The-Compiler [0] (n=compiler@the-compiler.org) 14.02.55 Join pbxy [0] (n=pbxy@89.163.145.9.static.rdns-uclo.net) 14.09.21 Join daurn| [0] (n=daurnima@ppp118-208-164-190.lns10.mel4.internode.on.net) 14.16.46 Quit daurn (Read error: 60 (Operation timed out)) 14.19.48 Join obo [0] (n=obo@77-99-230-49.cable.ubr04.trow.blueyonder.co.uk) 14.22.39 Join Casainho [0] (n=chatzill@bl8-155-233.dsl.telepac.pt) 14.27.14 Join kushalone [0] (n=kushal@12.169.180.178) 14.27.39 Join {phoenix} [0] (n=dirk@p54B45BCE.dip.t-dialin.net) 14.29.02 Quit kushalone (Client Quit) 14.39.57 Join avis [0] (n=ident@pdpc/supporter/student/avis) 14.44.09 *** Saving seen data "./dancer.seen" 14.46.31 Quit PaulJam (".") 14.47.56 Join kugel [0] (n=kugel@rockbox/developer/kugel) 14.50.07 Join Casainho_ [0] (n=chatzill@bl8-165-30.dsl.telepac.pt) 14.50.25 Quit midijunkie ("?(???~•~)?") 14.50.28 Quit Casainho_ (Client Quit) 14.51.25 # freeze is over? :) 14.51.56 # not yet 14.53.41 # gevaerts: patch for FS10026? 14.54.10 Quit CaptainKewl (Read error: 110 (Connection timed out)) 14.57.30 # I ran some errants today at lunch, and my sansa just suddenly died 14.57.35 # robin0800: is adding the line shown at the place indicated really that hard? 14.57.49 # pitch black, had to do the 15 seconds menu-press to shut off for real 14.58.18 # but I must admit it isn't fully up-to-date 15.00.08 # B4gder: any idea when you'll do the 3.2 branch? 15.00.18 # I've noticed now that if I suddely get a data abort on my beast, it'll shut off after a few seconds and allow me to restart it without having to resort to the battery switch. 15.03.03 # gevaerts: yes for me unless you can tell me how? 15.04.32 # robin0800: grab a text editor, open the file toni mentioned, go to the line toni mentioned and insert. It's easy 15.05.38 Join StealthyXIIGer [0] (n=stealthy@c-68-62-18-116.hsd1.mi.comcast.net) 15.05.38 # kugel: You sure mine refused to open in a text file? 15.07.30 Join evilnick [0] (i=0c140464@gateway/web/ajax/mibbit.com/x-70b5c0ef6e45b1e0) 15.07.36 Quit Casainho (Read error: 110 (Connection timed out)) 15.08.49 # kugel: and for c200 possibly not right if the comment there is correct? 15.09.34 Quit kugel (Nick collision from services.) 15.09.38 Join kugel [0] (n=kugel@rockbox/developer/kugel) 15.13.06 # B4gder: I take it as a "no"? :) 15.13.28 Quit einhirn (Read error: 104 (Connection reset by peer)) 15.17.35 Join jaykay [0] (n=chatzill@p579E6A36.dip.t-dialin.net) 15.20.10 # if you search the bug tracker for wma, you get 5 results, of which 1 and 3-5 are problems with low-bitrate wma files 15.20.23 # i suggest them all except one for closing 15.25.42 Quit freqmod_qu (Read error: 131 (Connection reset by peer)) 15.27.50 Join freqmod_qu [0] (i=quasselg@dhcp208-240.ed.ntnu.no) 15.33.56 # kugel: changed the file used the comment value what do I do now? 15.35.01 # compile rockbox? 15.36.34 # kugel: Do you mean re-run the script or use make? 15.37.29 # * pondlife calls all timestretch testers to assemble at http://www.rockbox.org/tracker/task/8894 ;) 15.43.54 Join tyfoo [0] (n=tyfoo@77-20-31-238-dynip.superkabel.de) 15.53.35 Join jgarvey [0] (n=jgarvey@cpe-098-026-065-013.nc.res.rr.com) 15.56.03 Join toffe82 [0] (n=chatzill@74.0.180.178) 16.13.04 Join dfkt [0] (i=dfkt@unaffiliated/dfkt) 16.14.01 Quit avis (Remote closed the connection) 16.15.19 Join dmb [0] (n=dmb@unaffiliated/dmb) 16.30.08 # shouldn't we create a ReleaseNotes32 page and fill it with infos? 16.32.12 # we should! 16.32.29 # Who wants to do the honors? 16.32.32 # * rasher is on it! 16.33.52 # I was about to create (after searching 5 min how to create a page), but then I decided to ask first ;) 16.37.08 # * kugel wonders when we'll take rockbox out of the freezer 16.37.20 # How do you feel about switching the credits part to "new contributors since 3.1"? 16.39.27 Join bmbl [0] (n=Miranda@unaffiliated/bmbl) 16.42.23 # kugel: no improvement in Gnome detection is the comment for FS 10026 correct? 16.43.35 # http://www.rockbox.org/twiki/bin/view/Main/ReleaseNotes32 16.44.13 *** Saving seen data "./dancer.seen" 16.44.13 # Time to make Zagor produce a "closed tasks in FS since 3.1" page again 16.49.24 Join Chex [0] (n=Stefan@bas1-montreal48-1176173096.dsl.bell.ca) 16.57.15 Quit Zagor ("Don't panic") 17.04.17 Join Tuplanolla [0] (n=jani@unaffiliated/tuplanolla) 17.04.30 # helloes 17.05.16 # is it possible to modify the statusbar from wps? 17.06.13 # the statusbar in the menus? no 17.07.27 # yeah. thanks. 17.09.02 Join yhuang [0] (n=yhuang@unaffiliated/yhuang) 17.10.23 Nick JdGordon_ is now known as JdGordon (n=jonno@rockbox/developer/JdGordon) 17.11.27 Join avis [0] (n=ident@pdpc/supporter/student/avis) 17.12.35 Nick HBK- is now known as HBK (n=hbk@pool-71-96-74-73.dfw.dsl-w.verizon.net) 17.17.20 # * kugel whistles quickscreen 17.17.42 Join Ubuntuxer [0] (n=johannes@dslb-094-220-228-203.pools.arcor-ip.net) 17.18.08 # JdGordon: it is possible, using the quickscreen 17.18.41 # what? 17.18.55 # the only thing you can change is the volume and battery display 17.18.57 # modify menu statusbars 17.19.04 Join GodEater [0] (n=ge@rockbox/staff/GodEater) 17.19.18 # modifying, as in enabling or disabling, of course 17.19.26 Join bertrik [0] (n=bertrik@ip117-49-211-87.adsl2.static.versatel.nl) 17.19.28 # You can't *modify* the statusbar. You can enable or disable it... not really the same. 17.21.13 Quit tyfoo (Read error: 104 (Connection reset by peer)) 17.23.53 Join z35 [0] (n=z35@h213.59.90.75.dynamic.ip.windstream.net) 17.25.19 # Which bitmap target has the smallest screen? 17.25.32 # Ondio? Or is it one of the remotes? 17.25.51 Quit GodEater ("Don't follow me") 17.26.09 # smallest as in physical or pixels? 17.26.17 # Pixels 17.26.44 # Or - on what target is the pitch screen most cramped..? :) 17.26.59 # Archoses 17.28.04 # does the simulator require the sdl mixer libs for compiling? 17.28.54 # PSPdemon: only libsdl, and the developement version 17.29.20 # thanks 17.29.30 # PSPdemon: what os are you on? 17.29.36 # ubuntu 17.29.39 # just was curious 17.29.54 # then, just do "sudo apt-get install libsdl1.2-dev" and you're done 17.29.57 Join planetbeing [0] (n=planetbe@c-71-236-164-204.hsd1.or.comcast.net) 17.30.01 # heh 17.36.28 Quit kugel ("ChatZilla 0.9.84-rdmsoft [XULRunner 1.9.0.7/2009030516]") 17.39.55 Nick JdGordon| is now known as JdGordon|w (i=836b0055@gateway/web/ajax/mibbit.com/x-ca84230bccdae510) 17.43.59 Quit Ubuntuxer ("Leaving.") 17.47.59 Join bs66_ [0] (n=sysuser@95.209.57.183) 17.48.11 # hmm 17.48.34 # i tried to run doom in the simulator but it says that im missing base wad? 17.49.13 # * pixelma wonders whether the pictureflow "input" fix will make it into SVN before the release 17.49.55 # reminds me that I should try it... 17.50.19 Join kugel [0] (n=kugel@rockbox/developer/kugel) 17.51.07 # PSPdemon: Did you add rockdoom.wad to .rockbox/doom in the simdisk folder? 17.58.09 Quit yhuang (Read error: 110 (Connection timed out)) 17.59.34 Part B4gder 18.01.11 Join Ubuntuxer [0] (n=johannes@dslb-094-220-228-203.pools.arcor-ip.net) 18.01.59 Quit flux (Read error: 104 (Connection reset by peer)) 18.02.07 Join flux [0] (i=flux@jolt.modeemi.cs.tut.fi) 18.02.22 # has anyone tried patching OF version 1.1.32 for the sansa clip? 18.02.41 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is) 18.03.02 # LambdaCalculus37, yes i did 18.03.09 # and doom + doom2 18.03.23 # ( and a few iwads/pwads for debugging my modifications on ) 18.03.44 Quit lymeca (SendQ exceeded) 18.04.08 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is) 18.05.11 Quit lymeca (SendQ exceeded) 18.05.48 # bertrik: I haven't. Want to be a daring man today? :) 18.06.31 # pondlife: many problems 18.06.54 # pixelma: i'm only looked closely at c200 and ondio keymaps in that, and the beast and e200, since i own those. they may still be broken on other targets. 18.07.04 # I won't mind trying it 18.07.09 # kugel: I'm about to leave, please list them on Flyspray.. 18.07.16 # ok 18.07.24 # :/ 18.07.30 Join clerk39 [0] (n=best@dslb-082-083-069-206.pools.arcor-ip.net) 18.07.31 # LambdaCalculus37, would be a waste if someone else already tried it 18.07.38 # hi 18.08.02 # >_< 18.08.16 # why wont it load rockdoom >_< 18.08.27 Quit petur ("work->home") 18.08.31 # LambdaCalculus37, I'll try sometime later this evening and share here what happened 18.08.37 Join CaptainKewl [0] (i=2669ecc2@gateway/web/ajax/mibbit.com/x-e54843cb22aea368) 18.08.57 # I just installed rockbox on my ipod video 5.5 - which was fantastically easy with the installer. now I copied music onto it - the ipod loaded the old apple firmware for that - and now ..rockbox won't load anymore - what am I doing wrong? 18.09.10 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is) 18.09.13 # pondlife: pitchcorrection is nice though ;) 18.09.32 # bertrik: Okay. 18.09.53 # can't find info on the rockbox page either :/ 18.10.47 # is it documented somewhere maybe? 18.11.48 # clerk39: You need to hold MENU+SELECT to force the Apple firmware to reboot (it normally just sleeps) 18.12.22 # thanks 18.12.33 Quit z35 ("Leaving") 18.12.47 Quit planetbeing () 18.12.56 # weh 18.13.11 # this timestrech is so cool, that needs to go in soon 18.14.28 # I was wondering about something for the manual. Since some DAPs have system folders (e.g. Gigabeat F/X) hidden by default, some OSes like Mac OS X will not display them by default, unless you enter a complicated command in the Terminal. 18.14.50 # There's a Dashboard widget, though, that will simply kill and relaunch the Finder with hidden files and folders exposed. 18.15.09 # Would anyone have any objections if I were to add a link to this Widget in the manual? 18.15.53 # Unhelpful: ping 18.17.30 Quit clerk39 () 18.17.32 Join miepchen^schlaf [0] (n=miepel@p579ECA9C.dip.t-dialin.net) 18.18.04 # LambdaCalculus37: "ls -al" is complicated? Where in the manual would you put that info though? 18.19.19 # linuxstb: There are people that don't know the Terminal whatsoever. And an example of where to put it would be here: http://download.rockbox.org/manual/rockbox-gigabeatf/rockbox-buildch2.html#x4-110002.2.2 18.22.04 # kugel: can't chat, but i can get back to you later 18.28.00 # LambdaCalculus, i copied my doom folder from my sansa to the same placement as the simdisk 18.28.17 # ( or rather same directory structure ) 18.28.20 # still no go :/ 18.30.36 # Unhelpful: I didn't want to chat, I just wanted to suggest closing http://www.rockbox.org/tracker/task/9726 as fixed 18.32.03 Join MethoS- [0] (n=lem@host-091-097-240-149.ewe-ip-backbone.de) 18.32.11 # Okay, I have iTunes seeing the main memory of my e280 now. And things more or less work. A few things: 1) Once in a while a second ipod shows up, which iTunes think is corrupted. 2) I can't copy/sync AAC files - I'm told my iPod doesn't support it. Though that might be my fault. 18.32.33 Part pyro_maniac ("Leaving.") 18.32.54 Join domonoky [0] (n=Domonoky@rockbox/developer/domonoky) 18.33.00 # The first point doesn't actually cause any harm. It's just a bit weird. 18.34.27 # What's the point of faking an iPod btw? Wouldn't you need the iTunesDB on the device too? 18.34.51 # dionoea: The point, I guess, is to use iTunes for syncing. 18.35.04 Join flydutch [0] (n=flydutch@host238-166-dynamic.15-87-r.retail.telecomitalia.it) 18.35.19 # but won't that do it the iPod way? ie with the DB and random filenames 18.35.19 # Didn't someone also say that their xbox 360 no longer recognises their ipod? 18.35.19 Quit robin0800 (Read error: 104 (Connection reset by peer)) 18.35.26 # dionoea: Yes. 18.35.48 # dionoea: but if you use the Rockbox database, that won't really matter anyway 18.35.56 # fair enough 18.36.21 # linuxstb: Yes, on the mailing list 18.38.24 # dionoea: This would basically be useful for people who want much of the same usage pattern as on an ipod. 18.39.42 # Ok. I guess that iTunes can't sync to non Apple devices ... that's bad :) 18.40.07 # dionoea: Not unless they act like an Ipod! 18.40.13 # hehe :) 18.40.33 # But yeah, it's a bit odd considering that many players would play music bought in the ITMS 18.40.38 # You'll just need to add embeded album art support and you'll be able to fake the iPod OF on a rockboxed iPod 18.40.45 # ultimate usefulness 18.43.02 # Well the album art is stored separately also 18.44.16 *** Saving seen data "./dancer.seen" 18.45.15 # dionoea: because we can! :) 18.48.52 Quit moos ("Rockbox rules the DAP world") 18.48.58 # :/ 18.49.11 # i need help with the simulator 18.49.44 # short question; "TOUCHSCREEN_POINT" is the only button on Touchsreen, isn't it? 18.50.01 # i have compiled the simulator no problems....and the simulator runs 18.50.28 # but i cant get doom to work...and when i load the simulator and browse the "files" section it has nothing there 18.50.44 # even though that simdisk has .rockbox in it 18.51.10 # The Rockbox file browser doesn't show hidden files by default (files starting with "." are considered hidden) 18.51.32 # You need to change the "show files" option to "all". But what error does Doom give when you run it? 18.51.39 Join Seed [0] (n=ben@bzq-84-108-232-45.cablep.bezeqint.net) 18.52.20 # linuxstb: My Xbox 360 doesn't recognize any of my iPods in Rockbox USB mode. 18.52.24 # that it cant find base wad 18.52.45 # Strangely, my Archos, H340, and Gigabeat F work. 18.52.46 # And have you put the wad in the right place? 18.52.53 # yea 18.53.12 # and have doom/doom2 plus a few addon wads 18.54.58 Part Ubuntuxer 18.55.00 # okay i now see the .rockbox directory 18.55.16 # thanks for telling me about the "show all" option 18.55.30 # but even so it says it still cant find the base wad :/ 18.57.00 # PSPdemon: The files are in /.rockbox/doom/ ? 18.57.19 # You need rockdoom.wad, but the game wad 18.57.58 # yes 18.58.06 # doom.wad and doom2.wad are there as well 18.58.09 # gevaerts: Making sure the SD slot doesn't identify as "iPod" helps as well... 18.58.59 # .rockbox/doom/rockdoom.wad 18.59.04 # .rockbox/doom/Doom.wad 18.59.09 # .rockbox/doom/DOOM2.wad 19.01.17 # again..i just copied it out of my sansa with the same filestructure into the simulator 19.03.46 Quit jhMikeS (Nick collision from services.) 19.03.52 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 19.04.55 # PSPdemon: Are you on Linux? 19.05.09 # linuxstb, yes 19.05.31 # Try renaming to lower-case - i.e. doom.wad or doom2.wad 19.05.43 # (I don't know if the sim simulates case-insensitivity...) 19.05.45 # k 19.06.13 # linuxstb: I doubt it 19.09.30 # worked 19.09.30 # lol 19.11.44 Join tyfoo [0] (n=tyfoo@77-20-31-238-dynip.superkabel.de) 19.13.32 # linuxstb, works now thanks :D 19.16.19 # * n1s wants testers for FS#10018, anyone with e200 h10(big or small) or mrobe 100 around? 19.16.38 # e2 here 19.17.18 Join Conic [0] (n=conicpp@c-75-68-165-66.hsd1.vt.comcast.net) 19.17.31 # PSPdemon: do you want to test the patch? 19.18.18 # * PSPdemon checks what FS#10018 is 19.18.49 # ohhh 19.18.55 # i was looking at that acually 19.19.56 # kinda busy though...need to finish a few things before i can test 19.20.43 # n1s: is 5 seconds enough? 19.20.54 Join Horscht [0] (n=Horscht@xbmc/user/horscht) 19.21.19 # interesting... 19.21.26 # anyway thanks for the rockdoom help 19.21.48 # rasher: dunno, it's easy to extend 19.21.51 # itll help me fix up these errors easier now that i can read what ones are causing the errors :P 19.22.51 # kugel: I'm back, for a short while... what were your problems? 19.23.15 # rasher: do you think it should be longer? 19.23.54 # pondlife: data aborts sometimes, pressing select in pitch view resets speed too, sim (64bit) segfaults entirely 19.24.15 # Select is meant to reset speed 19.24.22 Join Nico_P [50] (n=nicolas@rockbox/developer/NicoP) 19.24.49 # For the other issues, please can you check which .patch file they started with? 19.24.54 # if you set speed, then you go into pitch view, select resets the speed too. 19.25.08 Quit jhMikeS (Read error: 110 (Connection timed out)) 19.25.11 # Yes, that's intentional. 19.25.19 # why? 19.25.33 Join stripwax [0] (n=Miranda@87-194-34-169.bethere.co.uk) 19.25.37 # Select just means "reset normal pitch and speed" 19.25.45 Quit stripwax (Client Quit) 19.25.47 # I think it should depend on in which view you are 19.26.13 # I don't want to distinguish the modes any more than we need to, so I disagree, I think.. 19.26.21 # But, it's not a biggie 19.26.33 # yea, but the other problems are 19.26.38 # Indeed 19.26.39 # I don't really understand them, though 19.26.50 # gdb shows segfaults in buffering.c 19.27.16 # line 363, specifically 19.27.37 # Sorry, I don't have source ATM 19.27.57 # also, looking at td speed, I'm far from understanding all the different data types, it seems to use int, int32_t, long long rather randomly 19.28.22 # I've not got into that much 19.28.35 # I suspected long long could be a problem on 64bit, but changing it didn't really help 19.28.38 # Could you see if the older patches work better? 19.28.47 # sure 19.29.03 # _090305 was ok, I think. 19.29.19 # btw, for special factors, speeding up sounds very nice 19.29.51 Join midijunkie [0] (n=Miranda@pD954721F.dip0.t-ipconnect.de) 19.30.05 # very nice compared to the non-special factors, of course. It cannot exactly match the normal speed quality but it's not too far away 19.30.43 # If you use pitch up/down in the timescale mode, it attempts to keep the speed constant. Works on my sim, but not tried it elsewhere - do you know if that worked? 19.31.08 Quit Darksair ("To Arch or Gentoo? That is the question...") 19.31.18 # I assume that speed * pitch should be constant, but no idea if they're accurate enough. 19.32.22 # yea, that worked quite good on the sansa 19.32.51 # a minor issue though is, that pitch is applied instantly, but speed not (so it won't be balanced out until you stop changing the values) 19.33.00 # Indeed 19.33.26 Join Strife89 [0] (n=michael@204.116.244.200) 19.33.51 # Not sure if low latency mode could help - would probably just cause dropouts 19.33.52 # _090305 is bad too 19.34.11 Join MethoS-- [0] (n=lem@host-091-097-242-138.ewe-ip-backbone.de) 19.34.18 # Phew! ;) 19.34.39 # phew? it just segfaults 19.34.54 # That means my recent work didn't break it.. 19.35.11 # I'm more interested in the data aborts 19.35.17 # * bertrik prepares to write a sansa clip bootloader based on OF version 1.1.32 19.35.33 # The 64-bit sim issue is probably on all versions 19.36.17 # eh, I think I see the long long things. It tries to do 32x32=64 bit math (not sure if that works) 19.37.37 # bertrik: is that version special? for earlier versions it was just a matter of adding the md5 to mkamsboot 19.38.13 # no, it's not special and it doesn't seem necessary to add the md5 to mkamsboot 19.38.38 # who's "it"? 19.38.42 # it's just that nobody has tried it yet so far, as far as I know 19.39.02 # ah, I understand 19.39.28 # the md5 is for identifying the version, and I think mkamsboot fails if the version cannot be identified 19.40.11 Quit MethoS- (Read error: 60 (Operation timed out)) 19.40.26 # it reads the model from the header if the md5 is unknown 19.41.17 # mkamsboot does identify it as Clip 19.42.48 Quit MethoS-- (Read error: 145 (Connection timed out)) 19.43.38 # yay, it worked 19.43.47 Quit Nico_P (Remote closed the connection) 19.48.11 Join perrikwp|class [0] (i=98214b73@gateway/web/ajax/mibbit.com/x-cfcc368b11e42683) 19.48.25 Quit perrikwp|class (Client Quit) 19.49.21 Join kperri [0] (i=98214b73@gateway/web/ajax/mibbit.com/x-ccb5d4b0978388f2) 19.50.41 Quit Strife89 ("Gotta go.") 19.51.41 # ok, since it works, I'm adding the md5 to mkamsboot 19.51.48 # bertrik: \o/ 19.59.25 Join Lear [0] (i=chatzill@rockbox/developer/lear) 20.02.11 Join Thundercloud [0] (i=thunderc@persistence.flat.devzero.co.uk) 20.04.22 Quit kugel ("ChatZilla 0.9.84-rdmsoft [XULRunner 1.9/2009020407]") 20.04.25 Join toffe82_ [0] (n=chatzill@74.0.180.178) 20.06.49 Quit blithe ("Lost terminal") 20.07.00 Join blithe [0] (n=blithe@blakesmith.me) 20.10.47 # so wait....what does it mean when you say that mkamsboot identifies the clip? 20.12.20 # i guess that means the clip is able to boot? 20.14.44 Join bluebrother [0] (n=dom@rockbox/developer/bluebrother) 20.15.38 Join planetbeing [0] (n=planetbe@c-71-236-164-204.hsd1.or.comcast.net) 20.16.13 Quit planetbeing (Client Quit) 20.16.33 Quit toffe82 (Read error: 110 (Connection timed out)) 20.16.49 # PSPdemon, yes, mkamsboot correctly identified the new 1.1.32 original firmware file as a clip firmware and successfully patched it. I verified that it can still boot the OF and rockbox with it. 20.17.06 # ahhh 20.21.04 Quit midijunkie ("?(???~•~)?") 20.22.37 Quit barrywardell (Remote closed the connection) 20.24.21 Quit kperri ("http://www.mibbit.com ajax IRC Client") 20.27.41 Join nibbler [0] (n=Nibbler@pD9E31806.dip.t-dialin.net) 20.33.21 Join casainho [0] (n=chatzill@87.196.63.213) 20.33.30 # hello :-) 20.33.41 Join faemir [0] (n=daniel@88-106-169-118.dynamic.dsl.as9105.com) 20.33.49 # while trying build with "make zip", I get the following error: cat: /home/cas/Documentos/rockbox_player/rockbox/build_firmware/apps/features: No such file or directory 20.34.28 # it buils ok if I do "make bin" 20.34.38 # what I am doing incorrectly? 20.35.15 # make zip and make bin are completely different 20.35.33 # run 'make V=1 zip' to see the full commands that fail 20.36.01 Join Aurix_Lexico [0] (n=comrade@c-68-56-205-239.hsd1.fl.comcast.net) 20.36.06 # it sounds like the features.txt processing somehow has problems 20.37.14 Join yhuang [0] (n=yhuang@c-68-84-62-252.hsd1.nj.comcast.net) 20.37.19 # over here: http://pastebin.com/m39359998 20.39.04 # do a make clean and make V=1, then check the command that creates the features file 20.40.17 # oh, did you do make bin first and then make zip? 20.41.25 # http://pastebin.com/m279ca622 20.42.02 Join Geno_ [0] (n=Geno@69.177.2.153) 20.42.13 # quick question 20.42.36 # does any build work on the classic yet? 20.42.36 # casainho: ? 20.42.49 # Geno_: No. 20.42.49 # Geno_: no, and it's not likely to do anytime soon 20.43.01 # Bagder: sorry, I was on phone. No, I just did "make zip" 20.43.21 Part pondlife 20.43.43 # are there any other firmwares that would work on the classic? 20.43.57 # You can't build a zip without a normal build first. 20.43.58 # None. 20.44.05 # Geno_: Not to my knowledge and they would be offtopic for Rockbox anyway. 20.44.17 *** Saving seen data "./dancer.seen" 20.44.41 # i suppose i just need to stick with ds/wii/computer emus then 20.44.43 # ah well 20.46.22 Part Geno_ 20.50.13 Join LinusN [0] (n=linus@rockbox/developer/LinusN) 20.53.22 # hey LinusN, you probably missed adding the path for the mipsel compiler in your acbuild.pl for rbclient 20.53.34 # oops 20.53.41 # I am getting a message on LCD: "Codec failure"... does anyone knows why? 20.53.53 # I remembered that now, I disabled that on your host the other day 20.54.00 # casainho: still the reason I said before 20.54.02 # Bagder: I was trying do make zip for avoid that error 20.54.15 # casainho: and you did a full 'make' first? 20.54.31 # and then you load _that_ rockbox image to your target? 20.54.32 Join petur [50] (n=petur@rockbox/developer/petur) 20.54.41 # Bagder: when i get home this arvo ill fix up mips on my desktop and make jdgorond.info actually point to it again... 20.54.42 # Bagder: fixed 20.55.00 # JdGordon: nice, just tell me when it's there! 20.55.04 # LinusN: goodie 20.55.26 # Bagder: I am doing first "make zip" and after using the rockbox.elf file for debug/run the firmware... 20.56.03 # casainho: and for the _third_ time, do you run 'make' first and NOT make bin? 20.56.46 # and the .elf _that_ make produces is what you must use 20.56.47 # eheh, no, jsut make bin... well, then I will do it again... I don't know why, but i did it always like this :-) 20.56.57 Quit LambdaCalculus37 ("CGI:IRC 0.5.9 (2006/06/06)") 20.57.13 # casainho: you should never run make bin. 20.57.19 # casainho: your rockbox.elf needs to load a codec from somewhere, codecs are not built with "make bin" 20.59.37 # so, no testers for FS#10018? come on people it'll be fun ;) 21.00.14 # n1s: maybe later tonight. Right now I'm testing FS#10015 and FS#10026 :) 21.01.16 # gevaerts: yay \o/ 21.01.20 # okok - thanks. I am doing "make" now and I will run/debug the code again :-) 21.01.31 Quit faemir ("Lost terminal") 21.01.36 Part LinusN 21.02.09 # Does anyone have any suggestions about why the rockbox USB stack behaves differently (more errors) with an "old" filesystem than with a freshly mkfs-ed one, if I'm dd-ing the full disk? 21.02.58 # * gevaerts *really* can't understand that 21.04.40 # is the "old" one very fragmented, full or broken in some way? 21.04.45 # n1s: should i test FS#10018? 21.04.54 # I was about to say, could fragmenting mean more seeks and thus cause problems somehow? 21.05.09 # dd-ing the full disk should make such things irrelevant, surely? 21.05.11 # n1s: that's the point, I'm not accessing the filesystem in any way, just the underlying device 21.05.14 # jaykay: which player do you have? 21.05.20 # n1s: e200.... 21.05.27 # gevaerts: ah 21.05.41 # jaykay: yes, testing on e200 would be good 21.05.57 # I think I used sansa.fmt both times though, not mkfs.vfat, but would that make a difference? 21.06.06 # jaykay: can you build a patched version yourself? 21.06.20 Join guest001 [0] (n=someone@32-121.107-92.cust.bluewin.ch) 21.06.41 # n1s: yes 21.06.59 # ok, great 21.07.02 # Something is broken either in the db or in pf on the beast 21.08.03 # I have two albums where cover.bmp exists, but pf refuses to show it, showing '?' instead. I've double checked the file, rebuilt the db and the pf cache - still nothing 21.08.09 # jaykay: the new thing it does is print a message on the display about not finding a rockbox.mi4 and booting the OF instead of powering off it the rockbox.mi4 is not found everything else should be as before 21.11.29 # It works on other DAPs 21.12.51 # Does anybody think I shouldn't move custom filetype colours into the manual (and leave it in the wiki) before I start doing it? 21.13.13 # BigBambi: If it still works, it should be documented in the manual. 21.13.23 # I'm not *entirely* sure all the problems ever got fixed. 21.13.33 # Llorean: Ah, which problems? 21.14.08 # I haven't tried it in an age - I just noticed that there is currently a one liner on the manual pointing at the wiki page 21.14.22 # BigBambi: Do you happen to remember the wiki page? 21.14.26 # BigBambi: i think it belongs as an "Advanced topic" thing 21.14.32 # I seem to vaguely recall problems, maybe if I saw the syntax again I'd remember. 21.14.41 # Llorean: http://www.rockbox.org/twiki/bin/view/Main/CustomFiletypeColours 21.14.54 Quit BUMBACL0T (Connection timed out) 21.15.04 # n1s: Yes, I would just replace the current place holder with actual instructions 21.15.38 # n1s: it didnt work, it said "...not found" and shut down 21.15.42 # nice, didn't know we had a placeholder 21.15.46 # n1s: im trying to read it now... 21.16.12 # n1s: cant load rockbox.mi4: file not found 21.16.23 # cant load rockbox.e200: file not found 21.16.29 # then shutdown 21.16.45 # BigBambi: Hm. I seem to recall problems relating to colors being attached to things they shouldn't be (if you coloured an MP3 it got all audio files, or all other audio files got the ??? or something) but I'm not really sure. 21.16.54 # I did a make clean and after make, but I continue with the same problem, the message "Codec failure" when playing a file... 21.16.58 # It was something relating to colors being passed on to other things. 21.17.00 # jaykay: sansapatcher didn't give errors? 21.17.07 # jaykay: doesn't sound like you properly installed it 21.17.28 # BigBambi: I'm kinda amazed our text-editor handles colours files. That seems like it should be a separate plugin. Our text editor doesn't give special treatment to any other filetypes does it? 21.17.32 # Llorean: I'll try it out 21.17.40 # rasher: gevaerts: i only changed rockbox.mi4 to rockbox2.mi4 21.17.46 # before this rockbox worked 21.17.55 # Llorean: Not that I'm aware of, and I didn't know it did here until I just read that page 21.17.59 # well yes, but this is a bootloader patch... 21.18.10 # BigBambi: I mean, that's _really_ nice, but also kinda _really_ wrong in my book. 21.18.29 # Bagder: do you have any idea? 21.19.34 # gevaerts: should i select bootloader in tools/configure? 21.19.44 # yes 21.20.34 Join BUMBACL0T [0] (n=ORF@unaffiliated/bumbacl0t) 21.20.56 Join taylor_ [0] (n=taylor@c-24-91-82-205.hsd1.ma.comcast.net) 21.21.32 # geaerts: and what should i do next? 21.22.11 # sorry, gevaerts 21.22.18 # install it with sansapatcher 21.23.00 # Using some command-switch 21.23.22 # -a i think 21.24.09 # * jaykay is totally confused 21.24.12 # where -a? 21.24.36 # it says on LCD "Codec failure" and jumps over music one to music 2, and again to one, and 2... 21.24.51 Quit nibbler ("Ex-Chat") 21.24.56 # casainho: do you actually have the codecs installed? 21.25.30 # jaykay: Type "sansapatcher -a pp5022.mi4" (or whatever your new bootloader is called) 21.26.07 # gevaerts: how do I know that I have or not the codecs installed? -- I just did checkout of SVN code, apply my patch and made "make" 21.26.37 # casainho: Does your device have a ".rockbox" folder, with a "codecs" folder inside there, containing lots of "*.codec" files? 21.27.11 # Llorean: It doesn't seem to work at all here (on beast) 21.27.35 # Llorean: The special text editor mode works, but when I select the cfg no colours change 21.27.36 Join r4v5 [0] (n=r4v5@glasnost.us) 21.27.38 # BigBambi: I blame viewports. 21.27.51 # I bet with viewports assigning text colors now, the patch doesn't work the same way 21.28.01 # linuxstb: I don't know :- ) -- will check it :-) 21.28.11 # * Llorean is just making random assumptions in this case. 21.28.25 # It's been forever since anyone's used that feature, I'm sure. I used to love it, but lost my colors file and never rebuilt one. 21.28.33 # Llorean: yeah, could be. It says settings loaded and all but bog all happens 21.28.51 # Llorean: I was the same - I loved it, lot it and forgot 21.29.00 # n1s: it works 21.29.03 # *lot 21.29.08 # dammit - *lost 21.29.24 # BigBambi: A separate color editor that listed all the extensions in filetypes.c would make it a lot more usable in general (more saying this to the "air" than you) 21.29.32 # VKeyboard = "nobody will use it" 21.29.39 # n1s: but i noticed that it took some time from "file not found" to "loading original firmware" 21.29.43 # Llorean: Yes, I agree 21.30.21 # rockboxdev.sh seems to choke when installing multiple toolchains at once because of the creation of summary-$1 in the /tmp/rbdev-build directory. Would the better fix be to create those summary files in a different directory or to not check for the nonexistence of /tmp/rbdev-build between runs? 21.30.44 # casainho: A typical installation of a rockbox build is done by "make" then "make zip" then extracting the zip to the storage of your player, so that the bootloader can load the zip from the storage. Is that how your build of Rockbox is installed (and loaded)? 21.30.52 # r4v5: i.e. running multiple instances simulataneously? 21.31.03 # No, just choosing s m a i 21.31.19 # r4v5: Hmmm, that worked fine last time I tried it 21.31.33 # Llorean: loading the binary :) 21.31.49 # Hmm, PF has a kinda funny bug: If you add albums but don't rebuild the cache, the pictures no longer match the albums, they're shifted... 21.31.50 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 21.31.54 # or build maybe :) 21.31.56 # BigBambi: Binary, right. 21.32.06 # okay. I'm using an svn co from a few hours ago and it definitely bails after each toolchain. 21.32.29 # Llorean: no. I am putting .rockbox folder on SD Card (did this just one time) and after I am loading the rockbox.elf file witth JTAG and debug/run it... 21.32.35 # r4v5: What environment are you trying it in? 21.32.48 # r4v5: that summary thing was modified recently, perhaps it bugs 21.33.03 # * Bagder looks for kugel 21.33.48 # Llorean: this is ubuntu, running with a root shell, GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu) 21.34.30 # Llorean: er, I take it back - me stupid 21.34.44 # BigBambi: They work, or something else? 21.34.49 # Llorean: It turns out that the .colours file has to be in .rockbox/themes 21.34.56 # r4v5: cut out that entire summary thing for now to make it run 21.34.59 # I had it in .rockbox 21.35.00 # casainho: Does your SD driver work? 21.35.05 # When in the themes subdir, it works 21.35.08 # BigBambi: I don't remember that being a requirement previously. 21.35.21 # linuxstb: He can browse to the file to attempt to play it, at least. 21.35.23 # linuxstb: more or less ;-) -- most part of times. 21.35.30 # Llorean: I didn't expect it - I thought it was in there on the wiki page just as an example 21.35.38 # casainho: Then that may be your problem... "more or less" isn't good enough ;) 21.35.54 # BigBambi: I guess that makes sense, though. Enforced cleanliness. heh. 21.36.14 # I'll make it more clear that it has to be there 21.36.56 # Llorean: It seems OK too - e.g. my MP3s have changed but my oggs haven't 21.36.58 # linuxstb: sometines I got a panicf... 21.37.09 # (as per my quick try) 21.37.27 # casainho: Have you done any tests to see if it is reading data correctly? 21.38.15 # linuxstb: yes, I did. I am using the CRC32 to check it -- Domonoky did help a lot on that time :-) 21.38.21 # Bagder: I'm just installing them one at a time and nuking the rbdev-build dir each time, same process. seems like lines 244 to 254 should be moved out of buildone(), if the build dir is reused 21.38.59 Quit jhMikeS (Read error: 60 (Operation timed out)) 21.39.10 Quit casainho (Read error: 104 (Connection reset by peer)) 21.39.47 Join casainho [0] (n=chatzill@87-196-63-213.net.novis.pt) 21.40.01 # casainho: A logf-enabled build might give some clues as to why the codec fails. 21.41.07 # also make sure the codecs on the sd-card are new enough.. (there is a version check) 21.41.59 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 21.43.54 # Lear: thanks. 21.44.27 # domonoky: for example, I need to put the codecs on SD card everytime? 21.45.17 Join jordoex [0] (n=quassel@d142-058-094-228.wireless.sfu.ca) 21.45.45 # not everytime, but if there are changes in the codec api in rockbox, or if you change linkage options, (maybe more) 21.45.58 # jaykay: great, thanks for testing. The delay is intentional to let people read the message on the display 21.46.04 # and ofcourse, if you get problems, you should try a complete fresh install :-) 21.46.14 # casainho: To be safe, especially while developing, you should always make sure all files come from the same build to avoid extra errors. 21.46.33 # n1s: how about a blank line between failing and loading? 21.46.52 Quit bertrik ("Leaving") 21.47.23 Quit guest001 () 21.47.40 # okok... I am getting now some more problems. At least the "Codec failure" do not happens any more :-) 21.49.16 # jaykay, might be nice 21.49.38 # hmm, maybe the display should be cleared entirely first 21.50.41 Join tessarakt [0] (n=jens@e180074066.adsl.alicedsl.de) 21.52.42 Quit casainho ("ChatZilla 0.9.84 [Firefox 3.0.7/2009030422]") 21.53.52 # n1s: how about this: before "could not load" a blank line so that everyone reads it, a delay, than cleaning the screen and then loading original.... 21.54.38 # why clear it after displaying the message? 21.57.16 # [21:49] hmm, maybe the display should be cleared entirely first 21.57.21 # you said it 21.57.46 # to make sure everyone reads "could not load" and "loading original..." 21.58.03 # jaykay: try adding reset_screen(); after line 552 in bootloader/main-pp.c and see what you think 21.58.04 # or make these two messages red :) 21.58.30 # jaykay: sorry i misread your message 21.58.53 Join EvanCarroll [0] (n=ecarroll@12.28.61.169) 21.58.56 # Unfortunately, RockBox is not something we support as we feel we are providing everything that our customers need. 21.59.00 # per Greg at rockbox 21.59.04 # err 21.59.05 # Sansa 21.59.20 # i like clearing the earlier messages before printing "Could not find ..." more than a blank line though 22.00.33 # EvanCarroll: is there a question? 22.01.50 # no, I wrote an email to sansa, and in essense that was his response 22.02.22 # Trmarkable 22.02.28 Quit jhMikeS (Nick collision from services.) 22.02.29 # Remarkable 22.02.34 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 22.02.41 # I'm not sure I understand the context then. We don't depend on Sandisk's support or anything here. 22.02.54 # EvanCarroll: What were you asking Sandisk? 22.03.51 # for support or sponsorship to develop a port for the AMS and/or View 22.04.38 # * gevaerts thinks that the fact thay they bothered to answer is very encouraging 22.05.24 # n1s: it's better now, because the whole uninteresting crap before "cant load..."is not shown (well maybe for a fraction of a second) 22.05.31 # * Llorean remembers the lack of answers he got from PortalPlayer both pre and post-Nvidia. 22.05.42 # Galois: he actually wrote a long answer and his phone number is in the sig 22.05.55 # n1s: i suggest to remove the uninteresting crap after this as well :) 22.06.14 # Llorean: No reply from the USB people I assume? 22.06.14 # http://rafb.net/p/ve3D3t75.html 22.06.24 # I think we would get the port if we had advocacy that didn't suck 22.06.49 # linuxstb: Nothing. 22.07.09 # I mean, it isn't like sansa has the legroom to not-grow their market share. Walmart has fully pulled all third party accessories at every location i've been too, and i don't think the Fuse was the ipod competitor they wanted it to be. 22.07.09 # linuxstb: That one seems rather baffling, since they're inviting exactly the sort of inquiry I made. 22.07.25 # EvanCarroll: What do you mean "get the port"? 22.07.35 # EvanCarroll: The port just needs people to actually work on it... 22.07.57 # Nothing is really "needed" from Sandisk. What we need is more people doing the work. 22.08.10 # jaykay: hmm, maybe, that mi4 loading function outputs a lot of text but it might be nice tellign the user that it's loading the OF but otoh that's pretty obvious after a while... 22.08.26 # Llorean: as in them bestowing the assitance needed to get it supported up to the level of the offical ports, fixing the bug with the 1gb cap on 2gb+ models, and the scroll wheel 22.08.41 Part The-Compiler 22.08.41 # EvanCarroll: Again, that's just an issue of "people need to do the work" 22.09.02 # EvanCarroll: NONE of the Rockbox ports have had assistance from the manufacturers beyond maybe a hardware donation or two. 22.09.21 # the original e200 was supported by the manufacturer iirc 22.09.23 # n1s: i have basically the opinion that for a normal user only understandable things should be shown, the rest only for debug-whatever 22.09.34 # n1s: but its obvious, of course 22.09.35 # EvanCarroll: Not really. They donated two players. 22.09.36 # EvanCarroll: Not really. 22.09.38 # EvanCarroll: You recall incorrectly, or were misinformed. They gave us a few pieces of hardware. 22.10.02 # IIUC, it was just someone in their marketing department - they never provided any technical help. 22.10.09 # jaykay: Often we need to ask people the debug information, it's easier if it's shown rather than requiring them to time presses or something. 22.10.18 # ok 22.10.34 # I don't see the harm in asking them to fund a port through a bounty or to fix the problems that would create an incentive to purchase their player. 22.10.59 # EvanCarroll: it'll never happen. 22.11.04 # EvanCarroll: No harm in it, but it's somewhat unrealistic to expect them to spend money on it. 22.11.13 Quit Chex ("Lost terminal") 22.11.19 # I'm not a rockbox developer, but i bought a sansa model because my last one work with rockbox and I was happy, my current one doesn't, and I'm not happy, nor would i buy another one -- that's all I was aiming to tell them. 22.11.23 # And they responded. 22.11.38 # Llorean: why would you say that, their resellers sell on Rockbox. 22.11.45 # EvanCarroll: Basically, it probably goes something like this. 1) We start supporting a player. 2) People use our tools to mess up players. 3) Those people try to get warranty replacements. 4) We get blamed for increased support costs. 22.11.46 # Llorean: the pp bootloader doesn't print any text unless it encounters an error or a button is pressed 22.11.59 # Could somebody have a quick look at http://pastebin.com/m1285bd85 - it jut corrects the spelling in the special part of text_editor that deals with filetype colours. It is tiny but I'm not well versed in these things so want to make sure 22.11.59 # n1s: Yes, so if it encounters that error, it should display all relevant text. 22.12.49 # n1s: i guess including that i cleared out 22.12.54 # Llorean: The same arguement could be made of all things with unofficial linux ports, but yet companies do come around. 22.13.02 # Look at Buffalo, which now sells a router with a linux port. 22.13.14 # BigBambi: A one-character change is hard to mess up 22.13.18 # Llorean: "file not found" is all the relevant text to the file not found error, it's just that i turned on the "verbose" mode to get any text out at all and it displays a lot of stuff when loading the OF too, not that it matters much 22.13.25 # And Linksys, which sells a whole line of Linux capable routers with more ram. 22.13.37 Quit evilnick ("http://www.mibbit.com ajax IRC Client") 22.13.47 # EvanCarroll: Routers is a different industry entirely. 22.13.52 # Llorean: I know, I'm just a little paranoid 22.14.06 # I'd say froobi selling Sansa w/ coupon code "Rockbox" is definitly a sign that someone realizes their is money in the market share 22.14.12 # Llorean: And I guess this counts as a bug fix so can go in? 22.14.24 # n1s: Ah, well does it reboot to the OF in the case of bad binaries (wrong ones) too? 22.14.32 # Like finding a .ipod for the wrong model, or with a bad CRC? 22.14.39 Join MethoS-- [0] (n=lem@host-091-097-240-090.ewe-ip-backbone.de) 22.14.49 # EvanCarroll: Froobi doesn't provide end-user support. They aren't shouldering an added risk. 22.15.50 # People don't even log into routers unless they're moderately technical. Rockbox on the other hand can be installed by a monkey that gets lucky enough with the mouse. We've got to be somewhat frightening to people who see us as a significant possible added cost. 22.16.18 # In fact most routers come with a basic password on them so that you *have* to read at least some of the manual before you can even try to upgrade their firmware. 22.16.26 # * domonoky would find it very nice if some manufacturers would support rockbox, but it probably wont happen.. 22.16.36 # I'd love it if we were supported/helped. 22.16.37 # the monkeys with a mouse, that return their sansa, are doing so because they lost 7gb of storage and a mousewheel, both of these are technical problems that sansa could overcome, or pay to overcome. 22.16.40 # Llorean: actually it prints "Can't load rockbox.mi4" since this case covers all cases where the loading failed, which is either the file is not found or is broken or wrong. And yes, it shoudl start the OF if the file is not valid 22.17.12 # EvanCarroll: That's entirely incorrect. I'm not talking about AMS sansas in terms of returns. I'm talking about supported targets. 22.17.13 # Llorean: maybe i should create a few advocacy pages on the wiki 22.17.51 # n1s: It needs to show the CRC and target string then, if it's a bad file. So we can know if the CRC check was the problem, or if it's an IP4G on an IPCO or whatever the strings are 22.17.59 # also this patch does not touch anything in the ipod bootloader just the other pp-one 22.18.08 # Llorean: oh? So you believe the dual-booting linux firmware for the e200 that runs almost wholey without flaws makes a for a net-loss on Sansa 22.18.18 # n1s: The keypress wait needs to be in a location where that stuff is still visible, no clear. 22.18.29 # EvanCarroll: What linux firmware? 22.18.41 # rockbox 22.18.45 # rather 22.18.47 # * domonoky would like to ask a sandisk ams-developer a few things.. :-) *why did they connect the scrollwheel this way?* 22.19.01 # EvanCarroll: Rockbox is in no way whatsoever based on linux 22.19.18 # BigBambi: my typo, thinking about the router again 22.19.42 # I'm just saying that I honestly think you'd be smoking the crazy pipe to conclude rockbox causes more damage in support than sales. 22.19.43 # EvanCarroll: Considering how many people I've seen openly admit to being willing to lie to Sandisk about things after using sansapatcher or some other tool to brick their Sansa by not following directions, I don't know if it's a net loss, but I DO know it changes their profit/loss from what they expected. 22.20.03 # I'm saying *they* probably think it causes more damage than increased sales. 22.20.17 Join Chex [0] (n=Stefan@bas1-montreal48-1176173096.dsl.bell.ca) 22.20.26 # Llorean: on the c200 if all the output is preserved a lot of text is printed an some lines are overwritten and it's generally very hard to find the relevant message imo 22.20.47 # I just don't think they want to get into the software business. The see each unit sold as basically a finished item 22.20.54 # n1s: So clear, then reprint only the necessary lines. Getting rid of all of them is bad. 22.21.16 # rasher: And what if *we* do something that causes say, 40,000 users to have bricked units? 22.21.19 # companies are normally very sceptically about such open-source things. But it would probably not hurt if someone asks them a few specific things. Maybe we are lucky :-) 22.21.27 # They have no control over us, and we could (conceivably) screw up massively. 22.22.21 # If they get involved with us, someone sue-happy somewhere like the US could try to start a class action or something. It's probably best for them, in an overall liability sense, to be "not involved at all" rather than "helping but take no responsibility for" 22.23.47 # it probably very unlikly they "cooperate" officially with us.. but maybe they can helpout with some advices a litte.. :-) *maybe some one knows a engineer there, and spends a few beers* :-) 22.24.25 # Someone needs to find out where the Sansa engineers drink... 22.24.26 # domonoky: you mean you want the advice of a drunk engineer? ;) 22.24.37 # gevaerts: Ask them first, then buy beer... 22.24.54 # yes ! if they are drunk, they tell more as allowed :-) 22.25.08 # I simply disagree, with the conclusion that it is a) better for them to stay out of it, and b) useless for people to demand it 22.25.19 Quit bmbl ("Woah!") 22.25.20 # EvanCarroll: Nobody said either of those 22.25.33 # EvanCarroll: We said A) They probably think it's better for them, and B) Don't expect anything to come from your demands. 22.25.44 # ok, well, i understand both of those ;) 22.25.46 # Also, whether or not you agree with (a) is totally irrelevant anyway 22.26.24 # Anyone know how to do the release branch properly? 22.26.51 # Llorean: Yes, you say "Bagder, can you create the release branch?" 22.27.20 # Ah, my guess was right. I should've had the courage to just go with instinct on that one. 22.27.41 # Can't any committer branch? 22.27.50 # I think so. 22.28.02 # Llorean: http://www.rockbox.org/irc/log-20080903#11:06:44 22.29.26 # Who wants to do it then? 22.29.34 # IMO, the release should just say v3.2 with no SVN revision at all for the version number 22.29.47 # BigBambi: That can be fixed in the branch later. 22.30.01 # Right now we should just create the branch, so it's there and the freeze on the main branch can lift. 22.30.20 # Llorean: Sure, I just meant in general as we seem to have forgotten for 3.1. It certainly wasn't meant as a do now thing :) 22.30.47 # BigBambi: 3.0 has SVN revision and 3.0, 3.1 just had svn revision, 3.2 will just have 3.2? 22.30.50 # * gevaerts hopes that people will still hold back things like whitespace cleanups until the actual release 22.31.01 # Shall I create the branch then? 22.31.15 # Oh. 22.31.15 # sure 22.31.21 # Llorean: I think that'd be best, and then from here on out just have the release v number 22.31.31 # I actually *can't* release the branch right now. 22.31.39 # BigBambi: still 3.2-RC I think 22.31.39 Quit CaptainKewl ("http://www.mibbit.com ajax IRC Client") 22.31.41 # My laptop isn't in the box I thought it was packed in. 22.31.52 # yes, 30 seconds :) 22.32.06 # * gevaerts volunteers 22.32.28 # What's the build server up to? 22.32.35 # 3.2, right? 22.32.52 # v3_2 for the branch, right? 22.33.04 # The 3.2 is just for the svnversion string? 22.33.06 # yes 22.33.14 # * gevaerts commits 22.33.57 Join jordoex_ [0] (n=quassel@d142-058-094-228.wireless.sfu.ca) 22.35.20 Quit jhMikeS (Nick collision from services.) 22.35.26 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 22.36.53 # Llorean: topic change? 22.37.24 # Llorean: do you want to send the mail to -dev, or shall I? 22.37.46 # gevaerts: Feel free 22.38.26 # ok 22.38.57 Topic "Please read before speaking: http://www.rockbox.org/wiki/IrcGuidelines | Please direct offtopic/social chat to #rockbox-community | 3.2 is branched for release candidates." by ChanServ (ChanServ@services.) 22.39.51 Quit jordoex (Nick collision from services.) 22.40.01 Nick jordoex_ is now known as jordoex (n=quassel@d142-058-094-228.wireless.sfu.ca) 22.40.23 Quit jhMikeS (Nick collision from services.) 22.40.29 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 22.42.58 # didn't 3.1 include "3.1"? 22.43.14 # oh 22.43.19 # * Bagder spots his mistake 22.44.22 *** Saving seen data "./dancer.seen" 22.44.47 # mushroom mushroom 22.44.58 Join __lifeless [0] (n=lifeless@94.50.160.53) 22.45.55 # * Bagder starts a 3.2-RC build round 22.46.59 # * gevaerts sends mail 22.48.14 Quit _lifeless (Read error: 60 (Operation timed out)) 22.53.47 Join poolboy [0] (n=62cb1fd8@gateway/web/cgi-irc/labb.contactor.se/x-619a3072df80d81f) 22.53.52 Quit poolboy (Client Quit) 22.54.11 Join poolboy420 [0] (n=62cb1fd8@gateway/web/cgi-irc/labb.contactor.se/x-632a9dba838569ce) 22.55.04 # so do we know it's a AS3536 in the newer sansas? 22.55.22 # no rockbox for 120gb ipods? 22.56.23 # anyone? 22.56.55 # no 22.57.02 # as the rockbox.org front page says... 22.57.25 # that blows. do you know when it will be released? 22.57.43 # not anytime soon, if ever 22.57.52 # i didnt c it on the front page 22.58.00 # c? 22.58.34 Quit poolboy420 (Client Quit) 22.59.13 # Bagder: did my mail to -dev get lost? 23.00.23 # load average: 31.57, perhaps it'll take a little longer than usual... 23.00.46 # That would explain it :) 23.03.51 # but no, I don't see it in the mailman logs 23.04.15 # I could resend... 23.06.42 Quit jordoex (Read error: 110 (Connection timed out)) 23.07.08 Quit jaykay (Read error: 110 (Connection timed out)) 23.07.29 Quit Lear ("ChatZilla 0.9.84 [Firefox 3.1b4pre/20090313042508]") 23.09.39 Quit Thundercloud (Remote closed the connection) 23.10.07 Quit __lifeless (Read error: 104 (Connection reset by peer)) 23.10.25 Quit jhMikeS (Nick collision from services.) 23.10.31 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 23.10.34 Join __lifeless [0] (n=lifeless@94.50.160.53) 23.14.51 # * amiconn ponders the feasibility of a pure asm opt 23.15.05 # Gcc is just too stupid to optimise this properly... 23.15.28 Quit jhMikeS (Nick collision from services.) 23.15.34 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 23.16.23 Join saratoga [0] (n=9803c6dd@gateway/web/cgi-irc/labb.contactor.se/x-820144a3e415aaa6) 23.16.51 # gevaerts: I tried Toni's patch and was able to copy 15GB without any disconnects 23.16.57 # i think this is promising, but I need to test more 23.17.00 # the 3.2 RC builds are done 23.17.18 # Loading constants from memory, in a tight loop, when there are enough registers available. Also not taking the pipeline latency of the multiplier into account... 23.17.38 # the disconnect thing seems sporadic to me, I was able to copy 2GB with SVN rockbox today without disconnects, while the other day I could barely do 200MB 23.17.53 # i need to test more rigorously to be sure the improvement is real 23.18.21 # Sounds like battery problems... 23.18.51 # http://daniel.haxx.se/rockbox/rc-3.2/ 23.19.40 # saratoga: that sounds promising at least :) 23.19.47 Quit jhMikeS (Read error: 60 (Operation timed out)) 23.20.33 Join jhMikeS [50] (n=jethead7@rockbox/developer/jhMikeS) 23.20.36 # saratoga: this is svn+Toni's patch, without FS#10015, right? 23.20.49 # * amiconn never copied that much using rockbox usb 23.21.00 # http://dailyfail.blogspot.com/2008/05/ogc-logo-fail.html 23.21.23 # Not because I don't trust it, but because OF/diskmode is faster, and I don't want to wait unnecessarily 23.21.47 # bubsy: please, this is not a random chatter channel... 23.21.51 # gevaerts: Is there a patch containing your usb speedup work? 23.22.06 # gevaerts: yes SVN with only Toni's patch 23.22.11 # gevaerts: Sorry for trying to make people smile 23.22.14 # I'll stop with it 23.22.15 # amiconn: FS#10015. You need the DMA patch to make full use of it though 23.22.36 # for the Sansa, the OF and Rockbox speed are basically the same 23.22.40 # unfortunately both are very slow 23.22.46 # testing is quite tedious 23.23.45 # is Toni's patch supposed to be Sansa specific? 23.23.46 # bubsy: #rockbox-community is there for that purpose 23.24.10 # * pixelma was too slow pointing to the topic 23.26.25 Join itcheg [0] (i=62db4767@gateway/web/ajax/mibbit.com/x-345fc70ebdb77d49) 23.27.06 Quit {phoenix} (Remote closed the connection) 23.29.22 # saratoga: not sure. from what I understand it's pretty generic, although ipods may of course be different 23.29.27 Join deweycooter [0] (n=chatzill@64.91.195.155) 23.30.21 Quit jhMikeS (Read error: 104 (Connection reset by peer)) 23.32.00 Join jordoex [0] (n=quassel@d142-058-094-228.wireless.sfu.ca) 23.36.41 Quit jgarvey ("Leaving") 23.37.09 Join Tex [0] (n=cf2ff955@gateway/web/cgi-irc/labb.contactor.se/x-615c1e813baf9deb) 23.39.27 # ok i have an ipod clasic 80g so would that be the same as ipod video? 23.39.34 # no 23.39.39 # ...crap 23.42.09 Quit itcheg ("http://www.mibbit.com ajax IRC Client") 23.42.52 Join CaptainKewl [0] (i=jds@207-237-172-77.c3-0.nyr-ubr4.nyr.ny.cable.rcn.com) 23.43.37 Quit tyfoo (Read error: 104 (Connection reset by peer)) 23.43.37 Quit Tex ("CGI:IRC (EOF)") 23.44.20 Quit lymeca (SendQ exceeded) 23.45.51 # gevaerts: did funman say if he received your cable yet? 23.46.23 # saratoga: no, but I wouldn't expect that yet. It went out on friday, so it's only been two working days 23.46.50 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is) 23.50.23 # ah ok for some reason it felt like longer 23.56.12 Join z35 [0] (n=z35@h213.59.90.75.dynamic.ip.windstream.net) 23.56.26 Quit lymeca (SendQ exceeded) 23.57.13 Quit petur ("ZzzzzZzzzz *plonk*") 23.57.52 Join lymeca [0] (n=lymeca@213-213-141-71.xdsl.is)