--- Log for 12.05.108 Server: leguin.freenode.net Channel: #rockbox --- Nick: logbot_ Version: Dancer V4.16 Started: 9 days and 10 hours ago 00.01.06 Join csc` [0] (n=csc@archlinux/user/csc) 00.04.54 Quit Buschel () 00.09.21 Join n17ikh [0] (n=n17ikh@adsl-243-230-43.chs.bellsouth.net) 00.13.49 Quit n17ikh|Lappy (Connection timed out) 00.14.23 Quit kugel (Remote closed the connection) 00.21.04 Quit Mathiasdm ("Yuuw!") 00.21.31 Quit domonoky (Read error: 104 (Connection reset by peer)) 00.23.17 Join vertic23 [0] (i=bla@d054053.adsl.hansenet.de) 00.23.42 Quit davina (Remote closed the connection) 00.25.01 # hello 00.25.07 Join n17ikh|Lappy [0] (n=n17ikh@adsl-243-230-210.chs.bellsouth.net) 00.28.21 Quit n17ikh (Connection timed out) 00.29.01 Quit Horscht ("Snak 5.3.3 Unregistered copy. Evaluation period is over. Program will now quit. Thanks for using Snak.") 00.33.06 Quit bluebrother ("leaving") 00.34.23 Join UNHchabo [0] (n=84b148bc@gateway/web/cgi-irc/labb.contactor.se/x-d8b132dff7e3088a) 00.35.42 Quit mcuelenaere ("Zzzz...") 00.38.04 Join UNHchab1 [0] (n=UNHchabo@student4-0188.unh.edu) 00.38.05 Quit UNHchabo (Client Quit) 00.43.55 # hey guys, I'm running rockbox on a Sansa e200, and mpeg videos don't show up in the file browser 00.44.20 # i used the automated installer, but i was under the impression that the MPEGplayer plugin got installed on my sansa 00.44.26 # UNHchab1: check the file view setting 00.44.46 # easily accessible from the quickscreen 00.45.10 Quit n17ikh|Lappy (Read error: 110 (Connection timed out)) 00.45.32 Quit ender` (" error compiling committee.c: too many arguments to function") 00.46.00 Quit ompaul (Client Quit) 00.46.37 # ahh, that's it, i had it set to only show playlists 00.46.40 # thank you 00.46.52 Quit n1s () 00.51.31 Join InigoMontoya [0] (n=621cd2f8@gateway/web/cgi-irc/labb.contactor.se/x-4540fa14e2588c61) 00.53.00 Quit gregzx ("ChatZilla 0.9.82 [Firefox 2.0.0.14/2008040413]") 00.53.06 Join miepchen^schlaf [0] (n=miepchen@p54BF7DE0.dip.t-dialin.net) 00.55.08 Quit InigoMontoya (Client Quit) 00.55.19 Quit jhulst (Connection timed out) 00.57.59 Join Zarggg [0] (n=z@216-15-73-111.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 00.58.59 Join Shaid [0] (n=adam@dsl-202-45-112-116-static.VIC.netspace.net.au) 00.59.49 Join MTee [0] (n=MT@41.233.145.16) 01.00.02 # Hello 01.03.55 Quit bertrik ("bye") 01.04.02 Quit obo ("bye") 01.05.37 # hi 01.07.16 Quit desowin ("KVIrc 4.0.0 Insomnia http://www.kvirc.net/") 01.07.35 Join RBPFC [0] (n=webmaste@p4FC7633A.dip.t-dialin.net) 01.07.43 # hi all 01.08.03 Quit Zarggg ("Pursued by a bear") 01.08.21 Join Nico_P [50] (n=nicolas@rockbox/developer/NicoP) 01.09.08 # is it possible to modify my mp3 player to act as an external soundcard? 01.09.36 # no 01.09.41 # why not 01.09.50 # we almost had a gsoc student to write it but he went with another project 01.09.55 # if i can move data to it i should be able to stream 01.10.10 # It is possible with some devices I thought 01.10.18 # But Rockbox can't do it at present 01.10.23 # i know 01.10.32 # In principle it's possible, but someone has to write the code 01.10.36 # does anyone know the binary architecture of Philips SA1210 01.10.48 # it has some .sb files 01.10.53 # and resource sections 01.11.12 # RBPFC: Are you looking to port rockbox to it? 01.11.20 # yes and no 01.11.32 # if no, this is #rockbox... 01.11.39 # i know 01.11.48 # yes: Im planning to port it 01.11.52 # no: a modified version 01.11.53 Join desowin [0] (n=desowin@atheme/member/desowin) 01.12.00 # modified how? 01.12.09 # once i know how my mp3 player works 01.12.13 # i want to add custom features 01.12.29 # er, yes, I gathered thT FROM MODIFIED 01.12.33 # oops :) 01.12.44 # I meant which modified features? 01.12.55 # not sure yet 01.13.06 # i was not thinking about that yet 01.13.11 # first i need to get it run i guess :) 01.13.24 Part UNHchab1 01.13.31 # jhMikeS: here? 01.13.48 # but im unable to figure out what kind of binary file my mp3 player uses 01.13.50 # OK, well check out www.rockbox.org/wiki/NewPorts, and have a look in the New Ports forum in the wiki (and on the wiki) to see if anyone has done any ground work 01.14.04 # RBPFC: do you know the architecture? 01.14.20 # nop 01.14.37 # I'd guess googling is an option, or you may have to open it up and look 01.15.13 # i used google 01.15.18 # and IDA is not helpful either 01.15.34 # it has its very own architecture 01.15.37 # well, if no-one has already done it I guess you will need to open it and look at the chips 01.15.53 Join leox_ [0] (n=leox@165-162-114-200.fibertel.com.ar) 01.16.06 Quit leox (Read error: 104 (Connection reset by peer)) 01.17.05 # yeh but its not up to the chip how they process code 01.17.30 # eh? 01.17.48 # you need to know the architecture for a start 01.17.56 # arm? coldfire? telechips? etc 01.19.08 # first i need to figure out howto open that ass 01.19.26 # it doesnt seem to have any standart screws 01.19.27 # :D 01.21.38 # what books are good to start reading embedded systems ? 01.22.39 Quit hannesd (No route to host) 01.23.27 # Incidentally, I realise that telechips isn't an 'architecture' 01.24.05 # BibBambi : do you know good books to start with in embedded systems ? 01.24.36 # *BigBambi :) 01.24.44 # sorry, no :( 01.24.56 Quit petur ("Zzzzz") 01.25.08 # emm .. how did you learn it? :) 01.25.14 # I didn't 01.25.17 # * BigBambi is no dev 01.26.04 # emm .. sorry, I just supposed that you were from your talk with RBPFC 01.26.19 # thanks anyways 01.26.44 # hehe :) I help out with support, and I can do simple patching and that, but for the in depth low level stuff, not guilty! 01.26.57 # :D 01.27.35 Join chrisjs169 [0] (n=keanu@unaffiliated/chrisjs169) 01.28.11 # MTee: Most core devs are European, and it is 01.30 here, so you may have more luck European daytime 01.28.22 # is it possible for the sansa to fail loading the i2c but still not go into pre-boot mode? 01.28.47 Quit miepchen^schlaf (Read error: 110 (Connection timed out)) 01.29.58 Quit gevaerts ("it's dark outside") 01.29.59 Join Zarggg [0] (n=z@216-15-73-111.c3-0.eas-ubr6.atw-eas.pa.cable.rcn.com) 01.30.17 # BigBambi : thanks, didn't notice that. I thought it's still earlier there ... anyways it's now 2.30 in here :) 01.34.37 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 01.34.41 # i was doing some testing and stuck an invalid copy of the i2c on the recovery mode partition 01.36.13 # * MTee is going to zZzZzZ 01.36.32 Quit MTee () 01.37.05 # from what i've always known and been told, it should go into preboot mode if it has any problems reading the i2c, correct? 01.39.37 *** Saving seen data "./dancer.seen" 01.51.39 # i destroyed my screen of my mp3 player 01.51.40 # :( 01.52.26 # i seem to have destroyed my mp3 player :( 01.52.33 # mine still work 01.52.33 # :D 01.53.38 # i can't figure out why mine doesn't 01.53.55 # it's supposed to go into preboot mode when it fails, but it isn't 01.54.54 Join asda653 [0] (n=18560af5@gateway/web/cgi-irc/labb.contactor.se/x-be2e929623fd675f) 01.55.06 # Despondent rockboxer here :[ 01.57.08 Join Fewlio [0] (n=Fewlio@c-75-72-22-149.hsd1.mn.comcast.net) 01.57.20 # Anyone know how I can reboot a sansa that crashed as a result of installing rockbox? 01.57.30 # went unresponsive after I plugged it back into USB 01.57.46 Join joecool [0] (i=joecool@no-sources/joecool) 01.59.08 # my computer is not recognizing my perfectly-working nano, but the nano recognizes it. iTunes says the nano is corrupt. help anyone? 02.01.55 # http://www.rockbox.org/tracker/task/8272 I seem to have ran into this 02.06.33 Quit Nico_P (Remote closed the connection) 02.07.16 Quit HellDragon (Excess Flood) 02.07.17 # philips sa1210 got a sigmatel chip 02.07.18 Quit asda653 ("CGI:IRC (EOF)") 02.07.56 Join HellDragon [0] (i=jd@unaffiliated/helldragon) 02.15.16 # BigBambi 02.15.17 # still there? 02.15.37 # http://img526.imageshack.us/my.php?image=0511081900pn5.jpg 02.16.01 # lol 02.16.22 # yeah 02.16.24 # thanks rockbox 02.16.40 # that's what happened when I plugged the USB back in 02.17.36 # shit happens 02.17.45 # yeah and nobody knows how to reboot it 02.17.55 # do the same over 02.18.00 # the what 02.18.10 # reinstall it 02.18.14 # do all the steps over 02.18.22 # well the thing is 02.18.24 # I need to reboot it 02.18.27 # I can't 02.18.57 # I can't find any useful info from sansa other than "push the button" 02.19.01 # and rockbox says the same thing 02.19.05 # but the buttons don't work :V 02.19.29 # .. 02.19.44 # because it's crashed 02.26.35 Join mackes [0] (n=root@cpe-24-198-43-238.buffalo.res.rr.com) 02.26.35 # seems like the only thing that's gonna work is removing the battery 02.30.30 Join tedrock [0] (n=tedrock@d235-156-24.home1.cgocable.net) 02.31.50 # How long have you held the power button down, Fewlio ? 02.31.55 # a minute 02.31.59 # literally? 02.32.01 # yes 02.32.04 # I watched a clock 02.32.29 # I have not experienced a crash of my 250 which can not be rebooted from with the long press of the power button. 02.32.29 # because someone told me 20 seconds so I said "yeah I tried that, I'll try a minute just to be sure I'm not an idiot" 02.32.46 # What version of Rockbox were you using? 02.32.50 # newest 02.32.58 # installed it half an hour ago 02.33.03 # what can I do if the HDD won't format (stopps at a certain point) 02.34.42 # used rbutilqt-v1.0.5.zip 02.35.03 Join Horscht [0] (n=Horscht@xbmc/user/horscht) 02.35.21 # oh, it just turned itself off 02.35.27 # battery died haha 02.35.29 Join fdinel [0] (n=Miranda@modemcable002.173-131-66.mc.videotron.ca) 02.40.33 # hmm anybody got a suggestion what to do? my formatting won't proceed 02.41.11 # run checkdisk 02.41.31 # new or old drive? 02.41.34 # older 02.41.43 # might be toast 02.41.55 # that's why I am formatting... 02.42.07 Quit fdinel (Read error: 104 (Connection reset by peer)) 02.42.08 # thought maybe that will fix the read/write timeouts 02.42.23 # no I mean actual toast 02.42.57 # hm? don't make fun (I just broke my mp3 player ^^) 02.43.16 # I mean spread some butter on that because it's not gonna save your data anymore 02.43.28 # :/ 02.43.29 # what're you using to format it? 02.43.33 # windows 02.43.41 # thought it'd be the easiest way 02.43.52 # even though if I had the feeling that it wouldnot work 02.44.08 # partition magic might do a better job 02.44.09 # "might" 02.44.23 Join fdinel [0] (n=Miranda@modemcable002.173-131-66.mc.videotron.ca) 02.44.25 # I just had a drive die in me in the same way not too long ago 02.44.37 # would go about half way and then just freeze 02.45.09 # hmm, I got the X5V - should I buy a new one then? guess will be about 50 bucks for a new one 02.45.38 # you might be able to replace the drive if it's really busted 02.45.58 # chance that it's windows just failing, which it doesn't seem to do much in simple tasks like formatting a drive 02.46.31 # I suggest finding a second opinion 02.47.37 # true, first I'm trying another tool 02.47.50 # good idea 02.59.29 Join ctaylorr [0] (n=ctaylorr@bas1-toronto43-1279532959.dsl.bell.ca) 03.00.46 # hmm, chckdsk fails with E/A timeout 03.00.53 # @3% sucks 03.01.04 # I knew it would end here 03.02.43 Nick fxb is now known as fxb__ (n=felixbru@h1252615.stratoserver.net) 03.02.57 Join JdGordon|uni [0] (i=768aa360@gateway/web/ajax/mibbit.com/x-d2d179851fa3adee) 03.05.35 Quit waldo (Remote closed the connection) 03.14.10 # before you buy a new one, look into replacing the drive, might be cheap might cost the same 03.17.40 Quit Thundercloud (Remote closed the connection) 03.27.19 Quit vertic23 (Read error: 104 (Connection reset by peer)) 03.31.21 Join midgey [0] (n=TJ@c-71-205-31-207.hsd1.mi.comcast.net) 03.34.41 Quit DerDome (Nick collision from services.) 03.34.42 Join DerDom1 [0] (n=DerDome@dslb-082-083-217-057.pools.arcor-ip.net) 03.34.54 Nick DerDom1 is now known as DerDome (n=DerDome@dslb-082-083-217-057.pools.arcor-ip.net) 03.39.01 Join vertic23 [0] (i=bla@d054053.adsl.hansenet.de) 03.39.19 # hmm, seems like I did it... 03.39.38 *** Saving seen data "./dancer.seen" 03.39.55 # you fixed it? 03.40.04 # now I got a fresh HDD - for 'installing' rockbox, I just need to copy a new build on it 03.40.33 # I think - I deleted the partition - created a new one with acronis disk director... 03.40.48 Quit spiorf (Remote closed the connection) 03.41.14 # sorry left out the ? 03.44.28 Join __Dragon__ [0] (n=__Dragon@fl-76-4-123-174.dhcp.embarqhsd.net) 03.44.40 # Fewlio: I have the iAUDIO X5 not disconnected - rebooted - so there is still rockbox booted - should I reboot? 03.45.06 # I'm not sure I joined here for rockbox support also 03.45.17 # I see hehe 03.45.20 # http://img526.imageshack.us/my.php?image=0511081900yb7.jpg 03.45.29 # it fixed itself by running out of batteries 03.46.04 # <__Dragon__> i would like to know if i can keep rockbox from restrating and going into the origial ipod software when i plug it into the usb 03.46.13 # <__Dragon__> original 03.46.37 # search for dualboot 03.46.48 # doesnot look that good, Fewlio 03.47.09 # it did that when I plugged the USB in with the sansa on 03.47.24 # which I found was an older bug apparently 03.48.02 # __Dragon__, A: the __ before your name is annoying. B: Rockbox does not have a USB mode of its own. If you want disk access you must be in Apple firmware of one sort or another. If you want to simply charge, press "Menu" while inserting the USB plug. 03.48.41 # <__Dragon__> ok 03.48.44 # heh, it booted with the new build 03.48.56 # love ya all :D :*** 03.49.24 # guess I keep the new theme hehe 03.50.29 # * __Dragon__ playing: "Insane Clown Posse - Growing Again" [256kbps][44kHz][Stereo] 03.50.29 # speed could be higher though, let's see if I keep those writetimeouts 03.51.54 # __Dragon__, please, no more now playing spam. http://www.rockbox.org/wiki/IrcGuidelines 03.52.11 # <__Dragon__> i hit the wrong button 03.52.42 # soap: do you think there is a connection between a dying HDD and slow transferspeeds (I get now 1,2 mb/s) 03.52.53 Join Llorea1 [0] (n=DarkkOne@adsl-69-154-187-90.dsl.hstntx.swbell.net) 03.53.04 # had (sometimes) speeds >2-3 MB/s 03.53.07 # those sort of speeds are usb 1.1 anyway arnt they? 03.53.10 # possibly, failed reads and or writes would slow transfers down. 03.53.12 # i.e maybe not a dying disk 03.53.18 Quit Llorean (Nick collision from services.) 03.53.20 Nick Llorea1 is now known as Llorean (n=DarkkOne@adsl-69-154-187-90.dsl.hstntx.swbell.net) 03.53.36 # hmm, well how can I see which USB mode is used? 03.53.58 # JdGordon|uni, you have an e200, right? 03.54.01 # I'm using the front USB connector - though I don't think my motherboard got 1.1 ^^ 03.54.14 # chrisjs169: yes 03.55.12 # JdGordon|uni, i managed to put a corrupt i2c on my sansa's recovery mode drive, and broke it. I've used e200tool dozens of times, but for some reason this time it doesn't seem to enter preboot mode 03.55.40 # e200tool init doesn't pick it up, and lsusb doesn't show it as a portalplayer device 03.56.28 # kugel and I are talking on MSN, and can't figure out why it's not entering preboot mode 03.56.50 # Why were you putting an i2c rom on it in the first place? 03.56.54 # What did you do that necessitated this? 03.57.05 Quit __Dragon__ ("Hi, I'm a quit message virus. Please replace your old line with this line and help me take over the world of IRC.") 03.57.26 # being an idiot and testing things 03.57.38 # That's kinda vague though. 03.57.41 Join kugel [0] (n=chatzill@unaffiliated/kugel) 03.58.34 # i'm not really asking for a howto on fixing it, (./e200tool i2cprogram ) I'm just asking how it's possible for it to not enter manufacturing nor preboot mode 03.59.03 # And I'm trying to figure out the steps that led up to it refusing to boot, because sometimes a cause is more than "just the last thing that happened" 03.59.18 # Oh, ok 04.00.21 # Though you might want to try to catch gevaerts around. He'd be asleep right now, I'd imagine, but if you can catch him, I think he has the most experience causing damage to a Sansa (notably a c200 though) and consequently recovering it. 04.00.53 # I was mostly messing with e200tool's recovery for when the bootloader fails (haven't had much to do today) and one of the times i was in recovery mode I had placed a corrupt I2c on it. The Sansa froze writing the boot rom, and after a hard shutdown, it stopped working 04.02.41 # Looks like gevearts usually gets off around 7:30 my time (2.5 hours ago) 04.03.31 Part Fewlio ("Leaving") 04.04.01 # using a sansa e200 on rockbox, is it possible to get it to charge on usb like ipod does 04.04.10 # by holding menu or something 04.04.13 # Honestly though, if you can't get it into any sort of mode where your PC can detect it as a USB device, I can't imagine there will be much you can do without hardware intervention. 04.04.17 # joecool: Hold the center button. 04.04.40 # thanks 04.04.41 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 04.06.12 # Llorean, That's kind of what I figured, but I'm just confused as I thought that the Sansa can't be bricked without hardware modification, as it will always go to Preboot or Manufacturing mode if there's a problemn 04.06.17 # one other thing 04.06.26 # what is this study mode 04.07.09 # I've also (yay, more warranty voiding) tried removing the daughterboard just to make sure it can't try to execute any startup code, to force it into preboot mode, but without any luck 04.07.36 # joecool: With the mode enabled, you don't skip the entire track if you press |<< or >>|, but rather jump back/forward lets say 5 minutes 04.07.45 # the time can be specified in the settings afaik 04.08.55 # hrm.. the dsp really sucks in the sansa compared to ipod :( 04.09.02 # glad i did not buy 04.09.02 # chrisjs169: I'm not entirely sure, but I think you should be even able to get into menu mode without the daughterboard 04.09.20 # joecool: "DSP" means "digital signal processing", and would be affects applied mostly by the software, not hardware relevant... 04.09.26 # which means, removing it does nothing 04.09.33 # er 04.09.34 # kugel, AFAIK, manu mode requires a working i2c, which is stored in the daughterboard 04.09.35 # DAC 04.09.51 # chrisjs169: again, I'm not sure 04.10.02 # in case noone in here saw me a day ago... that was 2 days of sleep deprivation, this is day 3 now 04.10.11 # er night now... it all feels the same after awhile 04.10.29 # which is why i was able to get into preboot after shorting the daughterboard on my last sansa 04.12.37 Quit ctaylorr (Read error: 110 (Connection timed out)) 04.16.34 # how much does the iAudio M3 cost? it is not yet available here in germany 04.17.08 # not yet.. or not anymore? how old is that one? 04.17.16 # not anymore 04.17.34 # I see 04.19.27 # vertic23: most of the rockbox targets aren't available anymore. Except on ebay of course 04.19.29 # hmm, I learned now that only very few players are still in active "production" - selling 04.19.45 # yeah, hmm sad 04.20.25 # so I go and look for which one the rockbox will be available in the future, heh? :D 04.20.51 # vertic23: cowon d2 seems promising 04.21.08 # that's the only player which I know being still available 04.21.23 # I wouldn't recommend the d2 to someone who seems to be looking for an HD based player. 04.21.27 # but, this one is pretty much the opposite of the M3 04.21.47 # Perhaps the Gigabeat S. More recently unavailable, so you can often find them used or refurbished. 04.21.49 # Llorean: I am looking for a player for my girlfriend 04.22.07 # so ...the player doesnot be that ...expensive hehehe 04.22.13 # *shouldnot 04.22.29 # vertic23: Well, you'll more or less just have to search the internet. 04.22.30 # vertic23: Then I#d recomment ebay 04.22.44 # D2 is probably not your best bet, since it's impossible to predict when it'll be really usable 04.23.15 # I did already, Llorean: and I found the cowon iaudio 7 (which is with 110$ affordable) 04.23.23 # 4 GB too - but HDD based 04.23.42 # besides, if he wants an M3, which has no display, a D2 which pretty much only consists of a display (a touchscreen), I doubt the D2 is the one he searches for 04.23.45 # Well, if you're just discussing players not running Rockbox, it doesn't really belong here. 04.24.19 # well... yeah, thanks for the info ;) 04.24.20 # vertic23, the iaudio 7 is flash based but it is getting off topic 04.26.11 # thanks 04.28.55 Quit kugel ("ChatZilla 0.9.82 [Firefox 3.0b5/2008032620]") 04.30.32 Join BHSPitLappy [0] (n=BHSPitLa@unaffiliated/bhspitmonkey) 04.32.40 # can somebody tell me if it's now possible to make a scrolling text when there is a character in the first place? 04.35.02 # ? 04.36.02 # zezayer.cfg <-- I think in this skin it was not possible to let the text scroll (which was annoying when you had long titles...) 04.38.16 Quit joecool (Remote closed the connection) 04.38.45 Join RBPFC1 [0] (n=webmaste@p4FC77626.dip.t-dialin.net) 04.40.47 Quit jhulst (Read error: 104 (Connection reset by peer)) 04.42.12 # hmm iriver h120 is available again, cool 04.47.14 Join simonrvn_ [0] (i=simon@unaffiliated/simonrvn) 04.47.26 Join homielowe [0] (n=eric_j_l@66.183.89.40) 04.47.44 Quit simonrvn (Nick collision from services.) 04.47.51 Nick simonrvn_ is now known as simonrvn (i=simon@unaffiliated/simonrvn) 04.48.50 # * JdGordon|uni 's sansa seems to be FUBAR :'( 04.49.14 # What'd you do to yours? 04.49.38 # nothing, screen doesnt want to turn on! 04.49.55 # Even when dual booting? 04.49.57 # volume control isnt working either 04.50.15 # na, its fine if i reboot it.. 04.50.22 # * JdGordon|uni should have said rockbox was playing up :p 04.50.37 Quit RBPFC (Read error: 110 (Connection timed out)) 04.51.25 # hmm... the sd chip isnt in.. I wonder if its tag/dir chache being naughty 04.51.37 # grr.. it just crashed 05.00.33 Quit z35 (Read error: 113 (No route to host)) 05.07.12 # JdGordon|uni, do you know if the i2c is stored somewhere on the daughterboard, or should I wait for Bagder or gevaerts tomorrow? 05.07.47 # no idea 05.08.23 Join jhulst [0] (n=jhulst@unaffiliated/jhulst) 05.10.44 # ok, i'll wait till tomorrow 05.10.50 # * chrisjs169 tired anyways 05.22.30 # OK, here I go again - after ~6 GB of data copied to my iAudio X5V he says "Disk is full" (so 12-13GB / 18 GB available) 05.22.50 # does that mean my HDD is about to die? 05.22.51 # have you run a disk check? 05.22.58 # well, fresh formated 05.23.35 # does checkdisk other stuff? (I deleted the partition, created a new one / quickformated with FAT32) 05.24.09 # what would you recommend as disk check tool? 05.25.38 Join Makuseru [0] (n=max@163.106.40.24.aeneasdsl.com) 05.27.29 # now I have difficulties in editing other files I had transfered (changing the ID3 tag with a taggingtool - takes [still] minuted to edit) 05.27.44 # now I have data loss @ windows in writing :/ 05.28.16 # if you are using windows, just run their included checking utility...it definitely sounds like something is a bit wrong... 05.28.25 Quit JdGordon|uni ("http://www.mibbit.com ajax IRC Client") 05.28.32 # so chkdsk 05.28.51 # which couldn't finish last time :/ and won't be this time :( 05.29.27 # which cmds would you recommend? 05.29.33 # /F /R? 05.30.41 # eh...the gui version should work fine...you can always have it run on startup too 05.31.42 # what does the opened lock say in the standard theme? 05.32.39 Join sharky6000 [0] (n=sharky60@S010600179a4978d0.ed.shawcable.net) 05.34.25 # hello. anybody here ever install rockbox on a Sansa c250? 05.34.33 # (in linux) 05.36.06 # vertic23: probably that it isnt key-locked 05.36.10 Part midgey 05.36.28 # sharky6000: was there a real question beneath that? ;) 05.37.17 # yeah, hehe, i can elaborate 05.37.30 # just wasn't sure if anybody here was paying attention :) 05.37.44 Quit Makuseru (Read error: 104 (Connection reset by peer)) 05.39.33 # i was planning to post the full details on the mailing list or forum but i haven't received the confirmation emails yet. i just followed the installation instructions and sansapatcher seemed to work, but when i turn off my sansa and power it back on after unplugging the USB device, the initial image flashes .. then when I press a button the rockbox firmware tells me that it can't load rockbox.mi4 (File not found) 05.39.43 *** Saving seen data "./dancer.seen" 05.40.00 # Sansapatcher is not the only install step. 05.40.13 # Did you do the rest of the install? 05.40.41 # i'm following http://download.rockbox.org/manual/rockbox-sansac200/rockbox-buildch2.html#x4-60002 05.41.29 # after sansapatcher it pretty much goes right to "2.4 Running Rockbox" 05.41.43 # But there's a step before sansapatcher, called "Installing the firmware" 05.42.09 # sharky6000: so, you didnt get the registration email? 05.43.07 # yeah, i got the firmware and uncompressed it.. same goes for the fonts. all the files are now in $HOME/.rockbox 05.43.24 # Llorean: do you get many rewards / money donations for your work? 05.43.30 # the instructions dont say to put it in $HOME.. 05.43.36 # root@gravid:~/.rockbox# ls 05.43.36 # backdrops database.ignore fonts recpresets rocks viewers.config 05.43.36 # codecs docs icons rockbox-info.txt tagnavi.config wps 05.43.36 DBUG Enqueued KICK sharky6000 05.43.36 # codepages eqs langs rockbox.mi4 themes 05.43.36 # root@gravid:~/.rockbox# 05.43.47 # (oops, sorry) 05.44.01 # sharky6000: $HOME/.rockbox is not where it tells you to extract them to. 05.44.08 Quit leox_ (Read error: 104 (Connection reset by peer)) 05.44.28 # vertic23: we are volunteers who do not receive any monetary compensation, although i wouldnt say it is rewardless ;) 05.44.47 # vertic23: I personally don't get any rewards. Rockbox itself has a fund that it uses for such things as buying replacement players when people doing work do something horribly wrong, etc. 05.44.54 # well, true - but ...maybe some bills for the server need to be paid... or beer, lotsof beer ;) 05.45.18 # so who wants the beer of you hehe 05.45.22 # vertic23: http://www.rockbox.org/twiki/bin/view/Main/DonatedMoney 05.45.29 # so it's supposed to be in /.rockbox? 05.45.42 # sharky6000: the instructions say the root of the device 05.45.55 # sharky6000: "extract the files in the .zip file onto your player." 05.46.05 # Not your home folder. 05.46.26 # yeah....... ok..... 05.46.34 # you have a rockbox party soon? 05.46.50 # vertic23: well, we have a developer conference soon, yes 05.47.01 # where? 05.47.05 # sorry, i thought the sansapatcher copied those files from the current directory to the device after finding it 05.47.07 # 'secret' lmao 05.47.31 # sharky6000: If it did, the instructions wouldn't say "extract the files in the .zip file onto your player" in them. 05.47.32 # we do work, make decisions and many other things during the conference, and it is far from just a "party" 05.47.42 # I hope so 05.47.52 # wasn't expecting a group of crackheads ;) 05.47.58 # right. 05.48.01 # sharky6000: Did you have problems with the automatic installation? 05.48.02 # well -- ehr you know what I mean ;) 05.48.05 # rtfm .. :) 05.48.15 # vertic23: http://www.rockbox.org/twiki/bin/view/Main/DevCon2008 see the 2 links there 05.48.47 # hmm, ok - I got now one error @ checkdisk "Timelimit \Device\HardDisk7\DR20 05.48.59 # was reached before E/A was done..." 05.49.05 # no.. didn't try it. just assumed an automatic installer wouldn't exist for linux :) 05.49.28 # sharky6000: even when the manual specifies an automatic installer link? ;) 05.49.42 # alright, my bad.. thanks for the help, but i would maybe suggest changing "onto your player" to "to the root of your device" =) 05.49.55 # sharky6000: "Prebuilt binaries for Windows, Linux and MacOSĀ X" and a link. You *really* need to read the manual more carefully, especially since there's a lot of features of rockbox that you'll benefit from having read the manual entries for. :) 05.50.09 # true... 05.50.15 # i hastily read through the manual... ok, i got it 05.50.17 # thanks 05.50.29 # sharky6000: We tried "The root of your device." People who know what "root" means can figure out "on to your device." People who don't know what "root" means generally still get "onto your device" though 05.50.51 # yeah... true. i missed it entirely 05.51.37 # we had lots of people unzipping to /root/.rockbox (and other fun variations) 05.53.47 # thank for the help 05.54.12 # so Llorean, scorche|sh you'll be in berlin? 05.54.31 # looks that way 05.54.49 # so I'll donate you some beer then 05.54.58 # are you in the area? 05.55.15 # yep 05.55.19 # ~200 km away 05.55.31 # but used to live there, so got many friends there 05.56.15 Part sharky6000 05.56.23 Join leox_ [0] (n=leox@165-162-114-200.fibertel.com.ar) 05.57.22 # hmm now my player freezes while calculation free diskspace in chckdisk 05.57.25 # *chkdsk 06.01.34 Join fml [0] (n=4fd3f6b9@gateway/web/cgi-irc/labb.contactor.se/x-01aaf32af2f3db6b) 06.02.27 Join sharky6000 [0] (n=sharky60@S010600179a4978d0.ed.shawcable.net) 06.03.56 # barrywardell_: (for the log): I couldn' reproduce the 'e200' message on c250. Now no text is shown, just the logo (which blinks once or twice). 06.04.32 # anyone here would like to help with subjective testing on a new codec? 06.04.38 # preglow? 06.05.05 # fml: I seem to recall that for some time the c200 builds were identified as e200 when loaded by the bootloader. 06.05.50 Quit Crayzie (Read error: 110 (Connection timed out)) 06.08.17 Quit fdinel ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org") 06.09.05 Join _vertic23 [0] (i=bla@d116057.adsl.hansenet.de) 06.10.46 Part sharky6000 06.24.27 # Llorean: ok. But the main thing is that everything works as it should. 06.24.51 # Yes, the problem is just with a string somewhere I believe 06.25.14 # It really is a c200 build, but since an awful lot of it was copied from the e200 target, I suspect that string accidentally got left. Just a guess though 06.26.48 Quit vertic23 (Read error: 113 (No route to host)) 06.26.52 # <_vertic23> hmm in GUI mode scandisks hangs @ phase 2 again :( 06.27.19 # <_vertic23> so hardware damage? or anything else I could try? 06.28.11 # <_vertic23> or should I try until it surrenders *g* playing the "who is first" game? 06.29.43 Nick _vertic23 is now known as vertic23 (i=bla@d116057.adsl.hansenet.de) 06.32.15 Quit fml ("CGI:IRC") 06.34.32 Quit chrisjs169 (Remote closed the connection) 06.36.48 # hm, ok a night with my player ...now I know it's the harddisk :/ 06.53.51 # wee some progress 07.16.34 Quit m0f0x () 07.18.51 Quit csc` (Remote closed the connection) 07.39.44 *** Saving seen data "./dancer.seen" 07.40.37 Join DaCapn_ [0] (n=dacapn@c-67-170-177-22.hsd1.or.comcast.net) 07.40.41 Quit DaCapn (Read error: 110 (Connection timed out)) 07.40.47 Nick DaCapn_ is now known as DaCapn (n=dacapn@c-67-170-177-22.hsd1.or.comcast.net) 07.58.20 Join z35 [0] (n=z@149.123.33.65.cfl.res.rr.com) 08.02.15 Join GodEater [0] (i=c2cbc962@gateway/web/ajax/mibbit.com/x-b7e179da80550c95) 08.02.20 Quit vertic23 (Read error: 110 (Connection timed out)) 08.11.57 Quit BHSPitLappy (Read error: 110 (Connection timed out)) 08.14.51 Join newnick [0] (n=3a6a9689@gateway/web/cgi-irc/labb.contactor.se/x-7791b65c32f4d545) 08.15.09 # hey guya 08.15.11 # guys* 08.16.06 # quick question 08.16.27 # ipod 6g, you working on a rockbox release for it? 08.16.30 # Quick answer: No. 08.16.36 # Ah, you asked after all. 08.16.47 # :-P 08.16.49 # Answer is still hte same. 08.17.04 # may i ask why 08.17.12 # not possiable? or? 08.17.20 # Because work gets done by people who own the player and are interested. 08.17.21 # The iPod Classic is using unknown hardware, and has an encrypted firmware file. 08.17.33 # It's not easy, and nobody who owns the player has been up to the work. 08.17.43 # ah ok 08.18.04 # i thought the hardware would be pretty much the same as the previous model 08.18.08 # Work can't be done, because no one knows what the hardware is, and that can't be figured out without disassembling the firmware. One can't disassemble the firmware, because it's encrypted. 08.18.18 # hmmm 08.18.20 # yeah 08.18.27 # where theres a will theres a way 08.18.33 # No doubt. 08.18.36 # There's no will. 08.19.40 # its been like 7 months though.. would of thought someone would have got it by now... but ah well.. thanks for clearing that up for me 08.19.53 # At least, there's no will to do it, from those who have the capability. Those that can are endevouring to do other things which they deem more worthwhile, or more entertaining, or easier. 08.20.14 # yeah true 08.21.56 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 08.21.56 # * Mouser_X is happy with the Gigabeat S. 08.22.03 # (Or the F. Both are great.) 08.22.09 Quit jhulst (Read error: 113 (No route to host)) 08.22.25 # which reminds me - time to read up on what I missed for S developments over the weekend! 08.22.41 # True. I ought to update as well. 08.22.58 # * GodEater is pleased he remembered to bring it with him to work today 08.23.34 Join miepchen^schlaf [0] (n=miepchen@p54BF7A19.dip.t-dialin.net) 08.23.43 # Heh. 08.24.07 # One of the commits gave me the impression that I might need a new bootloader. 08.24.15 # Though, I'm entirely unsure on that. 08.25.04 # once you have a rockbox bootloader on there, is upgrading it possible by simply replacing the nk.bin on the first partition with the new one ? 08.25.13 # or do you still have to boot OF and use sendfirm ? 08.25.14 # Indeed it is. 08.25.21 # neat :D 08.25.26 # Very. 08.25.36 # My problem is building an updated bootloader. 08.26.15 # * Llorean is more or less just waiting until power management is more complete to start using his beast, so he doesn't need OF. 08.26.50 # OF is nice for video out. Video out kind of sucks though... 08.27.15 # make your mind up ;) 08.27.30 # * linuxstb is waiting for 160GB disks... 08.27.43 # It's nice to have the feature, but the feature is poorly implemented. 08.27.47 # * Llorean has a PSP if he *really* must have a video out capable device. 08.27.47 # How's that? 08.27.49 # linuxstb: you want more than one ? 08.35.17 Part toffe82 08.37.43 Join Rob2222 [0] (n=Miranda@p4FDCCD0A.dip.t-dialin.net) 08.39.50 # Have people reported problems with bass/treble on the E200 before? I thought it was just other targets... 08.39.56 # http://forums.rockbox.org/index.php?topic=16781.0 08.40.42 # I think it's only been Gigabeats and iPods so far. 08.41.14 # Well "so far" being "up until that thread" 08.41.15 # I thought it was just some of the iaudios... 08.41.23 # So it seems broken virtually everywhere... 08.41.39 # Since austriancoder's commit, at least as far as I know. 08.42.26 # At least, that broke it completely on gigabeat until part of it was reverted, and it seems to mark the time the problems began cropping up for other people, though I don't know of the non-saving problem has been explicitly narrowed down to that revision yet. 08.50.11 Join Bagderr [0] (n=daniel@gateway/web/cgi-irc/labb.contactor.se/x-984dcd7b1ae7b91c) 08.51.44 Nick Bagderr is now known as B4gder (n=daniel@gateway/web/cgi-irc/labb.contactor.se/x-984dcd7b1ae7b91c) 08.55.58 Quit Rob2223 (Read error: 110 (Connection timed out)) 08.59.30 Quit newnick ("CGI:IRC") 09.02.12 Join ender` [0] (i=krneki@foo.eternallybored.org) 09.04.41 Join LinusN [0] (n=linus@rockbox/developer/LinusN) 09.12.35 Join OlivierBorowski_ [0] (n=OlivierB@ANancy-157-1-10-160.w86-204.abo.wanadoo.fr) 09.25.03 Join davina [0] (n=davina@cpc1-sout6-0-0-cust616.sotn.cable.ntl.com) 09.28.25 Quit OlivierBorowski (Read error: 110 (Connection timed out)) 09.28.58 Join [CBR]Unspoken|w [0] (n=cbr@212.98.160.130) 09.37.13 Join lee-qid [0] (n=liqid@p549648D7.dip.t-dialin.net) 09.38.41 Join Synergy6 [0] (n=Synergy6@0-1b-24-4c-ae-79.hb.esol.dur.ac.uk) 09.39.49 *** Saving seen data "./dancer.seen" 09.41.27 Join spiorf [0] (n=spiorf@host126-226-dynamic.25-79-r.retail.telecomitalia.it) 09.52.02 Join Llorea1 [0] (n=DarkkOne@adsl-69-154-187-90.dsl.hstntx.swbell.net) 09.52.17 Quit Llorean (Nick collision from services.) 09.52.19 Nick Llorea1 is now known as Llorean (n=DarkkOne@adsl-69-154-187-90.dsl.hstntx.swbell.net) 09.57.37 Quit Shaid (Read error: 110 (Connection timed out)) 09.58.17 Quit linuxstb (Read error: 110 (Connection timed out)) 10.05.57 Join n1s [0] (n=nils@rockbox/developer/n1s) 10.09.04 Join pondlife [50] (n=Steve@rockbox/developer/pondlife) 10.22.52 Quit Synergy6 ("Adios") 10.22.53 Join Buschel [0] (n=AndreeBu@p54A3CAF0.dip.t-dialin.net) 10.39.41 Join radio-head [0] (n=Dangerme@122.109.121.87) 10.39.48 # hi guys 10.39.53 # what's rockbox? 10.40.04 # www.rockbox.org 10.40.05 Quit Mouser_X (Read error: 104 (Connection reset by peer)) 10.41.04 # i went on it 10.41.13 # it doesn't explain it that well? 10.41.27 Join Mathiasdm [0] (n=Mathias@78-22-5-158.access.telenet.be) 10.41.45 # you read this too : http://www.rockbox.org/twiki/bin/view/Main/WhyRockbox ? 10.42.48 # ok 10.45.26 # question: codecs use the plugin iram? 10.47.36 Quit z35 ("Leaving") 10.47.46 # radio-head: did that help ? 10.48.14 # GodEater: a bit 10.48.25 # is there still something which is unclear ? 10.48.25 # i know its firmware 10.48.35 # and it replaces the original ipod firmware 10.48.36 # Buschel: no, then they wouldn't run while playing music 10.48.46 # I mean plugins and codecs 10.48.51 # but i don't know the advantages and the features of it yet 10.49.06 # b4gder: ok, so codecs use the iram size defined in the app.lds 10.49.38 # core, codecs and plugins basically have one part each of the iram 10.51.28 # radio-head: perhaps this then too : http://www.rockbox.org/twiki/bin/view/Main/FeatureComparison 10.51.41 # scroll down past the first table to find the feature comparisons for the ipod 10.51.45 # GodEater: ty 10.52.06 Join Arathis [0] (n=doerk@p508A5A4E.dip.t-dialin.net) 10.52.08 Join Pichet_Goulu [0] (n=Pichet_G@73.176-244-81.adsl-dyn.isp.belgacom.be) 10.52.10 Nick Pichet_Goulu is now known as Pichet (n=Pichet_G@73.176-244-81.adsl-dyn.isp.belgacom.be) 10.52.15 # radio-head: rockbox has some features (more codecs, normal folder browsing, some games, audio effects) which might be an advantage to some, but others are happy with itunes and the original firmware. 10.52.41 Join GodEater_ [50] (n=bryan@rockbox/staff/GodEater) 10.52.46 # markun: ty, much better help 10.52.54 # ty 10.52.57 # byt markun 10.52.59 Part radio-head ("Fuck off!! I'm fucking the T.V...") 10.53.21 # I guess he was the 2nd kind of user then :) 10.53.28 # I guess he was :) 10.55.35 # Bagder: ?? afaik plugins use the same iram as codecs, that's why you _can't_ use iram in a plugin without stopping playback 10.56.44 # ah 10.56.50 # * B4gder forgets 10.58.23 # when trying to support the 128KB iram of PP5022/24 i need to change app.lds (new length) and plugin.lds (new iram start adress and length). correct? 11.01.51 # like this http://pastebin.com/m7191fede 11.05.56 Join bertrik [0] (n=bertrik@190-023-045-062.dynamic.caiway.nl) 11.07.24 Join Genre9mp3 [0] (n=yngwiejo@dsl-88-218-17-35.customers.vivodi.gr) 11.08.14 Part Genre9mp3 11.08.50 Join Genre9mp3 [0] (n=yngwiejo@rockbox/contributor/Genre9mp3) 11.09.19 # Hmm, http://rockboxhack.wetpaint.com/page/downloads has an interesting installation sequence... :) 11.09.43 # But also, a GPL-violating ipodpatcher.exe 11.10.44 # ugh 11.11.08 # My thoughts exactly 11.13.26 # typo -- forgot a "0" -> http://pastebin.com/m4357476f 11.14.04 # pondlife: a GPL violating ipodpatcher?...looks like they tell them to use rbutil 11.14.44 # There's apparently an ipodpatcher.exe link there 11.16.29 # Which is particularly odd given that they go the RBUtil route - a minor blessing in itself... 11.16.42 # GodEater, MouserX: I uploaded a new dual-boot nk.bin after the recent you need a new bootloader build too commit 11.18.32 # pondlife: quite odd...probably just took it from rockbox.org and put it there though 11.19.07 # Indeed, but they should provide at least a link to the source (and the license), no? 11.19.14 # of course 11.20.22 # To be honest I'm more depressed by the quality of the instructions (and of most YouTube "help" videos) that make Rockbox look harder to install than it really is. 11.21.28 # yes...it isnt really something we can really do though (wrt the videos) 11.21.41 Quit Pichet ("ChatZilla 0.9.81 [Firefox 2.0.0.14/2008040413]") 11.22.44 Join inversions [0] (n=sam@79.97.22.57) 11.23.02 # * scorche might sign up on the site and send him a message 11.23.06 # ...tomorrow 11.27.14 Join Mouser_X [0] (n=mouser_x@layl001.digis.net) 11.27.14 # * JdGordon reminds scorche that it is already "tomorow" 11.27.20 # or actually this morning... 11.27.30 # and soon will be yesterday 11.27.42 # * scorche reminds JdGordon to stuff it and let him get his 3 hours of sleep before worktime 11.34.22 Join domonoky [0] (n=Domonoky@rockbox/developer/domonoky) 11.37.13 # BigBambi: url ? 11.37.35 # http://aeparker.com/files/nk.zip 11.38.20 # ta 11.38.30 # np 11.39.08 # and just to double check, it's possible to replace the nk.bin from the bootloader's usb mode? Or is that a bad idea, and I should do it from rockbox proper ? 11.39.52 *** Saving seen data "./dancer.seen" 11.40.37 # wow, configuring my 5.5G to 128KB iram and use it for several arrays speeds up the mpc decoder by 6.6% ;o) 11.41.36 # GodEater: I've never tried it from the bootloader usb mode, but from rb proper it is fine 11.42.10 Quit simonrvn (Read error: 113 (No route to host)) 11.45.25 Join Thundercloud [0] (n=thunderc@resnet32.nat.lancs.ac.uk) 11.47.00 Join simonrvn [0] (i=simon@unaffiliated/simonrvn) 11.49.07 Nick fxb__ is now known as fxb (n=felixbru@h1252615.stratoserver.net) 11.55.02 Quit Genre9mp3 () 11.59.06 # * JdGordon thought we didnt allow the delete option in the WOS context menu? 11.59.47 Join linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 12.06.41 Join Nico_P [50] (n=nicolas@rockbox/developer/NicoP) 12.08.36 Join lee-qid_ [0] (n=liqid@p549648D7.dip.t-dialin.net) 12.19.18 Quit lee-qid (Read error: 104 (Connection reset by peer)) 12.20.41 # JdGordon: it's there in official builds at least... 12.21.58 # B4gder: "Bagder got a nano2g bootloader image to disassemble"... how? does that mean you managed to decrypt it? 12.22.32 # no 12.22.48 # just that I have the image, which is mostly encrypted 12.22.50 # I looked at it briefly last night and at least some parts did seem plaintext 12.23.41 # B4gder: ah, I thought this was some major breakthrough :p 12.24.13 # a minor one only, they extracted this ;-) 12.24.13 # how did you get the image? it's available at Apple's? 12.24.42 # this came from work done by the linux4nano guys 12.25.05 Quit miepchen^schlaf () 12.25.42 # bloody hell 12.25.54 # you mean that project has actually acheived something ? 12.25.59 # B4gder: is there somewhere I can read about this? the linux4nano website doesn't seem to be quite up to date 12.26.32 # Nico_P: no, i don't think so. the only info I've found there was useless 12.26.56 # daniel.haxx.se/nano2g-bootloader.bin 12.27.10 # 1MB image 12.27.24 # big-endian arm in the beginnning 12.32.15 # Isn't the meizu also big-endian (and also the same/similar CPU)? 12.32.23 # yes and yes 12.32.26 Quit desowin ("KVIrc 4.0.0 Insomnia http://www.kvirc.net/") 12.32.49 # food 12.38.23 Join chevron [0] (n=7cbf6166@gateway/web/cgi-irc/labb.contactor.se/x-40f73bbaa2f5c6a2) 12.38.23 Quit pabs (Read error: 113 (No route to host)) 12.38.50 # does anyone know when the nano 3rd gen are coming out? 12.38.57 Quit chevron (Client Quit) 12.46.26 Quit spiorf (Remote closed the connection) 13.01.47 Join MiniUser [0] (n=kevin@124.66.141.214) 13.02.52 Join miepchen^schlaf [0] (n=miepchen@p54BF7A19.dip.t-dialin.net) 13.03.04 Join waldo [0] (n=waldo@ip-81-11-201-20.dsl.scarlet.be) 13.08.40 # Hi, I'm using an Ipod mini, 1st gen with rockbox r17250-080426. I'm getting a lot of errors when copying files to the player from xubuntu. A lot of the time, I'll try to copy a file and the attempt will fail with an I/O error, and then it becomes impossible to eject the Ipod without shutting down the computer 13.09.10 # it's happening on 2 different machines, one with xubuntu 7.10, the other with 8.04 13.09.26 # my windows machine is down at the moment so haven't been able to try there 13.09.38 # MiniUser: did you check the disk on your player for errors ? 13.10.10 # I've fsck'ed the player, nothing special, and the problem has reoccurred 13.10.54 # * Buschel added a patch to the tracker which enables 128KB IRAM for PP5022/24 -> FS#8987 13.10.58 # I've googled, looked through manuals and faqs, So far nothing 13.11.26 Join das-perceptron [0] (n=fabian@e176107198.adsl.alicedsl.de) 13.12.09 # there is also a patch included to take advantage of the additional iram for musepack decoding 13.12.23 # sounds like a good idea to make sure we use more iram 13.12.45 Part das-perceptron 13.12.59 # 5022 and 5024 are the most popular PP models too - counted by download 13.13.03 # MiniUser: its probably not a rockbox problem, as on ipods rockbox doesnt have its own usb mode (till now) .. you are using apple software for usb transfers.. 13.13.15 # ok 13.13.25 # any ideas on where to look then? 13.13.49 # B4dger: it also can help runtime as some of the codecs can be further optimized now 13.14.03 # it's a second hand player, I never used it with Itunes aside from reflashing it, but I can try moving files with itunes to test it out 13.14.16 Join desowin [0] (n=desowin@atheme/member/desowin) 13.14.30 # B4dger: nevertheless somebody should check my patch. i am not sure everything is done right. works for me though 13.15.28 # MiniUser: you could also try if it is your usb-cable, i had such problems with a broken usb extension cable.. 13.16.27 # Thanks, that's actually on my list of things to try once I get my hands on another cable 13.16.36 Quit Evilnick (Read error: 104 (Connection reset by peer)) 13.20.52 Nick Buschel is now known as Buschel_away (n=AndreeBu@p54A3CAF0.dip.t-dialin.net) 13.27.35 Join Bensawsome [0] (n=upirc@72.10.125.130) 13.27.57 # domonoky: Thanks a lot for the ideas. I'm heading off now. Hopefully it really is just a dodgy cable 13.29.46 Quit MiniUser ("Leaving.") 13.30.00 Quit Bensawsome (Client Quit) 13.32.04 # Buschel_away: Looking at your patches, did you look to see how much core IRAM is used by each target? Will the core benefit from the extra? Also, your musepack patch seems to have what look like unrelated changes - is decreasing MPC_DECODER_MEMSIZE related to the IRAM patch? 13.36.22 # Buschel_away: weird... 13.36.41 # * preglow back in a few hours 13.39.56 *** Saving seen data "./dancer.seen" 13.49.56 Join simonrvn_ [0] (i=simon@unaffiliated/simonrvn) 13.51.22 Join nplus [0] (n=nplus@141.25.Globcom.Net) 13.53.42 Quit lee-qid_ (Read error: 110 (Connection timed out)) 13.54.56 Quit simonrvn (Read error: 113 (No route to host)) 13.54.56 Nick simonrvn_ is now known as simonrvn (i=simon@unaffiliated/simonrvn) 13.56.11 Quit Horscht ("http://www.geisterfahrer.org") 13.57.03 Part LinusN 14.00.21 Quit ender` (Read error: 104 (Connection reset by peer)) 14.00.25 Join petur [50] (n=petur@rockbox/developer/petur) 14.00.43 Join das-perceptro1 [0] (n=fabian@e176107205.adsl.alicedsl.de) 14.02.23 Join ctaylorr [0] (n=ctaylorr@bas1-toronto43-1279532959.dsl.bell.ca) 14.06.28 Join fleytin [0] (n=fleytin@217.70.16.169) 14.07.57 Part fleytin 14.08.31 Join p3tur [0] (n=petur@d54C6F6F4.access.telenet.be) 14.09.22 Quit petur (Nick collision from services.) 14.09.27 Nick p3tur is now known as petur (n=petur@d54C6F6F4.access.telenet.be) 14.12.08 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 14.12.25 Nick Buschel_away is now known as Buschel (n=AndreeBu@p54A3CAF0.dip.t-dialin.net) 14.13.09 # linuxstb: MPC_DECODER_SIZE was another change I've made experimenting with the IRAM. this change is not needed, but doesn't harm anything -- speedwise 14.13.41 # Buschel: So does it need to be part of that patch? 14.13.57 # linuxstb: i did not check how much iram is used by the core. i just enabled it as a first step to check, if it works. 14.14.37 # linuxstb: mpc -> this change is not needed. nevertheless it makes sense to reduce ram usage, if it doesn't hurt speed 14.15.39 # Buschel: I'm just in favour of making patches as small as possible, and not mixing independent changes. 14.16.26 # linuxstb: that's right. i not submit it this way (if the iram stuff should be agreed for submission) 14.17.52 Quit perrikwp ("http://www.mibbit.com ajax IRC Client") 14.22.55 # is there any core stuff which may have advantages of more iram? otherwise we could simply add the additional iram to the plugins 14.23.04 Join ender` [0] (i=krneki@foo.eternallybored.org) 14.28.31 Nick Buschel is now known as Buschel_relaxing (n=AndreeBu@p54A3CAF0.dip.t-dialin.net) 14.36.09 Join dabujo [0] (i=xx@p4FDB2738.dip0.t-ipconnect.de) 14.42.51 Join Siku [0] (n=Siku@e81-197-72-64.elisa-laajakaista.fi) 14.45.03 Quit BlakeJohnson86 (Read error: 110 (Connection timed out)) 14.45.34 Join moos [0] (n=c40cd9a6@gateway/web/cgi-irc/labb.contactor.se/x-0515af34e61eecf7) 14.48.10 # JdGordon: around? 14.48.18 # am now 14.48.33 # * JdGordon not exactly in a useful state though 14.48.44 # is that rec screen as viewport somewhere online? 14.50.21 # dunno.. dont remember how far I actually got.. 14.50.31 # gimme a min.. ill look around ehere for it 14.53.09 # i found a patch changes.recscreen but I'm not sure hoiw much of it it is 14.53.10 # no hurry, I'm going to (try to) sync the REP first... 14.53.47 # http://pastebin.ca/1015702 14.54.01 # was just thinking that maybe changing the rec screen to viewports would save the work of re-syncing again afterwards 14.55.50 # thnx 14.57.40 Join LambdaCalculus37 [0] (n=44a0430f@gateway/web/cgi-irc/labb.contactor.se/x-239a1f0480bcbc5a) 14.59.41 Quit OlivierBorowski_ (Remote closed the connection) 15.01.40 Nick JdGordon is now known as JdGordon|zzz (i=jonno@rockbox/developer/JdGordon) 15.07.49 # petur: instead of syncing the REP patch.. if you strip the drawing code out of the main loop it would make viewportting it much easier 15.08.40 # I'm looking at the viewport now and will try to clean it up 15.15.58 Join p3tur [0] (n=petur@d54C6F6F4.access.telenet.be) 15.15.58 Quit petur (Read error: 104 (Connection reset by peer)) 15.16.18 Nick p3tur is now known as petur (n=petur@d54C6F6F4.access.telenet.be) 15.17.11 Join perrikwp [0] (i=982176d7@gateway/web/ajax/mibbit.com/x-4b7294a7e1dd4945) 15.24.01 Quit petur (Read error: 104 (Connection reset by peer)) 15.24.24 Join petur [50] (n=petur@rockbox/developer/petur) 15.25.56 Join Shaid [0] (n=adam@210-84-52-19.dyn.iinet.net.au) 15.28.57 Join voltagex [0] (n=voltagex@220-253-116-98.ACT.netspace.net.au) 15.29.02 # hi, anyone active? 15.29.14 # the os x rbutil keeps crashing on me 15.30.12 # There's 142 people in this channel right now. 15.30.51 # voltagex: do you have more details when it is crashing and how ? 15.31.05 # installing the bootloader 15.31.10 # And also what device you're trying to install Rockbox onto? 15.31.14 # after it finishes downloading bootloader.bin 15.31.24 # sorry for not providing details... H340 15.33.09 # i think it's the firmware patching app that's crashing 15.34.10 # Have you tried with both the "Small Installation" and "Full Installation" options? 15.34.29 # same result 15.34.37 # crash before the .hex is patched 15.34.40 # LambdaCalculus37: that wont help its the same code.. :-) 15.34.48 # voltagex: whats the last output ? 15.34.55 # with both 1.29 and 1.30 firmware .hexes 15.35.12 # "Downloading bootloader.bin" 15.36.14 # voltagex: could try running it from a console, and see if there a more outputs on the console ? 15.36.42 # domonoky: unsure how to run the osx .app from a console 15.37.00 # * domonoky also doesnt know OSX.. :-) 15.37.25 # voltagex: Run it by typing "open .app" in the console. 15.37.37 # * LambdaCalculus37 is glad he bought that "Unix for Mac OS X" book :) 15.39.08 # voltagex: Before you do that though... is RbUtil in "Applications" in the Finder? 15.39.13 # no 15.39.20 # desktop & on my h300 15.39.27 # location does not change the crash 15.39.59 *** Saving seen data "./dancer.seen" 15.40.54 # rbutil doesn't seem to like the EU version of 1.30 firmware 15.41.17 # Try with the J or K versions, then. 15.41.21 # firmware patching for h300 with rbutil works fine on windows, but i am not sure if someone tested it on Mac.. :-) 15.41.56 # domonoky: i will be your test pilot...note i had it working on Tiger, i am now on Leopard 15.43.05 # ok OSX's crash reporter has hundreds of qtcore errors from rbutil captured 15.43.19 # what do you mean with "rbutil doesnt like 1.30 EU" ? what does rbutil say for it.. 15.43.31 # Unable to detect firmware type 15.44.21 # ah, then its probably too new, rbutil has a list of hashes built in, to identify the firmwares, and check the patched result.. do be really sure its working.. 15.44.46 # new as in 4 years old? 15.44.52 # as a broken patched firmware can brick a hxxx player... (only BDM will then help) .. 15.45.20 # i just bricked one h300 by blowing a capacitor, so this is a new one which i do not want to brick 15.46.12 # have a look - http://rafb.net/p/Ua1uno99.html 15.46.39 # so nobody has done the neccessary tests, and provided the md5sums needed for the v1.30EU firmware, and as we have other working versions, nobody cares ..:-) 15.47.01 Quit saratoga ("CGI:IRC (Ping timeout)") 15.48.15 Join K4rP4D [0] (n=KrPD@unaffiliated/krpd) 15.48.36 # that paste is as much of a crash dump as i can get 15.48.40 # any help? 15.49.00 # voltagex: unfortunatly this crash log doesnt really help.. best would be to compile a debug version of rbutil and run it in gdb, and get the backtrace when it crashes... but this a bit of work.. :-) 15.49.27 # ok if you can give me the gdb commands to run 15.49.30 # so if you can compile rbutil on your mac, it would really help... :-) (i dont have a mac).. 15.49.35 # voltagex: Is your Mac Intel or PPC? 15.49.35 # i will do it 15.49.38 # as i want this thing to damn well work! 15.49.51 # yes, be aware this is only breaking on 10.5 15.50.00 # Intel, 1st gen macbook 15.50.15 # OK, I just wanted to rule out an endian problem... 15.50.30 # if you have built rbutil as debug, just run "gdb ./rbutil" then "run" and when it crashes "bt" .. 15.50.57 # actually don't think this is 1st gen but who cares 15.51.14 # ok ./configure --enable-debug right? 15.51.49 # see : http://www.rockbox.org/twiki/bin/view/Main/RockboxUtilityDevelopment 15.52.25 # use "qmake -config db" + "make" to build a debug build of rbutil.. 15.52.27 # oops ended up with an rbutil/rbutil/rbutil folder 15.52.27 # :P 15.52.38 # qmake -config dbg 15.53.33 # hmmm svn checkout still going 15.53.42 # will get on it asap 15.54.11 # take your time... building rbutil gets more and more complex.. :-) 15.54.30 # yeah don't even have qt on this 15.54.42 # only just formatted a broken 10.4 and put 10.5 on 15.54.57 Join advcomp2019_ [0] (n=advcomp2@unaffiliated/advcomp2019) 15.55.07 # you will need qt-dev, and i think lib-usb-dev... 15.55.16 # domonoky: 1.30EU is listed in h300sums.h... 15.55.36 # as a side note, linuxstb I'm still using your DVB utilities. 15.55.49 # voltagex: ;) So am I... 15.56.20 # i still want additional features but don't have the knowledge to do it myself ;) 15.58.35 Quit petur (Remote closed the connection) 16.00.52 # Buschel_relaxing: doesn't the official musepack code use it either? afaik, they have the same thing 16.01.58 # domonoky: libusb devel/libusb 0.1.12 Library providing access to USB devices 16.02.03 # that the one? 16.02.12 # voltagex: jup.. 16.02.46 # boy am i glad ports for mac exist 16.02.56 # because resolving dependencies manually sucks 16.04.23 Join kharo [0] (n=teemu@a91-153-69-60.elisa-laajakaista.fi) 16.10.47 Quit Ragnor (Nick collision from services.) 16.10.50 Join petur [50] (n=petur@rockbox/developer/petur) 16.10.57 Join Ragnor [0] (n=Ragnor@dslb-084-062-100-076.pools.arcor-ip.net) 16.11.10 Quit XavierGr () 16.12.11 # domonoky: this could take a while 16.12.14 Quit advcomp2019 (Read error: 110 (Connection timed out)) 16.12.51 # Can someone with an e200 try the test_fps plugin? When I run it, the screen goes blank. 16.12.57 # voltagex: jup :-) .. 16.16.56 # oops, doesn't happen with official r17471 16.18.29 # i need to hit the hay 16.18.44 # domonoky: can I email or do you want me to post this on a mailing list? 16.19.01 # its 12:18am here and I don't think our timezones match up very well 16.19.26 # email is fine.. 16.19.45 # PM me? 16.20.52 Nick Buschel_relaxing is now known as Buschel (n=AndreeBu@p54A3CAF0.dip.t-dialin.net) 16.21.48 # preglow: but the way it was called in rockbox the buffer was not used. when changing the source to always use the statis buffer i've had noises and freezes 16.22.46 # preglow: as far as i can see from the svn repository the static buffer was introduced via a patch. 16.23.47 Quit Mathiasdm ("Yuuw!") 16.23.53 Quit petur (Remote closed the connection) 16.24.08 Join petur [50] (n=petur@rockbox/developer/petur) 16.25.43 Quit Shaid (Read error: 110 (Connection timed out)) 16.25.49 Quit Nico_P (Remote closed the connection) 16.26.02 Join Mackes_ [0] (n=root@74.10.229.35) 16.26.03 Quit Mackes_ (Read error: 104 (Connection reset by peer)) 16.28.32 # casainho's ways certainly are unpredictable... 16.28.51 # I always told him u-boot is good while porting rockbox 16.28.55 # due to the tftp etc 16.29.01 Quit voltagex ("Lost terminal") 16.29.19 # now he seems eager to switch to full-speed usb isntead 16.37.00 Quit petur (Read error: 104 (Connection reset by peer)) 16.41.10 Join k4y [0] (i=korpse@196-209-87-157-tpr-esr-2.dynamic.isadsl.co.za) 16.41.39 Part k4y 16.42.18 Join saratoga [0] (n=9803c50e@gateway/web/cgi-irc/labb.contactor.se/x-6133f75b941c7c0d) 16.43.45 # B4gder: I don't think he can make up his mind anymore. He's all over the place. 16.44.14 # yes clearly 16.44.49 Join toffe82 [0] (n=chatzill@h-74-0-180-178.snvacaid.covad.net) 16.45.54 Join petur [50] (n=petur@rockbox/developer/petur) 16.46.00 # Actually, scratch that... He could never make up his mind. 16.50.58 Quit dabujo (Read error: 104 (Connection reset by peer)) 16.51.04 Join dabujo_ [0] (i=xx@p4FDB2738.dip0.t-ipconnect.de) 16.51.07 Quit domonoky (Read error: 104 (Connection reset by peer)) 16.51.30 Join fyre^OS [0] (n=fyre@cpe-68-173-171-53.nyc.res.rr.com) 16.53.11 Join domonoky [0] (n=Domonoky@rockbox/developer/domonoky) 16.53.32 Join Mathiasdm [0] (n=Mathias@78-22-5-158.access.telenet.be) 16.55.06 Join pabs [0] (n=pabs@xor.pablotron.org) 16.55.16 Part B4gder 16.59.12 Quit Arathis ("Bye, bye") 17.05.40 Join Horscht [0] (n=Horscht@xbmc/user/horscht) 17.08.21 Quit fyrestorm (Read error: 113 (No route to host)) 17.12.38 Join fml [0] (n=4fd3cf5a@gateway/web/cgi-irc/labb.contactor.se/x-e4ebbe2e243da0ef) 17.14.28 # He-he. With all the things done by linuxstb to port sansav2 I think we all should be buying Sansa e200 as long as the are sold! 17.15.02 # fml: I think you're over-estimating what I've done (and what I intend to do....) 17.16.25 # But the experience is that once a custom code (be it 1 byte long) can be executed, it lasts not long until any code can be executed. Especially if there is a preson behind pushing it with such energy! 17.16.52 # The whole v1 team! ;-) 17.16.53 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 17.17.24 # True ;) But the v1 team are all busy on the v1... 17.18.01 # :-) By the way: do the new Sansa e200 have file browser in their original firmware? 17.19.00 # And MSC mode? 17.19.14 # I'm pretty sure they do, but have never touched any kind of e200 17.19.57 # linuxstb: do you mean the browser or the MSC moder? 17.20.07 # Both 17.20.28 # But as I said, I've no real idea... So ignore me and wait for someone who knows. 17.21.07 # But the sansa e200 v1 doesn't have the file browser, just the database. Do you think they've changed that? 17.21.22 # It doesn't? 17.21.30 # * linuxstb retracts all previous comments 17.21.57 Quit petur (Connection reset by peer) 17.22.05 Join petur [50] (n=petur@rockbox/developer/petur) 17.22.14 # * linuxstb was misled by Sandisk's advertising - "provides everything you need for music, photo, and video clip playback. " 17.22.25 # No, not a hint of a file browser :-/ 17.22.28 Quit pabs ("leaving") 17.23.07 # And without MSC mode it would be a real &%$ 17.23.25 # saratoga: patch updated with all add-on iram to plugin/codec. works fine here 17.25.41 # linuxstb: have you talked to the sansa v1 team if they could help you on porting sansa v2? :-P 17.26.00 # fml: I can't get through - the phone is always engaged... 17.26.05 Join pabs [0] (n=pabs@xor.pablotron.org) 17.26.25 # * GodEater wasn't aware of a sansa v1 "team" 17.27.13 # linuxstb: you pick up the speaker, dial the number and it's always engaged? Weird, weird... 17.27.59 # You could try the mobile, that should work 17.28.24 Quit fml ("CGI:IRC") 17.28.34 # buschel: looks good 17.28.47 # though i don't know much about how the lds stuff works 17.28.57 # but thats what i'd done when playing around with the wma codec 17.29.01 Join gregzx [0] (n=chatzill@dtn77.neoplus.adsl.tpnet.pl) 17.29.08 # and it seems to work 17.29.12 # Buschel: how do you decide which parts get to use the newly available iram? 17.29.51 # betrik: i chose some large array which i knew are under heavy use while decoding 17.30.07 Join r0rshach [0] (n=chatzill@69.0.80.82) 17.30.14 # hi! 17.31.07 # bertrik: or are you asking for plugins vs. core? 17.32.02 # * Buschel needs to undo r17470 :/ 17.32.29 # Buschel: it was introduced via a patch, but i think official svn has the same code from the same guy (snowgoon). if rockbox didn't use it properly, why not fix that instead of removing it? 17.32.39 # if there is strange behaviour in the audiothread debug screen, there will some more in other parts of rockbox 17.33.02 # my question is kind out there, but i get the feeling rock box is capable of it... 17.33.07 # Buschel: Both. IIUC, iram is a scarce resource that could be of benefit to a lot of functions. What I mean is, how do we decide which parts DO get to use IRAM and which parts do not? 17.33.45 # or is there enough of it now? 17.33.53 # we've gotten more iram? 17.33.55 # preglow: i will have a look at it. 17.34.25 # preglow: we only use 96kB even on targets with more currently 17.34.28 # r0rshach: Just ask... 17.34.31 # I can continute taking more photos? 17.34.43 # shoot whoops 17.34.44 # bertrik: unless theres some specific need for IRAM in the core I don't see much sense in giving the core more since it uses relatively little CPU time compared to codecs 17.34.45 # one sec 17.34.53 # Buschel: anyway, i'm quite satisfied with our mpc seek efficiency as it is, i just want to keep our code as close to official as possible if there's not a good reason 17.35.18 # well, if you ask me, the best place to use iram is for codecs and some occasional core stuff 17.35.51 # Can I extract photos off my camera, w.o a pc, to my rockbox enabled player and store them in a folder? 17.35.54 # saratoga: did you have a specific target in mind for your RBaA GSoC project ? 17.36.06 # r0rshach: not currently 17.36.11 # Awwwww 17.36.15 # No USB-host. 17.36.15 Join Mackes_ [0] (n=root@74.10.229.35) 17.36.24 # r0rshach: it's on someone's todo list though 17.36.25 # that would have been so awesome 17.36.26 # r0rshach: It also depends on which player you have - the hardware may not even be capable of it. 17.36.35 # good point 17.36.43 # i got the iaudio x5 60 gigger 17.36.59 # i figure you guys were working on that 17.37.06 # ill keep my eyes peeled 17.37.45 Quit Mackes_ (Remote closed the connection) 17.38.26 Join mackes-Office [0] (n=root@74.10.229.35) 17.39.05 # r0rshach: No-one seems to be working on USB host for the X5... 17.39.10 # DOH 17.39.26 Join ali_as_ [0] (n=as@ambix.plus.com) 17.39.38 # preglow: either i am blind or the seek code is not part of the sv8 svn-version 17.39.41 # well for what its worth rockbox is still awesome as is and It makes the player way better 17.39.52 # Buschel: yeah, sv8 is simpler to seek in 17.40.04 *** Saving seen data "./dancer.seen" 17.40.13 # its cool, i can pursure other option that will accomodate me, figure it didnt hurt to ask you guys 17.40.22 # preglow: yes, but the sv7-seek stuff seems to not be included 17.40.45 # preglow: the source should support both sv7 and sv8 17.40.47 Quit das-perceptro1 ("Leaving.") 17.41.03 # weird 17.43.23 # preglow: btw, the current seek code allocates 4 bytes seek-table for each frame of the file 17.43.53 # preglow: this adds up to some 100KBs depending on duration of the track 17.43.56 Join kugel [0] (n=kugel@unaffiliated/kugel) 17.45.02 # Buschel: just curious, what kind of regression did r17470 cause? 17.45.07 # Buschel: it doesn't matter, the codec buffer is always 512 kb 17.45.25 # It would be nice to reduce it though... 17.45.46 # sure, but the mpc seek table code can change the stride in the seek table for big files 17.45.54 # so we could keep that arbitrarily small 17.48.29 # bertrik: if you were in the audiothread debug menu, it was not possible to skip one track. it always skipped 2. 17.49.17 # preglow: the stride did not work. i hardcoded the source to always use the seek table and set it to 512 entries. it crashes then. 17.49.51 # preglow: maybe the limitation to 512KB is the reason for a flyspray entry which describes playback and seek erros on long duration files >60min 17.50.48 # Buschel: if that doesn't work, it wouldn't surprise me 17.52.34 # preglow: maybe its better to limit the seek table to each 40 frames or so. this would still lead to a precision of 1 second 17.53.23 # preglow: that's what i will try. 17.55.25 # * petur discovers the patch JdGordon gave him was not what he used for the fancy screenshots.... 17.57.29 Quit ali_as (Read error: 110 (Connection timed out)) 17.57.50 # it also neatly steps around some of the key issues like different gain options depending on source :( 17.59.21 Join Evilnick [0] (n=chatzill@cpe-72-225-212-221.nyc.res.rr.com) 18.01.04 # Just taken delivery of a gigabeast 8) 18.01.28 # Time to get downloading the vmware build environment 18.01.55 # Evilnick: Ahoy there! :) 18.02.17 # Hello! I can almost do my own personal ToR now! 18.02.48 # :) 18.02.55 # So you got a Beast, too? :) 18.03.51 # preglow: Just saw your comment on FS #8680. I think the MOD codec is ready for full-time, too. 18.04.12 # I had to - I was using my iPod for too long. I'm blatantly not cool enough for that. 18.05.20 # LambdaCalculus37: yeah, there has been some reports, but nothing is happening, so i think it's time to force the issue by commiting it 18.05.49 # i'll see about it tonight 18.05.56 # preglow: I see no reason why it shouldn't be committed. I've already used it on three players with no issues. 18.06.20 # Evilnick: Want to jump onto #rockbox-community? 18.18.00 # GodEater: I was going to begin by merging in the Motorola EZX port to rockbox SVN 18.18.30 # but currently i'm somewhat stuck since I'm having a lot of trouble finding out about licensing and the build tools 18.24.40 Join bluebrother [0] (n=Dom@f053154238.adsl.alicedsl.de) 18.26.56 # saratoga: How about ignoring specific device targets for now, and start to adapt Rockbox to a generic "Unix" target platform? This could use SDL for I/O, but wouldn't be a simulator of any specific target. 18.28.32 Quit ctaylorr (Read error: 110 (Connection timed out)) 18.30.32 Join ali_as [0] (n=as@ambix.plus.com) 18.31.06 # preglow: Are you still interested in a backup h120? http://cgi.ebay.com/NEW-iRiver-H120-mp3-player-20gb-H-120-i-river-20-gb-NR_W0QQitemZ320249233415QQihZ011QQcategoryZ114622QQssPageNameZWDVWQQrdZ1QQcmdZViewItem 18.31.17 Quit petur (Remote closed the connection) 18.31.32 Join petur [50] (n=petur@rockbox/developer/petur) 18.31.40 # * scorche|sh glares at linuxstb 18.31.52 # * linuxstb credits scorche|sh for the link 18.32.06 # * scorche|sh thinks about sniping it before preglow gets a chance 18.32.14 # They have more than one... 18.32.25 # oh...missed that :) 18.32.36 # * scorche|sh apologizes to linuxstb for the glare 18.34.19 # er, I'm getting some FPA errors when building the beast bootloader, with a brand new vmware image. Any ideas? 18.35.30 # The brand new vmware needs updating... 18.35.44 # linuxstb: nah, i think i'll just drop that 18.35.52 # scorche|sh: go ahead :) 18.36.04 # For a linux novice; can you let me know the commands needed? 18.36.06 # Evilnick: You'll need to run rockboxdev.sh to rebuild the ARM compiler. 18.36.18 # Marvellous. 18.36.56 # Or you could just ask someone to give you a beast bootloader... 18.37.12 # Evilnick: sorry about that...been meaning to update that image 18.37.45 # Well, I was trying to go the "teach a man to fish" route, rather than being too grasping... BUT, does anyone have the bootloader? And the sendfirm utility? 18.37.53 # And a car? 18.39.03 # You can build the sendfirm utility - you don't need arm-elf-gcc for that. 18.39.28 # Although you'll need libmtp.... I think someone had a download of that as well - you could search the IRC logs. 18.39.58 Join krazykit [0] (n=kkit@adsl-76-240-192-86.dsl.ipltin.sbcglobal.net) 18.40.00 # This is from gevaerts - http://www.evonet.be/~gevaerts/sendfirm 18.40.20 Join Synergy6 [0] (n=Synergy6@0-1b-24-4c-ae-79.hb.esol.dur.ac.uk) 18.40.30 # Thanks linuxstb 18.41.09 # bye 18.41.12 Quit Buschel () 18.43.53 Quit DaCapn () 18.45.55 Join OlivierBorowski [0] (n=OlivierB@ANancy-157-1-10-160.w86-204.abo.wanadoo.fr) 18.48.00 # where is rockboxdev.sh located? Is it in the svn checkout? 18.48.10 # Yes, in tools/ 18.48.20 Quit ali_as_ (Connection timed out) 18.50.10 Quit toffe82 (Connection timed out) 18.50.35 Join mf0102 [0] (n=michi@85.127.21.196) 18.52.16 # and should I update all architectures? 18.53.22 # Yes, do so. 18.55.40 Join BigBambi_ [0] (n=Alex@rockbox/staff/BigBambi) 18.58.15 Join BlakeJohnson86 [0] (n=bjohnson@c-24-118-135-22.hsd1.mn.comcast.net) 19.00.10 Quit BigBambi_ (Remote closed the connection) 19.00.16 Quit BigBambi (Remote closed the connection) 19.00.32 Join BigBambi [0] (n=Alex@rockbox/staff/BigBambi) 19.06.04 Join toffe82 [0] (n=chatzill@h-74-0-180-178.snvacaid.covad.net) 19.06.06 Quit linuxstb (Read error: 110 (Connection timed out)) 19.06.25 # opinion requested: where's the nicest place to specify that an ARM target supports unaligned access? autoconfig.h or config*.h. It may or may not need to be turned on in system setup so it's not simply based on chosen CPU. 19.09.23 # why would we want that? :> 19.12.20 Join oswald_rocker [0] (n=simon_so@189.168.57.30) 19.13.56 # preglow: just load words starting at any address like with mpeg parsing 19.14.13 Part oswald_rocker 19.14.44 # it's faster to let the hardware do it than mask and shift afterall 19.20.34 # maybe I'll just make it compulsory for arm1136 (along with mixed-endian support) 19.22.04 Join Vorador [0] (n=tomas@lan-84-240-35-19.vln.skynet.lt) 19.22.09 Join fml [0] (n=4fd3cf5a@gateway/web/cgi-irc/labb.contactor.se/x-35524e4757602572) 19.22.25 Quit daskhweg (Read error: 110 (Connection timed out)) 19.22.28 Join daskhweg [0] (n=l3ech@bzq-79-181-253-207.red.bezeqint.net) 19.24.03 # Hi. Do you know that flyspray (your bug tracker) registration is currently broken? 19.34.30 # LinusN: ping (see ^) also the http://www.rockbox.org/tracker/ page is blang and Bagder blamed your upgrading of php ;) 19.34.45 # s/blang/blank/ 19.35.00 Join Synergy66 [0] (n=Synergy6@0-1b-24-4c-ae-79.hb.esol.dur.ac.uk) 19.35.23 Quit Synergy66 (Client Quit) 19.36.25 Join simonrvn_ [0] (i=simon@unaffiliated/simonrvn) 19.38.37 Join gevaerts_ [0] (n=fg@195-144-092-136.dyn.adsl.xs4all.be) 19.40.07 *** Saving seen data "./dancer.seen" 19.41.17 Quit simonrvn (Nick collision from services.) 19.41.18 Nick simonrvn_ is now known as simonrvn (i=simon@unaffiliated/simonrvn) 19.42.21 Quit r0rshach ("ChatZilla 0.9.82 [Firefox 2.0.0.14/2008040413]") 19.42.22 # There is a patch about anti aliased fonts. Does this mean that rockbox can have them in a not so far future? Or is it a 'nodo'? 19.43.53 # depends on who you ask :) 19.44.07 # fml: it's quite controversial ... there was a (more or less) lengthy discussion a few days ago 19.44.09 # font aliasing is discussed very controversal, many think its too much bloat for too less gain.. 19.44.33 # (search for amiconn thinking about forking) 19.44.41 # me too thinks it's bloat. 19.44.50 Join austriancoder [0] (n=austrian@rockbox/developer/austriancoder) 19.45.16 # Now the main question is who is "many." If they are the core developers then there is little chance 19.45.30 # * jhMikeS has though about forking too in order to support more capable hardware without restriction 19.45.42 # * preglow doesn't feel very strongly about anti-aliased fonts 19.45.55 # But I think the modern player have got enough RAM to have that. And that would allow nice fonts to be implemented. 19.46.20 # ipod video OF has antialiased fonts so I don't know why it would be a huge burdon 19.46.46 # I think even e200R OF does IIRC (have to look again) 19.46.53 Join atm [0] (n=atmb4u@117.196.130.42) 19.46.55 # fml: you never have enough ram and cpu, and there are better ways to spend cpu and ram, as for fonts.. 19.46.59 # But IMHO forking would be a pity 19.47.03 # indeed 19.47.18 Part atm 19.47.20 # if someone has time.. please review: http://www.rockbox.org/tracker/task/7138?getfile=16543 19.47.34 # http://www.osnews.com/story/19731 19.47.36 # err 19.47.40 # doh, misfire 19.47.40 # sorry 19.47.43 # domonoky: for example? 19.48.31 # fml: how about dsp plugins.. :-) 19.48.46 # austriancoder: have you seen the reports of problems with bass and treble setting son some players since your last commit? 19.48.54 # * preglow wants his relocatable plugin format, then 19.49.00 # doesnt the ipod OS fake the antialiasing with their always white background ? 19.49.17 # alpha blending! 19.49.26 # n1s: yes... but it i need to contect a device owner to check some stuff 19.49.50 # domonoky: My understanding though is that it continues working even with iPodwizard used to change backdrop images. But this is just what I've heard. 19.49.54 # * jhMikeS thinks fair amount of nice graphics stuff can be implemented frugally 19.49.57 Join ompaul [0] (n=ompaul@gnewsense/friend/ompaul) 19.50.46 # Couldn't we implement a somewhat reduced anti aliasing, i.e. only for a one-color-background? So when the font is loaded, it's "precalculated" for that background color 19.50.55 # * jhMikeS always means "implement" as in "nothing cut in capability" too 19.51.33 # fm1: I would never do it with anything less than blendable with anything or there no real point imho 19.51.36 # Have you guys tried the antialiased font patch and found it wanting, or just throwing alternate hypothesis around in advance? 19.52.43 # Llorean: I once wanted to create a font larger that nimbus14. Without anti aliasing, the next possible size was 19. A big step. 19.52.54 # alpha isn't really very CPU-intensive anyway 19.53.19 Quit Synergy6 (Read error: 110 (Connection timed out)) 19.53.43 Quit gevaerts (Read error: 110 (Connection timed out)) 19.53.56 Join Nico_P [50] (n=nicolas@rockbox/developer/NicoP) 19.54.19 # jhMikeS: Well the existing patch is used by a couple of unsupported builds for the Sansa which is probably, what, 3rd slowest color target because of its (relatively) large screen? 19.54.19 # fml: still, it increases code size and complexity. So ... 19.54.29 # fml, you can check clR6x12-(12) font (Grey Scale theme -> http://iaudiophile.net/forums/showthread.php?t=14918) which looks pretty good even without anti aliasing and silk nano icon theme ;) 19.54.52 # if we are to implement alpha blending, we should surely do it properly, no hacks 19.54.57 # Llorean: I have not tried the patch. But I've seen enough comparisons of anti aliased vs. no anti aliased. And AA looks way better. 19.54.59 # no one forces you to use it anyway 19.55.17 # bluebrother: sure. But it also gives you something. 19.55.46 # fml: If you haven't seen it on-player, comparing antialiased and normal versions of the same font, I don't see at all how you can say it looks "way better" 19.55.57 # The screens of the players make a significant difference. 19.56.10 # sure. The big question is if it's worth the price. 19.56.38 # IMO it would be much better to concentrate on making the current state better -- i.e. squash bugs etc. But I also think a release would be nice. 19.57.24 # only adding new features all the time only tends to make the code unmaintainable. Or at least makes that much harder. 19.57.37 # is a m:robe 100 owner online? 19.57.47 # austriancoder: yes :) 19.58.19 # Vorador: the small font is too small for me, and in the large, I dont't like the round pieces, e.g. lower left rounding of 'e' and 'a' 19.58.42 # austriancoder: Would you have any idea why we've got many users saying they can't save bass/treble settings? They can set them, but they don't get saved on shutdown, at boot up they're not working. 19.58.51 # Llorean: but it's also a target with a memory framebuffer so really it's not slow at all 19.59.02 # * domonoky raises hand (for the m:robe100) 19.59.16 # Llorean: i am checkig it atm 19.59.18 # bluebrother: properly implemented, it should have no impact at all on the main app code. 19.59.32 # bluebrother: cool - can you help me in debugging this: http://forums.rockbox.org/index.php?topic=16719.0 19.59.40 # austriancoder: Reports have come in on m:robe100, a few iPods, and I think the sansa. 19.59.50 # I know, the best way is to make a patch and see how the others find it. So I'll shut up. 19.59.56 # and I just looked and the e200R has antialiased font and seems to run quite well with it 19.59.57 # Llorean: sansa is working... i have one 20.00.07 Join hannesd [0] (n=light@p5B16411B.dip0.t-ipconnect.de) 20.00.08 # I'm getting further in putting rockbox on my beast, but now having updated the dev environment so that i can build the bootloader, I get a "fatal: kernel too old" then a segmentation fault. I've used the sendfirm from gevaerts 20.00.14 # fml: added functionality always has an impact -- at least code size and cpu usage, even if it's quite low. 20.00.20 Join einhirn_ [0] (n=Miranda@p5B032A0D.dip0.t-ipconnect.de) 20.00.24 # austriancoder: Well there's two e200 users in the forums for whom it's not working. They can set bass/treble, but it doesn't save across shutdowns. 20.00.40 # Okey, anyone with iAudio X5 here? 20.00.56 Quit hannesd (SendQ exceeded) 20.00.57 # * jhMikeS has one 20.01.26 # ...and it's still the best sounding player I've got 20.01.34 # jhMikeS: I was just basing it on mpegplayer performance, since that's the only approximation I've got for "overall performance" right now. 20.01.38 # Llorean: ahh.. thats something different.. doesnt save settings across shutdowns.. but here i have made no change... 20.01.50 # Can you take a look at -> http://iaudiophile.net/forums/showthread.php?t=14918 20.01.53 # austriancoder: you're referring to the diff you posted? Can you / someone (domonoky?) provide me a build? I'm not on my usual development environment (doing some w32 tests for rbutil) 20.01.57 # Urgh, redness... 20.02.03 # bluebrother: with that philosophy, we should cut away 80% of rockbox code and have it small and cute. 20.02.05 # Wrong link sorry. 20.02.12 # austriancoder: I said "doesn't save the setting across shutdowns" in my first statement to you too. It's just bass/treble, and reports started coming in since that one change of yours. 20.02.15 # Here -> http://forums.rockbox.org/index.php?topic=16809.0 20.02.17 Join hannesd [0] (n=light@p5B16411B.dip0.t-ipconnect.de) 20.02.24 # bluebrother: I will give you one.. 20.02.29 # fml: right. But as I said earlier, the main question is if it's worth the price. 20.02.50 # Llorean: ok 20.03.23 # fml: No, with that philosophy we need to weigh carefully any new feature vs its cost in binsize increase, cpu load, and code complexity. Antialiasing is an incredibly minor feature, over all, in terms of visual change. Especially on very small screens (which are most of them) 20.04.14 # bluebrother, Llorean: you always win 20.04.17 # jhMikeS? 20.04.27 # Vorador: mine is definitely black with the backlight turned off (which means graphical display is powered down but not the whole chip) 20.04.50 Join jgarvey [0] (n=jgarvey@cpe-024-163-032-204.nc.res.rr.com) 20.04.51 # basically it looks just like it does when its off 20.05.05 Quit gevaerts_ ("Lost terminal") 20.05.06 Quit fml ("CGI:IRC (EOF)") 20.05.07 # Is there any way to not turn off the screen when backlight is off? 20.05.48 # * Llorean would like it to be noted that he, personally, is in favour of antialiasing being included if it can be done so in an efficient way, but nobody actually asked his opinion on the matter, just continued to make statements he had objections to... 20.05.50 Quit hannesd (Client Quit) 20.06.01 # Evilnick: Try using wget to save the file directly in the environment. 20.06.21 # Vorador: you're saying yours looks different when the backlight turns off that it does when powered down? 20.06.22 Join Lear [0] (i=chatzill@rockbox/developer/lear) 20.06.36 # Yes. 20.06.41 # Anyone know how I build checkwps? 20.06.53 # * jhMikeS wonders how that's possible 20.07.36 # pondlife, read the readme in tools/checkwps ;) 20.07.38 # pondlife: just run make? 20.07.42 # And are you sure your screen turns off completely? 20.07.53 # ..when backlight is off. 20.08.12 Quit Reinhart (Read error: 104 (Connection reset by peer)) 20.08.19 Quit markun (Read error: 113 (No route to host)) 20.08.23 # * bluebrother wonders if he committed the changes to the checkwps makefile to make building easier 20.09.12 Join bluebrother^ [0] (n=Dom@f053154178.adsl.alicedsl.de) 20.09.24 # hmm. No, I didn't. 20.09.24 Join linuxstb [0] (n=linuxstb@rockbox/developer/linuxstb) 20.09.29 # Still getting the same error message. Anyone know how to install libmtp so I can build sendfirm myself? 20.09.35 # pondlife: run buildall.sh 20.09.50 # Vorador: it does and the datasheet procedures were followed to the letter for both visible display poweroff and standby mode. could be that some hardware change happened along the line. 20.10.04 # Evilnick: sudo apt-get install libmtp libmtp-dev 20.10.24 # any objections against me making checkwps build a bit easier? 20.10.40 Quit bluebrother (Nick collision from services.) 20.10.43 Nick bluebrother^ is now known as bluebrother (n=Dom@rockbox/staff/bluebrother) 20.10.48 Join Reinhart_ [0] (i=wizard@chime.student.utwente.nl) 20.10.51 # bluebrother: please do :) 20.10.52 # jhMikeS: Good news... toffe82 successfully repaired my Beast! 20.11.01 # LambdaCalculus37: awesome! :) 20.11.19 # jhMikeS, and is there any way to get the old behavior when the screen is not turned off when blacklight is off back? 20.11.21 # I have to seriously update the bootloader though; I'm about 9 versions behind. :) 20.11.23 # :) 20.11.31 # LambdaCalculus37: :) BTW, there is an errate for the mc13783 that may have to with that problem 20.11.34 # *backlight 20.12.02 Join SliM1 [0] (n=stefan@62.217.213.161) 20.12.16 # Vorador: removing a couple #defines in the config file should do it 20.12.33 # Could you send me a patch ;) 20.13.27 # Vorador: try disabling lcd sleep, general settings -> display 20.13.27 # [someday] 20.13.30 # jhMikeS: Is it okay to use a single-boot bootloader, or still stick with a dual-boot bootloader? 20.13.37 Join DaCapn [0] (n=dacapn@host-126-115.dhcp.pdx.edu) 20.14.03 # Doesn't work for me. 20.14.09 Quit Mathiasdm ("Yuuw!") 20.15.01 # n1s: this sounds just bizarre to me that it should differ at all from having the power turned off 20.15.31 # jhMikeS: well, yes it sounds kind of odd :) 20.15.33 # LambdaCalculus37: not if you want to charge but that's being worked on atm 20.15.42 # jhMikeS, I can make a video for you if you don't believe me ;) 20.16.00 # Vorador: I would like to see that, yes 20.16.03 # What version of Debian is the VMware image based on? 20.16.32 Join at1 [0] (n=atmb4u@117.196.132.50) 20.16.45 Part at1 20.17.09 Part SliM1 20.18.25 # :) 20.19.09 # bluebrother: http://www.christian-gmeiner.info/rb/rockbox-17273.zip and http://www.christian-gmeiner.info/rb/rockbox-r17475.zip -> change bass/treble settings and look which values are different from version to version (logf) 20.20.43 # Nico_P: http://pastebin.com/m63e11602 20.21.03 # I must be missing something... 20.21.50 # Vorador: http://rafb.net/p/wb8TPU14.html (not tested but it should be enough to disable the powermangement there) 20.22.24 # LambdaCalculus37: I am surprised it is still working ;) 20.22.31 # Thanks, I'll test it soon. 20.23.03 # * jhMikeS wonders why the sleep timer stuff was moved to the target backlight code (this makes no sense at all) 20.24.34 Quit moos ("CGI:IRC") 20.24.54 # toffe82: Because it's running Rockbox and is really happy. :) 20.25.12 # bluebrother: Any hints on how I can compile checkwps... under Cygwin, note. 20.25.35 # pondlife: give me a couple of minutes -- I'm about to check in a change to checkwps. 20.25.40 # OK 20.25.59 # I haven't tested it on cygwin but it allows me to build it fine on MinGW, so I guess it should work on cygwin too 20.26.30 Quit DaCapn () 20.27.27 # I have probably just broken checkwps.c, but can't build to check. You should have const char* parameters on load_remote_wps_backdrop() and load_wps_backdrop(). 20.27.35 # I can commit uncompiled if you like 20.27.45 # * jhMikeS tasers amiconn over the commit that did that 20.28.53 # austriancoder: ok, it works fine with r17273. About to check the other revision now 20.29.31 # bluebrother: fine.. can you note the b: and t: lines from logf? 20.30.27 # pondlife: committed 20.30.33 # Thanks 20.30.35 # * jhMikeS wonders how many 5.5g owners haven't noticed the removal of the ata locking hack yesterday 20.31.42 # some have? 20.32.04 # Nico_P: none I know about actually 20.32.43 # I've had some dropouts at one point. looking at the buffering debug screen, they happened when the "real" value became negative 20.32.59 # ...which shouldn't happen of course 20.33.12 # Nico_P: I see that happen there quite often 20.33.13 # austriancoder: no changes with r17475. Will retry, as logfdump seems to have hung 20.33.48 # jhMikeS: yes, me too. this time was special though, as the value remained negative for longer than usual and caused the PCM buffer to empty 20.33.49 # Nico_P: should any values become negative? :) 20.34.04 # Surely not... 20.34.42 # also loading time seem longer to me, but that might just be an impression 20.36.27 # austriancoder: the logf only contains button events -- at least the r17475 build 20.38.27 # Nico_P: I've never measured variation here and there more than a couple seconds with or without and that was before serializing metadata loading. 20.38.51 Quit XavierGr () 20.39.02 # bluebrother: hmm.. maybe i did something wrong with logf usage http://pastebin.com/m218e1b99 20.40.06 # bluebrother: I think i have found the mistake 20.42.47 # Now this is weird. For some playlists (not all), resume (via bookmark or otherwise) will often cause a crash/freeze, but only if the resumed track is on the microSD (e200). The track plays fine if I don't resume. Anyone with a suggestion on what it might be caused by? 20.43.56 # bluebrother: I have commited a fix.. could you test latest build, when it got compiled? 20.44.06 # sure 20.44.24 # scorche: Could I request that the vmware image be built with the updated build environment and if possible with libmtp and dependencies preinstalled? 20.44.54 # Whenever you have time, obviously. 20.45.16 # yeah 20.45.48 Nick advcomp2019_ is now known as advcomp2019 (n=advcomp2@unaffiliated/advcomp2019) 20.46.11 Join XavierGr [0] (n=xavier@rockbox/staff/XavierGr) 20.48.05 Quit Llorean (Read error: 104 (Connection reset by peer)) 20.48.50 Join ikari [0] (n=53be794d@gateway/web/cgi-irc/labb.contactor.se/x-0ca0f68e844c5190) 20.49.31 Join mcuelenaere [0] (n=mcuelena@rockbox/developer/mcuelenaere) 20.52.40 Join Llorean [0] (n=DarkkOne@adsl-69-154-187-90.dsl.hstntx.swbell.net) 20.59.07 # Bagder: what do you think about adding a diffstat output at the top of the svn commit mail notifications? 21.00.01 Join markun [0] (n=markun@bastards.student.ipv6.utwente.nl) 21.00.07 # * austriancoder Build should have been done 8m 44s ago, at 20:51:02 21.02.27 # * linuxstb sees austriancoder has broken the build system... ;) 21.03.02 Join lee-qid [0] (n=liqid@p54967E7B.dip.t-dialin.net) 21.03.26 # that too? :p 21.04.27 # Hmmm, increasing the dircache stack size seems to have helped... 21.04.33 Join das-perceptron [0] (n=fabian@e176107205.adsl.alicedsl.de) 21.06.08 Join matsl [0] (n=matsl@1-1-4-2a.mal.sth.bostream.se) 21.06.49 # Lear: helped for what? 21.07.25 # i've noticed tthe build system doesn't really seem to make good use of my CPUs 21.07.31 # * linuxstb notices new warnings for checkwps for the touchpad targets (D2 and the music wardrobe 500) 21.07.40 # i think it averages maybe 20% CPU while running 21.08.20 # make -j2 21.08.41 # this is with make -j 4 21.08.49 # oh 21.10.33 Quit K4rP4D ("Leaving") 21.11.56 # Nico_P: Playlist resume problem. 21.13.48 # is the build server hanging? 21.14.54 # looks like it got kicked 21.14.54 Join gevaerts [0] (n=fg@rockbox/developer/gevaerts) 21.15.09 # it kicks itself after a timeout IIRC 21.15.13 Join K4rP4D [0] (n=KrPD@unaffiliated/krpd) 21.15.21 # could someone with a 128k IRAM Coldfire target (X5?) try buschel's patch? 21.15.24 # andd that didn't help it seems 21.16.11 Quit saratoga ("CGI:IRC (EOF)") 21.16.35 Join saratoga [0] (n=9803c50e@gateway/web/cgi-irc/labb.contactor.se/x-35dc29bf281b10d2) 21.17.27 # saratoga: Does it affect iaudios? Looking at the .lds files, IRAM seems to already be split 64KB/64KB on the X5/M5. 21.18.55 # linuxstb: ah didn't realize that was already resovled 21.19.11 # out of curiosity, do you know if we use the extra IRAM in core on that target? 21.19.21 # it would be nice if we could also use that IRAM for codecs 21.19.41 # No, I've no idea how much core IRAM any of the targets use. "someone" should find out... 21.20.00 # i assume thats as easy as checking the .map files? 21.20.07 # At least the codec and main stacks are always in IRAM - about 9KB each IIRC. 21.20.10 # Yes. 21.20.21 # Plus I think the mem* functions are there (memset, memcpy etc) 21.20.31 # And mono targets put the lcd framebuffer in IRAM... 21.21.20 # do we not have map files on the builds page anymore? 21.21.28 # I was just thinking that... 21.22.06 # Ah, seems they are on the "old" daily builds pages - e.g. http://www.rockbox.org/dl.cgi?bin=ipodcolor 21.22.10 # Ah we used to have map files? I wondered sometimes about that being useful to diagnose data and prefetch aborts 21.23.37 # Slasheri: I get indications that the dircache size is too small, though I'm not sure why that would help after initial dircache build (could be that it moves things around in memory, hiding another problem that way). Any thoughts? 21.23.55 Quit matsl (Read error: 104 (Connection reset by peer)) 21.24.52 # saratoga: h140 for example is using 0xbe04 bytes (out of 0xc000 bytes) - so almost all of the 48KB. 21.25.03 # i get 50KB used for the x5 21.25.24 # Is the lcd framebuffer in IRAM on the x5? 21.25.50 # Ah, no it's not. 21.27.07 # is speex in IRAM on the other targets? 21.28.19 # linuxstb: but it probably has the 2bit remote buffer in iram 21.28.26 # n1s: Yes, it does. 21.28.56 # actually i think i misread that 21.29.09 # assuming stack_end is the address of the end of the stack its only using 48KB 21.29.24 # in which case maybe the 48/80k split could be used on the X5 too 21.29.53 # I make it 0xa3e4 bytes - so well under 48KB (0xc000) 21.30.25 # then lets do the same for coldfire, so that the arm stuff buschel and I are doing help the X5 too 21.30.55 # We should check the M5 as well - that probably has the (greyscale) framebuffer in IRAM... 21.32.19 # * preglow wtfs 21.32.32 # when trying to build ordinary builds now, naggage about a missing sysfont.h happens 21.32.44 # that was fixed yesterday i think 21.32.49 # i just svn upped 21.32.51 # make veryclean and try again 21.32.59 # or maybe rerun configure 21.33.01 # 0xbcb8 bytes on the M5 - so under 48KB as well... 21.33.05 # i just tried that... 21.33.07 # well, i'll try again 21.33.08 Quit nplus (Read error: 104 (Connection reset by peer)) 21.33.14 # preglow: have you added anything to SOURCES that doesn't exist? 21.33.33 # n1s: perhaps i've typoed, but even so, why would this happen then? 21.33.46 # old buildsystem bug 21.34.01 Join amiconn [50] (n=jens@rockbox/developer/amiconn) 21.34.06 Join matsl [0] (n=matsl@1-1-4-2a.mal.sth.bostream.se) 21.34.31 # see fs#7583 21.35.05 # maybe it's time to poke Bagder again ;) 21.35.12 # n1s: i've added a file, and it seems to cause what you say, but it exists :/ 21.35.19 # no, it does not 21.35.29 # target/targer, same thing! 21.35.39 # n1s: annoying bug, that 21.35.49 # n1s: but thanks for the heads up 21.37.00 # i really need to find 3 straight hours when no one will bother me so i can work on the imdct in arm assembly 21.37.11 # i just suck so much at assembly though 21.37.28 # well, using it is good traning :) 21.37.31 # training too 21.37.38 # amiconn, good that I found you: The iRiver remote clock still seems to work too fast for some models (including mine) 21.37.57 # I know... 21.38.29 # Would it be possible to slow it down a little more? Is there anything that I can help for "debugging"? 21.38.45 # * amiconn needs to prepare a set of test builds 21.40.08 *** Saving seen data "./dancer.seen" 21.41.06 Quit mackes-Office ("Ex-Chat") 21.42.09 Quit austriancoder (Read error: 113 (No route to host)) 21.42.19 # amiconn, good luck on that and thanks. If there is anything the owners of the affected devices can look up for you, please post in the bug list. Bye. 21.42.26 Part das-perceptron 21.45.39 Join Mathiasdm [0] (n=Mathias@vpnb125.ugent.be) 21.46.05 Join tkooda [0] (i=goaway@box.wtf.la) 21.50.18 Quit GodEater_ ("+++ OK ATH OK") 21.51.43 # I recently had my F40 stolen. in looking for another F40, it looks like some 40GB iPod's are cheaper (and I think I like the wheel interface better than the gigabeat's cross), can anyone comment on weither or not I should get an iPod (4th gen?) instead of another Toshiba Gigabeat F40? 21.52.19 # any known issues with 4th gen ipod (didn't see any on the site) 21.52.22 # ? 21.53.39 # tkooda: I would recommend the gigabeat over the iPod any-day 21.53.48 # why? 21.53.57 Join hcoal [0] (n=hcoal@unaffiliated/hcoal) 21.54.12 # It's faster in terms of decoding the audio files, connecting/disconnecting to USB. 21.54.38 # However, the iPod does have a nicer screen (in terms of alignment anyway) 21.54.50 # And far more support from case manufacturers etc! 21.54.59 # I know the GB's got a faster cpu.. but presuming it plays the same audio (and I don't need mpeg2 video)... 21.55.18 # how long does the ipod take to mount via usb? 21.55.28 # Depends. 21.55.36 # on? 21.55.40 # I also think that the wheel isn't a very nice way to navigate. I've used an ipod video for a few months and I will still overshoot way more often 21.56.22 # tkooda: They don't play the same audio equally well. If you turn on too many DSP features and have a complex WPS you can experience playback dropouts on the iPod. As well, higher complexity formats (AAC+SBR, Monkey's Audio) won't play at all on iPods. 21.57.33 # is there any other hdd player recomended over the F40? 21.57.56 # The Gigabeat S, although that port needs a little more work. 21.58.16 # The Gigabeat S is just coming into its own, though the install process is still a bit complicated, and the port is in the early stages of being usable so not *everything* works well yet (for example, charging should still be done in the OF) 21.58.25 # tkooda: the short summary is that it entirely depends on you 21.58.26 # Imho it all depends on what you want to do/use 21.58.49 # * jhMikeS is still yelling at powermgmt.c 21.59.06 # * amiconn deems the iriver H1x0 series the most versatile hdd based rockbox target 21.59.18 # * Llorean seconds amiconn's opinion there. 21.59.28 # * LambdaCalculus37 goes home 21.59.29 # Versatile for audio, especially. 21.59.38 # * gevaerts thinks that ebay prices of the H1x0s confirm that opinion 21.59.46 Quit LambdaCalculus37 ("CGI:IRC 0.5.9 (2006/06/06)") 21.59.53 # amiconn: have you seen the block diagram of the hdd6330 ? 22.00.04 # * jhMikeS likes his H120 for recording by far over anything else 22.00.21 # No, why? 22.00.28 # they'll never make one like that again 22.00.45 Quit Evilnick ("ChatZilla 0.9.82 [Firefox 2.0.0.14/2008040413]") 22.00.59 # amiconn: to see if it is like something you know with a pp (some component...) 22.01.33 Quit hcoal ("leaving") 22.02.19 # tkooda: My ear's aren't the best, but the Gigabeat sounds better than the 4th Gen ipod to me. I can't tell a difference between the 5th gen ipod and the Gigabeat though. 22.02.30 # philips make a dock which is compatible gogear and ipod with the difference of the connector 22.02.31 # (but others claim the Gigabeat sounds better) 22.02.49 # iriver h1x0's seem expensive on ebay, or only like 20GB 22.07.03 # jhMikeS: powermgmt.c needs a fundamental inside-out rework anyway 22.07.46 # That's a requirement for g1/g2 suspend, proper iaudio power management, ... 22.07.56 # i have high hopes for the S as a HD based player, the button layout on it is quite nice 22.08.20 # none of that touchpad nonsense 22.08.40 # * Llorean will probably always prefer discrete buttons. 22.09.11 # * amiconn too 22.09.22 # me too, i guess 22.09.39 # I've never got on with the h1x0's joystick though. 22.09.58 # I used my new "super-mini" this weekend, and while it's really nice to be able to carry all my music on such a small and robust device, the wheel always annoys me 22.10.16 # amiconn: I'm ready to move on it due to the new charging algorithm required for the beast 22.10.44 # try to the gogear serie and you will like better the discretes buttons 22.10.53 # i'm really surpised the S has software charging, i'd think that'd be too dangerous 22.11.27 # jhMikeS: Basically, the inner loop should call the various functions, instead of the current method to implement the more frequent task as the "sleep function" for the once-per-minute tasks 22.11.57 # That's a pretty fundamental change though, and needs testing on all targets, especially recorder v1 (software NiMH chargign) 22.12.26 # saratoga: I think it's software charging with hardware protection 22.12.28 # saratoga: why would it be too dangerous? 22.13.02 # * preglow wonders why anyone would implement software charging 22.13.13 # tons of nice cheap charging chips around 22.13.15 # * amiconn wouldn't dare coming too close to a purely software charged LiIon cell 22.13.18 # because if you put too much current into a lipoly battery they catch fire and then cause lawsuits 22.13.51 # saratoga: why program it to put too much current in? :) 22.14.00 # * linuxstb resurrects the "torch" plugin 22.14.17 # The iaudio X5 and M5 have kinda hybrid charging. All basic charging control is done by hardware (the PCF), but in order to get 500mA USB charging, we need to implement software control 22.14.24 # * bertrik points linuxstb to the fireworks plugin 22.14.25 # Otherwise it will only charge at 100mA 22.14.32 # the "too much" point for current varies as a function of temperture and charge cycle, so its more a case of failing to not program too much current 22.14.55 # * preglow sees his first sd card attempts fail 22.15.13 # saratoga: it's has current and temperature readout. the Lion cell charging really isn't that difficult 22.15.26 # hardware charging is fail safe, since it typically involves a dedicated gate array that watches the temperture and voltage level 22.16.03 # what happens if the player crashes? does the charging circuit disengage if the CPU stops talking to it? 22.16.10 # My main concern isn't that the algorithm miscalculates something, but that the software crashes, leaving a high charging current set without control 22.16.13 # it's not much different from PP or x5 in that you turn on the charging current by software 22.16.38 # thats basically hardware charging then . . . 22.16.39 # it has a voltage limiter and then you watch battery current for the constant voltage phase. 22.16.40 # But if the charging voltage is capped properly, there is no problem 22.16.48 # (in hardware) 22.16.57 # but you must turn the charger off in software once it's done 22.17.04 # amiconn: sure about that? what voltage would be safe then? 22.17.26 # as long as the hardware is throttleing the current and not the software, its more or less a hardware charger 22.17.40 # the battery will slowly rise above the limit in order to continout past the constant current stage 22.17.43 # since you can't really over charge such a system 22.17.50 # bertrik: I mean in hardware, of course. The exact LiIon end-of-charging voltage is temperature and model dependent 22.18.22 # you can and you never leave Lion batteries trickly charging, you stop charge and let them drop again to about 4.05V and then top off again 22.19.36 # amiconn: so to properly charge you need a table of end-of-charging voltages vs. temperature? 22.20.02 # * jhMikeS is glad to be able to use a charge current readout to make things simpler. :) 22.20.19 # bertrik: No, you need a chip that controls end-of-charge voltage, matching the cell 22.20.34 # ...and in good thermal contact with the cell 22.21.26 # I am looking at charging for the e200/c200's that use a AS3514 for charging but I'm getting confusing results 22.22.02 # I can configure a max. charging current and charging voltage, but there's no mention of temperature factoring into that, except for a high-temperature safety of course 22.22.43 # hmm 22.22.49 # Lion packs have safety circuitry built in to keep things in safe limits. this gives a charging algorithm for Lion: http://www.panasonic.com/industrial/battery/oem/images/pdf/panasonic_liion_charging.pdf 22.23.03 # * amiconn thinks doing that properly needs a little OF RE 22.24.03 # On a data abort on the arm, does the address readout say anything useful? 22.24.25 # Lear: well, yeah, where it happened 22.24.26 # It should be the address of the instruction that caused the abort 22.24.31 # i think most people just assume a constant temperture when charging and expect the hardware to cut out if it gets too hot 22.24.41 # Lear: at least i think i fixed it up so that it's the correct address 22.25.33 # The AS3514 does have an end-of-charge bit, but it seems to become active before reaching the configured voltage. In some cases it doesn't become set at all (e.g. when charging a battery that is already quite close to the max. charge voltage). 22.25.43 # Hrm, so would an abort in crt0-pp make sense? 22.25.53 # Of course you can get a data abort (indirectly) from stack corruption as well 22.25.57 # hmm blackhawk made a random post about getting rockbox running on his ezx without using the motorola QTE headers at all, but rather some native linux api 22.26.04 # i really need to find this guy 22.26.07 # Sorry, read wrong... 22.26.11 # bertrik: it's quite the case that if a battery is too close to max it shouldn't start the charging cycle at all. 22.26.45 Join evilnick [0] (n=chatzill@cpe-24-193-67-165.nyc.res.rr.com) 22.26.55 # jhMikeS: unfortunately, how close is not mentioned in the data sheet 22.27.11 # buffering.c seems like it. Makes sense, as it happens during buffering... 22.28.26 # bluebrother: Did you test your checkwps Makefile change on cygwin? 22.29.02 # linuxstb: no, I currently don't have cygwin around. But it's similar to *patcher, so I assumed it works just fine. Are there issues? 22.29.30 # bluebrother: IIUC, Makefile variables are case-sensitive, and you used "ext" for Cygwin. 22.30.07 # you're correct -- that's definitely a bug 22.30.10 # bertrik: follow that link and it tells about it. (I've done other reaseach but that sums it up nicely with the flowchart) 22.32.02 Join pixelma [50] (i=pixelma@rockbox/staff/pixelma) 22.32.04 # linuxstb: change committed -- thanks for noting. 22.32.17 Quit lee-qid (Connection timed out) 22.32.39 # for some unknown reason I overlooked that ... should install cygwin :o 22.39.39 # I'm now trying to setup the crosscompiler in Ubuntu, when I try to run the rockboxdev.sh script then it closes the Terminal window. My command is: ". rockboxdev.sh" (minus quotes), what am I doing wrong? 22.39.55 # jhMikeS: ah so the important parts are that the charger may modify the termination voltage based on current temperature and that we there should be a (yet unknown) minimal difference between the current battery voltage and the voltage configured in the charger? 22.40.02 # evilnick: it's "./", not ". " 22.40.16 # Yay for silly mistakes 22.40.16 # is there any effort by audio player manufacturers to begin to use some "standard"/"open" interface? (e.g. alternative to "iPod port/interface") 22.40.28 # (for controlling player) 22.40.43 # tkooda: not really 22.40.59 # evilnick: . refers to the current directory, so it would the same as path/to/dir/rockboxdev.sh 22.41.52 # Right, so how do I run the darn thing? 22.41.59 # soap: around? 22.42.03 # It's set to be executable 22.42.38 # evilnick: like bluebrother said, ./rockboxdev.sh 22.43.07 # evilnick: Open up a terminal window, type "cd /path/to/rockbox/tools/", then type "sudo ./rockboxdev.sh" 22.43.22 # Cool. Thanks guys, I'll install PATCH and try again. 22.43.42 # evilnick: if the script isn't marked as executable you can either chmod +x or put the interpreter in front -- in that case, "bash ./rockboxdev.sh" 22.45.35 # bluebrother: I'm very new to linux, or some aspects of it. I had an extra space AFTER the ./ 22.47.13 Join Falafel [0] (n=Falafel@186pc220.sshunet.nl) 22.47.23 # bertrik: Current draw seems to be more significant a factor than termination voltage. The hardware should handle the voltage part. 22.48.00 Quit ikari ("CGI:IRC (EOF)") 22.49.37 # hmm. Installed cygwin and building checkwps fails due to the ATTRIBUTE_PRINTF in debug.h. Do I need to install special stuff for that to work? 22.50.07 # There's probably an #include missing 22.51.58 # I'm being told that my C compiler cannot create executables 22.52.13 # on linux ? 22.52.18 # Ubuntu 22.52.31 # then you probably lack some of the necessary packages 22.52.36 # have you installed a c compiler? 22.52.42 # Try "sudo apt-get install build-essential" 22.53.09 # * gevaerts had that once after accidentally screwing up the permissions on /tmp 22.53.13 # The AS3514 handles both the charge current and the voltage, but does not allow to measure current (as far as I know anyway). There is an end-of-charge indication on which the software has to act to stop the charger. The datasheet mentions that end-of-charge current level is at 10% Inom (typical) 22.53.35 # I'm following the instructions on the crosscompiler wiki. 22.53.55 # bluebrother: firmware/include/_ansi.h 22.54.36 # evilnick: what happens if you run "gcc" ? Does it complain about not finding gcc, or does it say "no input files" ? 22.55.08 Quit Siku () 22.55.15 Quit Mathiasdm ("Yuuw!") 22.55.19 # It was probably not installed. I've just installed the build-essential package 22.55.47 # bertrik: 10% is what's mentioned in the panasonic info too (0.1CmA) 22.56.53 Quit n1s () 22.57.57 # so on the S with a stock battery, we stop at 70mA 23.01.20 # Ah. NOW I see the note for Ubuntu users. Sorry all. 23.03.02 # jhMikeS: Were there tests/reports that the sleep-at-ata-poweron fixes the problems on G5.5? 23.03.34 # * amiconn is a bit puzzled, because *enabling* the hack on mini (before the fix) didn't help at all 23.05.46 # amiconn: Nico_P checked it 23.06.03 # my test was rather basic 23.07.23 # Nico_P: I don't remember much delay in hearing "unresponsive" on previous tries :) 23.07.39 # hehe :) 23.08.19 # it does feel more responsive than it was without the hack before the fix, but I can't guarantee the behaviour is the same without and with the hack 23.09.30 Join chrisjs169 [0] (n=none@unaffiliated/chrisjs169) 23.09.39 # that's why I just decided to let time pass with it disabled and see if anything comes up 23.09.54 # * chrisjs169 hopes gevaerts is on 23.11.24 # Nico_P: I wouldn't expect everything to be precisely the same in terms of times or whatnot but things should run just fine as with other targets. 23.11.34 # * gevaerts wonders what he has done now 23.12.05 Join dan_a [0] (n=dan-mirc@217.23.173.156) 23.12.22 # from what i understand, you're familiar with recovering sansa's, correct? ;) 23.12.26 # * linuxstb spots a Clip owner... 23.12.51 # Depends on what's broken I guess. 23.12.57 # * dan_a spots someone who's got further with the Clip than he did 23.13.00 # i2c on e200 23.13.11 # dan_a: I had everyone elses work to build on though... 23.13.36 # hmm. I've never actually gone that far. 23.13.39 # normally, i'd just use e200tool and be on my way, but for some reason the sansa isn't showing up in lsusb 23.13.52 # lsusb as root ? 23.14.20 # dan_a: Are you still interested in hacking it? 23.14.24 # * chrisjs169 checks 23.14.32 # lsusb as root doesn't make a difference 23.14.44 Part simonrvn ("Thanks, and Take Care") 23.14.57 # linuxstb: I am 23.15.32 # Hm, buffering thread stack seems to be larger than necessary... 23.15.42 # I've not had i2c issues yet, so I can't really suggest anything 23.16.05 # I've not done anything on it in a long time though, and I've never been any good at reading disassemblies 23.16.21 # dan_a: Do you understand how the library blocks are organised in the firmware file? I'm not sure how to calculate their start addresses... 23.16.22 # gevaerts, a while back (nearly a year ago) i managed to brick my sansa by shorting the daughterboard due to a drop of water, which put it into preboot mode. i suppose what i'm asking is do you know if the i2c is stored on the daugherboard? 23.16.32 # * amiconn spotted something interesting in the DEV_EN table 23.16.33 Quit Vorador ("Ex-Chat") 23.16.39 # I don't know, sorry 23.16.49 # bluebrother: you forgot the elides when you change the backup filename in rbutil.. :-) 23.16.51 # chrisjs169: I don't think anyonw knows where that memory is physically located 23.17.14 # * gevaerts can fix nand flash issues on c200, but i2c issues on e200 are unfortunately still out of his reach 23.17.24 # Bagder, ok, I figured since e200tool can read from it, it'd be known 23.17.33 # dan_a: The Clip OF contains a lot of thumb code, which makes it nastier as well. At least for me using objdump (I should start using IDA...) 23.17.53 # chrisjs169: only from the processor's view, not from physical 23.18.09 # Bagder, ah 23.18.28 # linuxstb: I don't understand it at the moment. I'll have a look at what everyone else has found out so far, and see what I can add to that 23.19.07 # Bagder, do you know if it's possible for the sansa to try running/executing/(whatever the proper word is) the i2c, failing, and not go into preboot mode? I'm rather stumped as to how it isn't going into either preboot or manufacturing mode 23.19.53 # chrisjs169: we've not seen it happen before, but I guess everything is possible even though unusual 23.21.00 # Bagder, ok. I've always heard (and said) that it isn't possible to brick a Sansa without hardware modifications, so I've just been rather confused 23.21.37 # domonoky: I did? Dang. 23.21.47 # chrisjs169: so how did it end up like this? 23.21.55 # * domonoky just fixed.. another commit count increase.. :-) 23.22.44 # Bagder, I had put a copy of the i2c rom on the recovery mode partition, and the sansa froze while writing it 23.22.54 # hehe 23.23.39 # And since then it does basically nothing ? Did you do a hard reset ? 23.24.09 Quit pondlife (Read error: 110 (Connection timed out)) 23.24.19 # gevaerts, I've done everything from hard resets, to booting with no battery (power via usb), to removing the daugherboard itself, without any luck 23.24.21 # chrisjs169: I would expect that you just use the extension ".bin" and replace your BL with it... 23.24.33 # s/you/to 23.24.43 # hm no 23.24.46 # the BL is .rom 23.24.59 # yeah 23.25.00 # i2c is .bin 23.25.15 # suppose "i2c rom" wasn't correct then 23.25.34 # but the BL has no known way of writing it 23.25.52 # * linuxstb hugs his "unbrickable" telechips devices with their usb boot mode safely stored in ROM 23.26.14 # * gevaerts dares linuxstb to lend one of these to chrisjs169 23.26.27 # gevaerts, heh 23.26.34 # Bagder, really? because placing an i2c.bin file on the 16mb-format drive causes it to write it 23.26.35 # * Bagder offers a quote from an old mrh mail: 23.26.40 Quit petur ("*plop*") 23.26.47 # "You do not upload i2c.bin via 'recover'. You copy it to the recovery 'disk' and hopefully it will be written to the i2c boot-ROM" 23.27.05 # "hopefully" ? ;) 23.27.07 # "You NEVER ever copy ANY .bin file on the recovery disk unless you cannot get to the manufacturing mode anymore." 23.27.27 # Bagder, yeah, that's what I noticed 23.27.29 # That seems to match what we see 23.27.29 # "I cannot emphasize this point too much." 23.27.35 # Bagder: what about renaming a patch to the BL name and copying it over? ;) 23.27.36 Quit domonoky (Read error: 104 (Connection reset by peer)) 23.28.59 # is the SoundCodecWMA page up to date? And what was the type/version wma Rockbox can not play? 23.29.07 # I've run the rockboxdev.sh script, added the PATH line to my .bashrc file (for my user), when i run ../tools/configure from the build directory to create the makefile then I get an error telling me that the gcc compiler is not in my path! 23.29.25 # Bagder: don't know if you saw it in the logs: what do you think about adding a diffstat output at the top of the svn commit notifications? 23.29.38 # pixelma: I think it's just "wma pro" (v9?) and "wma lossless" 23.29.41 Join voltagex [0] (n=voltagex@220-253-116-98.ACT.netspace.net.au) 23.29.45 # evilnick: .bashrc is only evaluated when you start a new shell. 23.29.47 # bluebrother: a fair idea, indeed 23.29.58 # linuxstb: thanks :) 23.30.05 # gevaerts: thanks again. That's good to know! 23.30.10 # i've thought that since my last sansa went directly to preboot after I shorted the daughterboard, the i2c would be stored somewhere on the daughterboard as well (perhaps that small chip on the bottom? 23.30.11 # evilnick: as a start you could "export PATH=/your/compiler/path:$PATH" 23.30.40 # chrisjs169: quite possibly 23.31.16 # "Build should have been done 117m 50s ago, at 21:33:09" -> shouldn't this get fixed? 23.31.43 # Bagder, that's what seems odd though - if it was, the sansa should be in preboot mode right now (i have the daugherboard out) instead of some dead mode 23.33.14 # ah 23.33.35 # mcuelenaere: poking it 23.34.14 # Bagder: thanks :) 23.34.17 Quit bertrik ("bye") 23.34.40 # amiconn: what did you mean exactly by "the inner loop should call the various functions"? It sounds like you're saying the inner loop should just be gone and use one loop instead. 23.35.21 # mcuelenaere: the zen vision build needs a unique target_id, not it has the same as zvm (in configure) 23.35.31 # s/not/now 23.36.30 # I'm trying to compile rbutilqt, I've installed libusb but I get autodetection.cpp:24:17: error: usb.h: No such file or directory 23.36.32 # Bagder: ok, does this need to be set somewhere else too ? (ie config-xxx.h ?) 23.36.33 # 39 is available 23.37.17 # no, it's just a way to keep track of things in the configure for the most cases 23.37.35 # voltagex: linux ? 23.37.43 # gevaerts: mac 23.38.39 # Does it distinguish runtime and development packages ? You might need to install the libusb devel package 23.39.11 # gevaerts, here's one you might be able to help on - what program could i use as a usb sniffer? 23.39.34 # gevaerts: no packaging system on os x by defult, I'm using macports and it doesn't seem to have libusb-dev 23.39.50 # voltagex: I don't know then 23.40.11 *** Saving seen data "./dancer.seen" 23.40.13 # voltagex: Did it actually install usb.h anywhere? e.g. /usr/include/usb.h or /usr/local/include/usb.h 23.40.25 # linuxstb: /opt...somewhere 23.40.28 # chrisjs169: I've used the wireshark/usbmon way for a bit, but I'm actually more used to sniffing hardware 23.40.49 # voltagex: Then that's probably the problem - you need to add that to the -I include path somewhere in the rbutilqt Makefile 23.41.26 # /opt/local/include 23.41.55 # I think you'll need to add that to INCPATH in rbutilqt/Makefile 23.42.26 # And maybe add /opt/local/lib to LIBS 23.42.54 # strange, the makefile had -Included most of /opt/local 23.43.09 # but not /opt/local/include 23.43.50 # anyone with a mac feel like testing my new binary? 23.45.27 Quit OlivierBorowski (Remote closed the connection) 23.46.14 Join stripwax [0] (n=Miranda@87-194-34-169.bethere.co.uk) 23.46.20 Join OlivierBorowski [0] (n=OlivierB@ANancy-157-1-10-160.w86-204.abo.wanadoo.fr) 23.47.07 Quit stripwax (Client Quit) 23.47.39 Quit Lear ("ChatZilla 0.9.82 [Firefox 3.0pre/2008051206]") 23.48.46 # voltagex: add the path to the INCLUDEPATH variable in rbutilqt.pro 23.49.21 # or LIBS += -L/opt/libusb 23.50.29 Join stripwax [0] (n=Miranda@87-194-34-169.bethere.co.uk) 23.50.57 Quit mcuelenaere () 23.51.12 # gevaerts, ok, thanks. sadly, i'm getting absolutely no usb info from my sansa 23.55.05 # Strange. Trying to build checkwps on cygwin fails because _ANSIDECL_H_ seems to be already defined!? 23.58.08 Quit amiconn (Nick collision from services.) 23.58.14 Join amiconn [50] (n=jens@rockbox/developer/amiconn) 23.58.40 Quit davina (Remote closed the connection)