--- Log for 10.09.104 Server: leguin.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 14 days and 13 hours ago 00.04.17 # hmm, Tremor makes liberal use of malloc()... 00.04.33 # hehe 00.11.06 Join Swampylee [0] (Swampylee@host81-153-49-40.range81-153.btcentralplus.com) 00.14.59 Quit edx () 00.18.02 # hey, do you guys have a cross-compiler for the iriver target? 00.18.28 # yes 00.18.42 # so, at least that is not a holdup... 00.18.52 # it sounds like this will be very feasable 00.19.18 # yes, i think so too 00.19.46 # when Zagor says something is feasable -- then it MEANS it's going to happen! 00.19.52 # lol 00.20.08 # well, no promises... 00.21.04 # btw, when is someone going to remove the Shutdown entry in the v1 recorder menu? 00.21.10 # it's only in the way 00.21.13 # :) 00.21.18 # hö ? 00.21.21 # why that ? 00.21.23 # they told me LinusN was going to do that 00.21.41 # "they"? :) 00.21.47 # oh well 00.21.48 # dunno 00.22.12 # ah 00.22.20 # * zeekoe just complains too much i think 00.22.22 # I just ordered a h140 online... --> Eric is getting ready for iriver:rockbox -- the clash of titans! 00.22.27 # u got more hw info from the .de guys yet? 00.22.40 # all chips accounted for? 00.23.30 Quit JoeBorn ("CGI:IRC (EOF)") 00.23.30 # pike|: yup, Dave Hooper nailed the last one i think 00.23.44 # sweet, gulligt 00.24.09 # is there a dedicated ML for iriver (or perhaps to early?) 00.24.11 # $361 for the h140 -- has anyone seen a better price? 00.24.26 # there is still a mystery chip 00.24.34 # i can only hunt for low prices in .se 00.24.37 # pike|: I think it should just be the rockbox mailing list... I mean it is rockbox -- not ArchosBox 00.24.38 # wow, that's cheap. where did you find that? 00.24.45 # got a h120 myself 00.24.48 # Comp-U-Plus Direct 00.24.59 # I've ordered from them before -- pretty good place. 00.25.08 # i paid more than that for our 120 :) 00.25.09 # and Harmony Computer right here in New York has them for $369 00.25.24 # elinenbe, thats certainly true, but will the 2 versions be compatible at any level ? 00.25.52 # pike|: i agree with elinenbe. we won't benefit anything by splitting up the mailing list. 00.26.18 # there are not THAT many mpe hardware hackers out there -- there really is no benefit ot have more than one list. 00.26.36 # let me just introduce myself, swede, 30ish, male naturally. Project Manager for XBMC and proud ihp120 owner 00.26.51 # it would be great if we could combine the neuros efforts, the ipod on linux efforts, our efforts etc. 00.27.00 # pike|: xbmc is a nice piece of work. 00.27.14 # "naturally male", no gender change surgery then. :-) 00.27.15 # pike|: quite amazing actually -- I LOVE it. 00.27.23 # elinenbe, yeah, we're "getting there" slowly but steady 00.28.09 # pike|: what is missing? really? other then built in shoutcast support :) (without using the python script) 00.28.26 # we support shoutcast, just make a strm file 00.28.27 # the iriver has REALLY nice build quality. 00.28.45 # pike|: I want to browse shoutcast streams like I do on shoutcast.com 00.28.50 # xbmc dvd handling is kinda weak, mmenues etc 00.29.05 # elinenbe, hmm, I think that is in the works 00.29.12 # we got nullsofts blessing 00.29.53 # pike|: really? awesome! 00.30.14 # pike|: yeah that is a HEAVILY requested feature (running DVD .iso images, and menus) 00.30.31 # 00.32.05 # yep.. efnet #xbmc is the place for those discussions :p 00.34.55 Join bagawk [0] (Lee@ACC03814.ipt.aol.com) 00.37.55 Join SmoothOperator [0] (~acbca9bd@labb.contactor.se) 00.38.03 # hey all 00.38.15 # hi 00.38.21 # hi Smoo 00.38.51 # hiya 00.39.04 # LinusN: which is a mystery chip? 00.39.43 # last in the hardwarecomponents wiki page 00.39.51 # Mystery chip on what? The iriver? 00.40.51 # lw052a? what's mysterious about it? 00.41.30 # azu-3aw-zd5l 00.41.46 # lol 00.41.50 # reload the page, zagor 00.41.55 # ah 00.42.10 # looks like bababa, barzvls. vrml. gugugugu 00.42.19 # :) 00.42.29 # had to use some serious photoshop tricks to make out the markings 00.43.13 # has anyone looked on the back of the lcd? 00.43.26 # nope 00.43.41 # unless you mean "on the board behind the lcd" 00.43.44 # LinusN, don't you have a binocular microscope for such things ? 00.43.54 Join tfinn [0] (541-ident-@209-162-215-114.dq1sn.easystreet.com) 00.44.03 # lImbus: hehe, no 00.44.24 # there are some markings on the side of it 00.44.32 # the lcd? 00.44.39 # 0301W and 3ZA 00.44.44 # yes, the lcd 00.45.29 *** Saving seen data "./dancer.seen" 00.45.33 # http://rockbox.haxx.se/iriver/front_big.jpg is not there, but the back counterpart is 00.45.48 # LinusN, too bad. makes soldering smd and such stuff much easier. no coffe for 2 days, and ready you are. 00.45.57 # pike|: oops, mistyped link. me fix. 00.46.09 # aha.. 00.46.12 # large not big, hehe 00.46.24 # exactly 00.48.41 # I assume you know the disk is fat(32?) formatted.. 00.48.51 # yes 00.49.01 # lImbus: yeah, we had a microscope like that on my previous assignment, really handy 00.49.01 # it's like one huge usb memstick when you connect it to the pc, lol 00.49.28 # yes, it's the same with the archos. 00.49.46 # ok. I never had one of those 00.51.13 # there's no pda o/s running on this cpu already, is there? 00.51.24 # cpu model I mean 00.51.39 # there's uclinux available 00.51.48 # what's the processor in the archos? 00.51.58 # tfinn: hitachi sh-7034 00.52.08 # just for clarification, I meant the coldfire cpu 00.52.23 # pike|: yes, so did I 00.52.31 # the original palms are predecessor to coldfire 00.52.42 # coldfire is new-generation 68k 00.52.51 # http://www.uclinux.org/ports/coldfire/binary.html 00.53.09 # tfinn: yup 00.53.11 # but really I would think for an audio player an RTOS would do a better job 00.53.27 # something like RTEMS or eCOS 00.53.29 # Another day, another dollar. 00.53.31 # tfinn: absolutely. we are using our own simple kernel. 00.53.38 # Good morning, fellow boxers. 00.53.53 # good night, dwihno :) 00.54.03 # Nah, I just woke up 00.54.11 # zag: how much ram/flash is available? 00.54.30 # dwihno: "i woke up" is not immediately equivalent to "it is morning" ;) 00.54.41 # tfinn: on iriver 2 MB flash and 32 MB ram 00.54.48 # Zagor: Well of course it is :) 00.55.03 # Zagor: It's like it's eftermiddag after you've eaten middag :) 00.55.15 # :) 00.55.39 # it can be a Bad Morning also 00.55.47 # Nah 00.55.49 # It's friday! :) 00.55.54 # There's no such thing as a bad friday 00.56.13 # And I already bought breakfast - curry/chicken baguette, featuring milky shake deluxe! :) 00.58.58 # yummi 00.59.05 # btw, if you want optimized software routines, dont forget to check the foobar SDK 00.59.11 # he optimized the hell out of some things 00.59.36 # has there been any development already? 00.59.49 # That would explain why Zagor's still around and not in bed :) 00.59.51 # pike|: yes, but it is ia32 only isn't it? 01.00.14 # dunno.. 01.00.38 # I know he fixed some crucual bug in the ISO mpeg specs :p 01.01.15 # yes, the specs are buggy. the libmad docs also mentioned that. 01.01.37 # [OT] how is the rockbox windows port progressing? anyone having some info? 01.02.01 # afaik nobody has started with that 01.02.30 Nick pike| is now known as pike (~amiga@h234n1fls22o1064.bredband.comhem.se) 01.06.01 # how many gray shades does the 120 have? 01.06.51 # 16/4bpp I *think* 01.06.55 Quit SmoothOperator ("CGI:IRC") 01.07.11 # can look it up for certain if u wish 01.07.29 # i thought it was 4 (2bpp) 01.07.30 Quit scott666 (Read error: 104 (Connection reset by peer)) 01.07.49 # hmmm, what did people have in mind regarding the windows port that isn't already done by the simulator? 01.08.09 # hardeep: just as a test bench for the reorganisation of the rockbox build system 01.08.18 Join scott666 [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 01.09.10 # 4 it was... my bad http://www.beermex.com/@spc/iriver/ihpbmp/ 01.09.58 # hello dithering :) 01.10.34 # well, we play movies and show jpegs with 1bpp on the archos :) 01.10.36 # Zagor: can't you still use the simulator for this? 01.11.20 # hardeep: most of it, yes 01.13.58 # Zagor: Imho porting of rockbox to Win should be a complete port, including playback (e.g. with libmad), in order to properly modularize the code 01.14.02 # one major difference between h1xx and h3xx is that the h3xx got a clock, but h1xx doesnt 01.14.53 # amiconn: yes, it's mostly a matter of how much work one wants to put into the "test bench" 01.14.56 # How about iriver batteries? 01.15.09 # Are they replaceable? 01.15.16 # dwihno: custom li-polymer 01.15.24 # li-poly? neato! 01.15.40 # Although I hate the idea of custom batts. 01.15.46 # Well, as long as they are replaceable 01.15.46 # Zagor: If done properly, this should make further porting much more easy. 01.15.56 # costs 500sek to replace it @ irivernordic 01.15.57 # amiconn: agreed 01.16.06 # amiconn: I agree 01.16.09 # pike: quite cheap. 01.16.27 # yeah, ok price 01.17.54 # as compared to the ipod (ipay?) fes 01.17.56 # fees 01.17.59 # "FLAC is asymmetric in favor of decode speed. Decoding requires only integer arithmetic, and is much less compute-intensive than for most perceptual codecs." 01.18.06 # sounds promising 01.18.07 # lol. ok, I now see sek means swedish kroner. I tought about: custom battery swap takes 500 seconds, geeeeez 01.18.35 # :) 01.19.21 # see, I'm ready for bed. I guess we'll continue laughing tomorrow 01.19.31 # it's already tomorrow ;) 01.21.33 # yeah, as you already slept, we went trough that a few minutes ago. But when I come home from the office, it's always today, always time to go to bed, and always late. 01.21.58 # even harder if I ass around in a strange irc all evening long ;-) 01.22.50 Quit Swampylee () 01.23.38 # cya geeks 01.23.58 Quit lImbus (" HydraIRC -> http://www.hydrairc.com <- *I* use it, so it must be good!") 01.25.21 # * zeekoe -> bed too 01.25.38 # have fun with being euphoric 01.26.02 # haha 01.26.44 # i'm off to bed too. see you in a few hours. 01.27.01 Quit Zagor ("Client exiting") 01.27.14 Quit zeekoe ("bed time") 01.27.34 # \o/ 01.34.05 # it is neat that my silly experiment with the v2 firmware started a new porting of rockbox :) 01.34.56 Join [IDC]Dragon [0] (~idc-drago@pD9512274.dip.t-dialin.net) 01.35.04 # hey [IDC]Dragon 01.35.14 # <[IDC]Dragon> hi! 01.35.14 # [01:34:07] it is neat that my silly experiment with the v2 firmware started a new porting of rockbox :) 01.35.14 # [01:34:58] *** [IDC]Dragon (~idc-drago@pD9512274.dip.t-dialin.net) joined 01.35.19 Join mrrrl [0] (~42570bf8@labb.contactor.se) 01.35.22 # :) 01.36.17 # <[IDC]Dragon> have been busy beeping 01.37.14 # beeping what? 01.37.29 # Having a problem. I installed Rockbox 2.2 on Studio 20 and when I select a song and press play, I get Error on the display. Any ideas? TIA 01.37.50 # [IDC]Dragon: [OT] Any idea where to get an el cheapo spdif optical->electrical converter? 01.38.20 # mrrrl: sounds like you need a .rockbox directory 01.38.54 # <[IDC]Dragon> let me check one more think, I have a question to Linus MAS Nielson then 01.39.11 # <[IDC]Dragon> amiconn: Conrad, Reichelt, DIY 01.39.13 # Hi Jörg! :) 01.39.28 # I did install the dir . 01.39.35 # Grr, this .rockbox dir issue gets annoying. Rockbox could simply create it in case it is missing 01.39.54 # <[IDC]Dragon> yeah, I also don't like it 01.40.06 # [IDC]Dragon: Conrad != el cheapo 01.40.10 # <[IDC]Dragon> since the Ondio has exchangeable media 01.40.13 # amiconn: :) good idea 01.40.54 # <[IDC]Dragon> amiconn: get a TORX173 from Reichelt, hook it up to 5V, a resistor and a cinch jack 01.41.03 Join John_Walker_Cefe [0] (iS2k4@200.167.210.72) 01.41.25 # nick John_Walker 01.41.35 # putz 01.41.39 Nick John_Walker_Cefe is now known as John_Walker (iS2k4@200.167.210.72) 01.41.43 # If the .rockbox dir is the common issue with getting the Error on the screen I will check it again... 01.46.07 # the iriver lcd has some markings on the cable strip 01.46.14 # S4E1 5002 01.46.14 # [IDC]Dragon: I can get it from Segor then, which means no online order (& associated fees & delays) necessary 01.46.47 # amiconn: rockbox shouldn't create it 01.46.53 # Why? 01.46.58 # the user should follow the instructions instead 01.47.16 # the rockbox dir contains other useful stuff 01.47.28 # maybe not that vital for the studio though 01.47.32 # Yay! 01.47.34 # LinusN: any ideas if the hardware on the iriver flash based players is almost the same? 01.47.45 # i don't know 01.48.55 # LinusN: Agreed 100% that rockbox should at least warn if .rockbox isn't there, but either create it afterwards, or run without it (perhaps with somewhat reduced functionality) 01.49.35 # if i can find a 128 mb player or so really cheap, i might get one 01.51.33 # amiconn: you are aware that it is a bug that it hangs? 01.51.44 # and i fixed it some weeks ago 01.52.05 # it should continue, but the splash() function crashes 01.52.09 # Ah, he sad he runs 2.2... 01.52.38 # <[IDC]Dragon> LinusN: the ondia was a GPIO line to MAS pin "SIBI", any idea why? 01.52.50 # OK, the dir was there, I deleted it, mkdir again, still same problem, did it again, this time it worked. I don't understand why it didn't work the other 2 times. Thx for the help... 01.52.51 # <[IDC]Dragon> *ondio has* 01.53.06 # mrrrl: mkdir isn't the solution 01.53.28 # unzipping the entire zip file is the solution 01.53.37 # SIBI? 01.54.17 Part tfinn 01.55.11 # <[IDC]Dragon> pin 51, serial input word indication 01.57.19 # the markings on the LCD COG: TF3X23 01.57.30 # <[IDC]Dragon> datasheet says we should hold it low 01.57.44 # [IDC]Dragon: i have no idea 01.58.37 # <[IDC]Dragon> what undocumented features does this allow? 01.58.49 # wav playback? 01.59.07 # <[IDC]Dragon> ;-) 01.59.34 # <[IDC]Dragon> ogg playback? 01.59.56 # Iirc the (unmodified) wav_io module needs pio in 02.01.02 # <[IDC]Dragon> we have only out, the (bidirectional) buffer is hard-wired for reading 02.01.04 # <[IDC]Dragon> :-( 02.01.25 # Same as in the jukeboxes 02.02.12 # From the datasheet: (1) For the MPEG bitstreams the word strobe pin SIBI must always be connected to VSS, bits must be sent MSB first as created by the encoder. 02.02.58 # <[IDC]Dragon> and if not, we can send LSB first? ;-) 02.02.59 # (2) For the MPEG bitstreams the word During enabling the DSP and its interfaces, it is strongly recommended to hold the SIBC Pin low. 02.03.15 # Argh, messed up 02.03.27 # (2) During enabling the DSP and its interfaces, it is strongly recommended to hold the SIBC Pin low. 02.03.45 # <[IDC]Dragon> SIBI, you mean 02.04.47 # No, SIBC (copy&paste). Ah oops, I didn't catch that. This has nothing to do with the "feature" you discovered 02.04.57 # Hmm 02.05.34 # There's more that Micronas doesn't want to tell... 02.09.13 Quit John_Walker ("Itaperuna Script 2004 - iS2k4") 02.13.52 # Anyway, I'm off now 02.14.02 # bye amiconn :) 02.14.05 Part amiconn 02.14.36 # my computer programming teacher at school is really lame :P 02.24.50 # time to go bye 02.25.06 Quit bagawk ("umount /dev/brain") 02.32.39 # time to sleep 02.32.42 # nite all 02.32.46 Part LinusN 02.33.43 # I'm trying to findout what cpu dwells in the recent flash based iriver players 02.37.50 # early conclusion, they are ARM cpu's 02.40.32 Join gromit`` [0] (~gromit@ALagny-151-1-49-139.w83-114.abo.wanadoo.fr) 02.40.39 Quit gromit`` (Read error: 54 (Connection reset by peer)) 02.44.28 Join nullobject [0] (~nullobjec@news.pec.co.nz) 02.45.24 # hi all, i just read zagor's post on iriverlounge.com...thanks for the invite to participate :) 02.45.33 *** Saving seen data "./dancer.seen" 02.46.59 # so what's the latest on the progress? 02.47.05 # dunno really 02.47.14 # Zagor and LinusN bought a IHP-something 02.47.41 Quit [IDC]Dragon () 02.47.51 # There's been some talk about porting rockbox to win32 as an exercise to prepare for upcoming platforms 02.47.52 # do they have the data on the LCD yet ? 02.48.01 # oh....I managed to get a copy of dogberts ihp.board file for the coldfire emulator 02.48.07 # check the wiki, it might be up to date 02.48.24 # anyone had a play around with that yet? 02.52.34 # has anyone actually gotten the emulator to work...i've been tinkering with that myself ;) 02.52.55 # just wondering if anyone can shed some light? 02.54.49 # reading the thread @ english iriverlounge forum, subforum firmware, wonder how it will end (hopefully everyone kiss and be friends again) 02.58.02 # url? 02.58.30 # http://forum.iriverlounge.com/viewtopic.php?t=2 03.01.08 # sad it almost ended there. very glad it didn't! 03.03.20 # *fix contact lenses* 03.06.38 # yeah! 300% visibility increase! 03.08.27 # nice! 03.08.33 # pretty dumb thing to get upset about if you ask me 03.08.38 # Instant improved vision, how could people not like glasses 03.09.23 # i mean, a forum is supposed to be a space for open collaboration... 03.09.30 # nullobject, I agree 100%. "praise the lord" Zagor is bigger than that 03.09.54 # is Zagor the person in charge of the rockbox project? 03.10.01 # (sorry for my ignorance) 03.10.18 # He started it along with LinusN and Badger 03.10.28 # I think he's the official coach of the team. 03.10.43 # * dwihno just sits at the bench ;) 03.10.46 # ah cool, yeh just added my details to the wiki...i'm keen to get hacking my ihp140 03.11.08 # I'm just here for the ride. Stuff like this fascinates me 03.11.55 # This project actually convinced me into buying an archos in the first place 03.12.04 # i'll be much more excited when i can actually boot up my ihp into an alt. firmware...even if it doesn't do anything fancy 03.12.40 # i think getting to that stage will be the hardest part. What was your experience with the other hardware? 03.12.40 # Although, when I bought it, there was no support for recorder models (ATA errors, no sound, fishy fat driver to mention a few things) 03.13.18 # I wonder if the SRS stuff is done purely in hardware, because implementing SRS support will probably not happen... heh 03.14.19 # hmm...not sure, i reckon it's done in software tho because it chews up the battery which would indicate that the cpu is under constant load. If there were a chip for SRS then i don't think it would drain the battery as fast :) 03.14.57 # Also, it's probably a proprietary algorithm...anyone know about this? 03.15.45 # proprietary as in you gotta licensce it sounds about right 03.16.07 # nothign I would miss. a parametric eq would be better anyway :) 03.16.26 # bass & trebele adjust != EQ 03.16.41 # i agree totally 03.23.39 # Interesting forum 03.24.57 Quit midkay (Read error: 104 (Connection reset by peer)) 03.25.01 # not much in the english forum, try .de instead 03.25.09 Join midknight2k3 [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 03.25.49 # got an url? 03.25.55 # same just .de 03.26.06 # http://forum.iriverlounge.de 03.26.55 # ah, okay 03.28.11 # the ihp140/h140 harddrive is a little thicker than the h120 harddrive. wonder if the companies that makes these hd's will make bigger hd's the same depth as the one in h120 03.30.46 # h120=5mm, h140=8mm 03.31.10 Quit mecraw ("Trillian (http://www.ceruleanstudios.com)") 03.39.54 # I'm only accustomed to 2.5" regular laptop disks... is this some new kind of standard? 03.51.40 Join bc|feeding [0] (~BlueChip@cpc3-colc1-3-0-cust61.colc.cable.ntl.com) 03.51.59 Nick bc|feeding is now known as BC (~BlueChip@cpc3-colc1-3-0-cust61.colc.cable.ntl.com) 04.02.02 Quit mrrrl ("CGI:IRC (EOF)") 04.22.49 # it's 1.8" disks, made for the sole purpose of portable mp3 players :) 04.23.05 # when I'm not here I play Burnout3 on the xbox.. 04.26.53 # 1.8"? Coolness! 04.27.18 # I guess you can't buy them yourself? 04.28.38 # http://www.ebuyer.com/customer/products/index.html?rb=1700426180&action=c2hvd3N1YmNhdGVnb3J5X3BhZ2U=&subcat_uid=19 04.29.23 # ooh - no sorry, that looks a 1.8" disk in a pcmcia card 04.30.41 # Fishy :) 04.35.05 Quit nullobject ("Leaving") 04.35.54 # Hm 04.38.03 # Living in these ages is quite fun 04.38.11 # Electronics becoming smaller and smaller 04.38.16 # Fast and faster 04.38.22 # Expensiver and expensiver ;) 04.38.27 # 40TB on a holographic credit card recently 04.38.53 # The new ipods use 1.8" as well? 04.39.05 # yes 04.39.10 # as do many of the old ones 04.39.13 # aaah 04.39.14 # okay 04.39.48 # I wonder about the voltage 04.39.54 # and power consumption as well 04.40.15 # lower power 04.40.18 # I'd like to see a picture of an archos next to an iHP... 04.40.23 Quit hardeep ("[BX] Mike Tyson says BitchX BITES! Do you HEAR what I'm saying?!") 04.40.25 # I'll have to ask Zagor about that 04.45.35 *** Saving seen data "./dancer.seen" 04.46.04 Part taaz 04.59.25 Part BC 05.24.15 Join maikeul [0] (~gromit@ALagny-151-1-45-137.w83-114.abo.wanadoo.fr) 05.32.47 Quit gromit` (Read error: 60 (Operation timed out)) 06.12.49 # http://www.google.com/search?q=4004GAH&hl=en&lr=&ie=UTF-8&start=10&sa=N 06.13.40 # yeah, found out about that 06.14.11 # there's prob 60 &/ 80 available also 06.14.47 # or... there was this new hd that was supposed to be in an upcoming ipod 06.15.00 # specs about the hd leaked, so steve jobs got mad as hell 06.15.43 # I wonder why ;) 06.16.09 # Windows is a interesting creature 06.16.25 # I've had problems when I work with larger files residing on our server 06.16.36 # The network driver totally fucked up 06.16.43 # So now I've installed a newer driver 06.16.50 # ... it seems to work better now. 06.17.05 Join edx [0] (edx@pD9EAAF75.dip.t-dialin.net) 06.17.07 Quit edx (Remote closed the connection) 06.19.53 # you jumping on the iriver train also, dwihno ? or you'll wait awhile till there's something usable ? 06.20.36 # pike: I jumped on the archos train before there was anything usable 06.21.18 # but to answer your question... right now, my unit works flawlessly, and as long as it does, I do not think I will use my hard-earned money on an iriver :) 06.21.28 # so you'll stick with it till it works no longer? ^_- 06.21.37 # kk 06.21.59 # at least until I don't know what to spend my money on ;) 06.23.10 # What do you think? Will there be a rockbox for the iriver platform? 06.24.08 # well, like Zagor says.. they promise nothing. But it sure looks like they're gonna give it a try 06.26.01 # If the Linus/Bag/Zag team says they will try building a space rocket, I would buy stocks in their company :) 06.26.20 # xchat sucks on so many levels.. oh man, why did I ever switch from trusty old mirc 06.26.46 # xchat windows v2.4.0 = the suckage 06.29.08 # you can switch back 06.29.19 # and I will. soon 06.45.37 *** Saving seen data "./dancer.seen" 06.59.28 Quit scott666 ("i'll be back...eventually...") 07.00.08 Quit midknight2k3 (leguin.freenode.net irc.freenode.net) 07.00.08 NSplit leguin.freenode.net irc.freenode.net 07.00.44 NHeal leguin.freenode.net irc.freenode.net 07.00.44 NJoin midknight2k3 [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 07.53.02 Join ashridah [0] (ashridah@dialup-a1-304.Melbourne.netspace.net.au) 07.54.59 Join lImbus [0] (lImbus@34.105-200-80.adsl.skynet.be) 08.00.47 Join plok [0] (s336156@student.uq.edu.au) 08.02.49 # Is anyone awake? 08.03.10 # I'm trying to get awake *more coffee* 08.03.58 # :) My archos is dying, I wonder if anyone else has seen these symptoms? : 08.04.17 # which symtoms ? 08.04.22 # +p 08.04.25 # It usually powers off within about 2-30 minutes of use, no matter how charged or new the batteries are 08.04.34 # tried both rockbox and original firmware 08.04.52 # It's an original 6gig player that I got a long time ago, so I think it's just dying a normal death? 08.05.41 # It just shutsdown when it needs to access the disk after a while.. strange 08.05.53 # I know of bad battery connectors, so you may check that. 08.06.26 # The things that the battery touches at each end of their housings? 08.06.42 # yup. 08.07.08 # Furthermore, the 4 batteries are 2 in series and two in parallel. so if one side (left or right) is not correctly working, it drains only the other side, leading to such probs. 08.07.45 # Do you feel handy opening and taking apart your device ? 08.08.07 # Never done it before, but I'm almost certain that I'll buy a new one anyway, so why not? 08.09.05 # Can I do it with a screwdriver? 08.09.14 # it's pretty easy. You'll find a fine explanation on the rockbox-page somewhere. you should get rid of the bumpers and check if everything beneath that is ok. 08.09.30 # like broken soldering points and so on. 08.09.37 Join LinusN [0] (~linus@labb.contactor.se) 08.09.59 # Hmm..thanks! I'll give it a go. I wouldn't be suprised as I've had it I guess over 4 years now and it's been banged around a lot 08.10.10 # screwdriver ? you'll need a tiny screwdriver (for the 4 screws at the top and the lower boundary) as well as torx 08.10.30 # if you want, I can give you some pictures how it should like. 08.10.38 # iirc, i made some pics before 08.10.55 # I'd really appreciate that, should I messgae you my email, or do you have a link? 08.11.11 # mhmm. lemme first check my pictures 08.11.15 # k 08.11.39 # Of course, with the problems I've been very tempted to just go out and buy a new iRiver H340. 08.11.47 # Do you know if they are good? 08.12.02 # I'd heard some rumours that rockbox might one day make it to the iRiver units? 08.12.36 # plok: one of my mates has the h340. they look decent, but the LCD remote that comes with the 1xx series is better (although you can buy it separately and use it with the 3xx) 08.12.48 Quit ashridah ("Client exiting") 08.12.50 # see yesterdays irc-logfile. somebody was saying they had a better keypad that the h1xx, but something else was bad. must 've been something like less battery power but more weigth and bigger 08.13.07 Join ashridah [0] (ashridah@dialup-a1-304.Melbourne.netspace.net.au) 08.13.48 # plok: There has just been bougt the first hp120 and been dissected yesterday. there is no code yet running, and still a lot of work to do. a LOT 08.14.15 # I dunno if it's even clear it will work one day. 08.15.21 # well, i can tell you that it will be harder to reverse engineer than the archos 08.15.55 # a Linus, didn't see you coming in. good morning. what timeframe do you suppose ? 08.15.57 # the cpu is a BGA package, making it impossible to trace the signals with a multimeter 08.16.23 # LinusN: i would have assumed the high frequency more or less ruled out using a multimeter anyway 08.16.27 # oh well, fingers crossed. If I do get a new player, is there any call for an early JB6 player from the developers? 08.16.41 # so we will have to rely a heluva lot more on disassembling the original firmware to find out how the hardware is designed 08.17.02 # plok: studio or recorder? 08.17.14 Join [IDC]Dragon [0] (~idc-drago@pD9512274.dip.t-dialin.net) 08.17.20 # morning [IDC]Dragon 08.17.33 # <[IDC]Dragon> good morning 08.17.35 # it's just a player 08.17.41 # original thing, 6 gig one 08.17.44 # mojen 08.18.04 # plok: sounds like a good paperweight :-) 08.18.09 # :) 08.18.28 # Welcome back, Linus 08.18.39 # <[IDC]Dragon> LinusN: I need to ondio-adjust a few drivers, am not sure about the best way 08.18.54 # Perhaps just IFDEF? 08.19.00 # <[IDC]Dragon> I2C is on different pins, keys are different 08.19.03 # ah, okay 08.19.56 # <[IDC]Dragon> the #ifdef strategy was to not name the hardware, but the feature flavour 08.20.24 Join midkay [0] (~midk@c66-235-14-120.sea2.cablespeed.com) 08.20.32 # <[IDC]Dragon> so should I do like #ifdef ONDIO_I2C_PINOUT ? 08.20.38 # Linus, do you know if the H340/320 are much the same as the hp120/140's, in terms of porting rockbox to either? 08.20.45 # [IDC]Dragon: yes 08.20.46 # plok, I'm just uploading 2 pictures to my webspace 08.20.53 # Awesome :) 08.21.07 # plok: they look a lot the same on the pics i've seen on the web 08.21.29 # i see two major differences, the color lcd and usb2go 08.21.44 # same cpu 08.21.51 # <[IDC]Dragon> but I hope we'll leave that road for "real" porting 08.22.22 # plok, did some pics when I swapped the big hdd from the device I got first (a used device) to the brandnew device that was flasheable 08.22.23 # Cool. 08.22.26 # [IDC]Dragon: the "real" port will probably have different source files for different drivers 08.22.33 # like i2c_ondio.c 08.22.40 # i2c_h120.c 08.22.42 # etc 08.23.10 # and the config script will select the drivers 08.23.10 # <[IDC]Dragon> the makefile is not really suggesting that, because we name directories, not single C files 08.23.17 # plok, I suppose the device I bought used must have had such problems like you have. that's why I has been mended 08.23.42 # [IDC]Dragon: today, yes, but we'll change that 08.23.52 # <[IDC]Dragon> ok 08.24.06 # that's the approach we are thinking about now anyway 08.24.07 # It's only started happening in the past 6 months or so I guess. Also, the battery life has become atrocious, which would seem to fit in with your theory 08.24.29 # plok: http://www.dejonghe.de/downloads/rb_HowItWas.jpg 08.24.32 # http://www.dejonghe.de/downloads/rb_howItShouldBe.jpg 08.24.35 # awesome :)( 08.24.38 Quit midknight2k3 (Read error: 104 (Connection reset by peer)) 08.24.56 # sorry for bad quallity, it#s just an old cheap digi-cam 08.25.37 # a flatbed scanner is the best tool for PCB images 08.26.14 # I know, but I didn't want to make pictures of the pcb. It has some 3rd Dimension ;-) 08.26.15 # <[IDC]Dragon> not my LED one 08.26.30 # lImbus: saw that now, my apologies 08.26.41 # <[IDC]Dragon> it has a focal depth of maybe 0.5 mm 08.26.41 # they're fine. What was done to fix it? In the wrong one the coil seems to going off into nowhere? 08.27.07 # corrected typo: http://www.dejonghe.de/downloads/rb_HowItShouldBe.jpg 08.28.07 # plok, I suppose it started detatching, so 'they' (whoever repaired) just stick it to the contact 08.28.27 # LinusN: don't bother. 08.29.44 # (lower case was working for me anyway) Hmm.. you mean on the back where we can't see in the second photo? It seems in the first photo, the bit of wire that drags the coil down to one side is gone completely in the corrected version? Am I all wrong? :) 08.30.54 # err. it's the other way around. "HowItShouldBe" is how it should look like on a new device 08.31.02 # it WAS a new device 08.31.20 # HowItWas looks like a solution. It was the used device I bought like that 08.32.09 # and as you saw correctly, I forgot to make pictures of the back, and the wire straight through it is to hold it down solely 08.34.57 # Ok. I think I understand. rb_HowItWas.jpg is a correctly functioning configuration also? 08.36.12 # yes. it was repairing, but it looks handmade, at least on the backside. so I suppose it's repaired 08.39.14 # <[IDC]Dragon> LinusN: your port pin assignment table is my valuable resource right now! 08.40.16 # * plok is away - Automatically set away. - messages will be saved. 08.40.49 # [IDC]Dragon: nice to have, isn't it :-) 08.44.22 # <[IDC]Dragon> indeed 08.44.42 # <[IDC]Dragon> but I keep theOndio map separate for now 08.45.38 *** Saving seen data "./dancer.seen" 08.46.55 # Is there a link that will tell me what Ondio means? 08.47.06 # <[IDC]Dragon> yes, see twiki 08.47.20 # Ondio is a smaller Archos device, no hdd, all MMC 08.47.49 # <[IDC]Dragon> LinusN: the I2C code sets PB5 high, regardless of model 08.48.42 Join amiconn [0] (~jens@pD9E7FAED.dip.t-dialin.net) 08.48.55 # hi all 08.49.05 # hi jens 08.49.05 # <[IDC]Dragon> which is MAS enable on player, charging off for recorder, power hold for FM/V2 08.49.09 # <[IDC]Dragon> hi 08.49.30 # [IDC]Dragon: (sorry for log peeking) I discovered this bug some time ago, when investigating the recording prob with rombox 08.50.08 # I did not do something about it yet. Imho PB5->high belongs to something like mas_init() 08.50.25 # <[IDC]Dragon> yes, but only for players 08.50.40 # <[IDC]Dragon> else it belogs to charging or power 08.50.48 # yes. On recorders it could do the mas poweron reset instead 08.51.28 # Then we could switch to using the normal reset in all other code 08.53.38 Part LinusN 08.53.48 Join LinusN [0] (~linus@labb.contactor.se) 08.53.52 # why does everybody excuse for log peeking. what's wrong with that ? 08.56.07 Quit ashridah (Read error: 60 (Operation timed out)) 08.56.27 # lImbus, I just went downstairs and bought a H340! 08.57.16 # [IDC]Dragon: I already tried that (mas_init() and changing the reset) back then, but reverted it because it didn't help the recording problem 08.58.15 # Hmm.. it's much smaller than my archos. 08.58.55 # plok: ouch. don't like the feeling of loosing so much precious money in so less time. 08.59.54 # lImbus. I was looking for an excuse anyway.. I think you scared me when you told me my old archos might be fixable :) 08.59.55 # I hope you'll get rockbox running on it once 09.00.03 # lol 09.00.42 # There are two usb ports, on says 1.1 Host. They are different form factors 09.01.50 # I have to wait for it to charge before I can play with it :( 09.02.47 # host means you can connect another usb-device to it. for example your digital camera to empty the memory of it. 09.03.03 # how about my archos? 09.03.28 # err. yeah, why not. 09.03.41 # if it stands the battery time ;-) 09.04.16 # Yeah.. at least now I won't be scared when I'm pulling it apart and having a look :) 09.04.26 # I wonder if you could plug this thing into itself? 09.04.40 # argl. 09.04.55 # you could. but don't switch it on then ;-) can't be good 09.05.44 # every connected to pc's with the archos usb-a to usb-a cable ? never seen a machine crashing so fast ;-) 09.07.06 # Heh.. of course, my IBM's laptop's USB ports are broken. If you plug anything into it, it instantly shuts down.. sometimes you can hear a spark 09.07.23 # Just happened when it came out of warranty 09.07.34 # lol 09.07.36 # lImbus: When doing that you may even fry the mobo/ usb card 09.07.55 # I know, it was not mine ;-) 09.08.07 # Wait, was it an IBM laptop? 09.08.21 # :) 09.09.13 # no, two standart pc 09.10.48 Join Zagor [242] (~bjst@labb.contactor.se) 09.11.00 # morning 09.11.24 # hoi 09.12.56 # gooood morning, or.. goood night (for me, lol) 09.13.57 # Now gcc 3.3.x is used for the daily builds... Nice :) 09.14.05 # P0NG 9:13am 09.14.12 Join ashridah [0] (ashridah@dialup-a1-144.Melbourne.netspace.net.au) 09.14.12 # <[IDC]Dragon> hooray! 09.16.40 # Zagor: morning 09.16.52 # I can't find any LEDs on the H340 09.17.31 # plok: i think there's two on either side of the nav pad under the LCD, just like the 1xx series 09.19.02 # ....maybe they'll light up when it's playing? 09.19.18 # one'll be the hard drive light, the other is the 'charging' light 09.19.28 # one of them is directly to the hard drive bus. 09.19.47 # http://www.misticriver.net/images/h340/review/120340down.jpg 09.19.48 # lImbus: i had a feeling that'd be the case 09.20.01 # http://www.misticriver.net/images/h340/review/mainunit.jpg 09.20.26 # well hidden... 09.20.59 # there is as a little reset recessed button on the side of the unit though, I wonder if that resets the firmware? 09.21.16 # reset = just if the unit hangs 09.21.24 # happened me once on my h120 09.21.29 # it's a reboot 09.21.32 # ahh, thanks 09.22.03 # pike, are you saying there are leds ther just very hard to see? 09.22.08 # plok: the device is mostly screwed if you break the ahrdware, from what i've seen in the forums so far 09.22.14 # s/hardware/firmware/ 09.22.21 # I'm saying I dont know where they are, if there are any 09.23.14 # pike, well I've looked over this one about 5 times and I can't see any, but I just bought it and isn't charged yet so I haven't been able to turn it on yet 09.23.35 # something should light up when you charge, atleast it does on h1xx 09.23.47 # odd. my h140 came charged enough to use the device for an hour or so, and longer if i used the radio 09.24.21 # I haven't tried turning it on yet.. the dude in the stote told me to charge it before using it.. is that baloney? 09.24.25 # store 09.24.38 # it's probably a good idea 09.24.41 # if it's empty, it's always good to give it a full charge 09.24.43 # but almost no battery is sold completely flat 09.24.56 # since most will sulfate and screw themselves 09.25.08 # the li-poly in the iriver series isn't supposed to do that tho 09.25.25 # my iriver was completely flat when i bought it 09.25.52 # hmm.. I'll just charge it when I get home. I can wait a few hours to answer the pressing LED question 09.26.21 # it can charge while on, so you can poke at it completely then 09.26.38 # <[IDC]Dragon> sorry to bug you again with the ol' Ondio 09.26.53 # <[IDC]Dragon> the buttonsare difficult to translate 09.27.12 # <[IDC]Dragon> it has only one common on/off button 09.27.22 # ok 09.27.32 # <[IDC]Dragon> the direction keys, and one "option" button 09.27.50 # can you short-press the on/off for stop? 09.27.59 Join pillo [0] (~trillian@navlab03.dei.unipd.it) 09.28.09 # <[IDC]Dragon> you mean in the original firmware? 09.28.11 # or is it impractically located? (can't see it on your photo) 09.28.21 # <[IDC]Dragon> it's on the top side 09.28.21 Quit pillo (Remote closed the connection) 09.28.29 # no, i mean is it technically feasible or does it turn off even on short press 09.28.39 # but the browser<->wps toggle will collide with the stop functionality 09.28.51 # <[IDC]Dragon> it turns off after a very long press 09.28.53 # if the on button is the same as the off button 09.29.17 Join pillo [0] (~trillian@navlab03.dei.unipd.it) 09.29.17 # LinusN: yes, but we need to rearrange a bit since we have fewer buttons 09.29.40 # maybe short press on option to switch between wps and browser and long press to enter menu 09.30.31 # <[IDC]Dragon> see the user manual on how Archos did it: http://www.minidisc.org/manuals/archos/archos_ondio.pdf 09.32.28 # <[IDC]Dragon> the UI is quite nice, actually 09.38.09 # <[IDC]Dragon> they use double clicks and long clicks as modifiers (not that I like it, but better than nothing) 09.38.56 # <[IDC]Dragon> instant recording is double clicking the on/off button 09.40.06 Join Lynx_ [0] (lynx@134.95.189.59) 09.40.38 # mental note: I am looking for instant rec on the recorder for a while, and double-on is not yet taken on the recV1, isn't ? 09.41.10 # <[IDC]Dragon> we have no double clicks yet 09.41.43 # I mean, there is no way to confound anything. 09.42.19 # uhh, there is one: If I am in the browser, want the unit to resume and go to the browser back again, I double click ON 09.50.16 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 10.00.04 # lImbus: that's not a separate double-click event 10.00.26 # you perform the same function by clicking it slowly 10.06.41 # ok. but I DO click very quickly for doing that at the moment. and it works. so implementing doubleclicks could mind some users. 10.07.06 # gotta go now. will peek the log, when I#m at work. 10.07.10 # cya 10.07.41 Quit lImbus (" HydraIRC -> http://www.hydrairc.com <- The dawn of a new age") 10.18.08 Quit plok ("I'm outta here!") 10.39.25 Join webguest81 [0] (~a9cfc147@labb.contactor.se) 10.41.28 Quit Bagder ("Leaving") 10.45.42 *** Saving seen data "./dancer.seen" 10.48.59 Quit webguest81 ("CGI:IRC (EOF)") 11.09.31 # <[IDC]Dragon> I'm pretending the Ondio to have a Player keypad now 11.10.12 # <[IDC]Dragon> lots of places to fix, we have the graphical LCD, but the limited keys 11.10.49 # yeah. the button issue is a rather difficult problem when supporting more platforms 11.10.53 # [IDC]Dragon: How far have you gotten btw? 11.10.58 Join lImbus [0] (~manuel@kernel.cycos.net) 11.11.23 # <[IDC]Dragon> dwihno: see twiki (my standard answer) 11.11.29 # :) 11.11.33 # :-) 11.11.41 # wiki wiki wang! 11.11.54 # Wiki - "How are YOUR wang today?" 11.23.00 # <[IDC]Dragon> any wps.c expert here? 11.23.41 # i wrote much of it, iirc 11.23.42 # i'm here 11.24.03 # * LinusN is not an expert, but he's here 11.24.24 # <[IDC]Dragon> I have a problemfor this recorder without a recorder keypad 11.24.26 # Zagor: it's good that you remember that you wrote it :-) 11.25.00 # cvs annotate agrees with me :) 11.25.21 # <[IDC]Dragon> there are 2 status_set_xxx functions to update the charcell display status 11.25.43 # <[IDC]Dragon> wps.c:580 11.26.05 # yes 11.26.23 # <[IDC]Dragon> I fall intothere, but have no player 11.26.48 # <[IDC]Dragon> just looking for the clean way, no extra #if 11.27.40 # #ifdef _is_ the clean way... 11.28.01 # <[IDC]Dragon> not if it's too many of them 11.28.22 # otoh I don't think the player button set is the best starting point 11.28.36 # <[IDC]Dragon> no? 11.28.46 # the ondio has true 4-way navigation, the player doesnt 11.28.51 # <[IDC]Dragon> else it'll be muchworse, I thought 11.29.12 Quit pillo (Read error: 104 (Connection reset by peer)) 11.29.13 # <[IDC]Dragon> but the 4 way doen't leave much else 11.29.22 # well it will be rather messy either way, but I think treating it like a player makes a worse UI 11.30.02 # <[IDC]Dragon> to get it working and functionaal, I prefered that 11.30.19 # up/down = volume, left/right = next/prev & ffwd/rew, option = browse/menu, power=stop 11.30.23 # no? 11.30.25 # <[IDC]Dragon> the missing recorder keys would make big parts inaccessible 11.30.34 # only the quickscreens 11.31.12 # <[IDC]Dragon> hmm, can I assign it that freely? 11.31.15 # actually i think power should be pause. stop is pretty useless on an mp3 player 11.31.56 # up/down/left/right and power is pretty simple, but the option button needs some hacking 11.32.07 # lunch time, back in a while 11.32.08 # <[IDC]Dragon> I'd need the functionality of F1(Menu), Play, On, Off 11.32.19 # hold option to get menu 11.32.21 # <[IDC]Dragon> andhave only Ontion, OnOff 11.32.36 # you don't need play in wps, only pause on/off 11.32.39 # <[IDC]Dragon> we have no long press yet 11.32.45 # we have repeat 11.32.58 # anyway, back soon 11.33.02 # <[IDC]Dragon> ok 11.33.18 # just use |BUTTON_REPEAT to sense long key presses 11.34.22 # <[IDC]Dragon> OK, let me summarize: 11.34.42 # <[IDC]Dragon> Menu is option+repeat 11.34.56 # <[IDC]Dragon> Play is option 11.35.07 # <[IDC]Dragon> On is OnOff 11.35.19 # <[IDC]Dragon> Off is OnOff+repeat 11.36.04 # <[IDC]Dragon> a repeated button causes no normal (unrepeated) event first? 11.36.47 # yes it does 11.36.56 # <[IDC]Dragon> :-( 11.37.05 # use the release events 11.37.22 # release without previous repeat == short press 11.37.46 # <[IDC]Dragon> that would require extra code in the handlers 11.37.53 # and? 11.38.19 # <[IDC]Dragon> I'm trying to port that part eith the button driver, if possible 11.38.31 # <[IDC]Dragon> s/eith/with 11.39.10 # i don't think rockbox would benefit from a quick'n'dirty port to the ondio 11.39.37 # this is a good opportunity to deal with the problem with different keypads 11.39.57 # <[IDC]Dragon> the Ondio woudn't benefit from the quick'n'dirty port of Rockbox 11.40.09 # exactly 11.40.30 # <[IDC]Dragon> I try not to break(touch) the rest 11.40.57 # <[IDC]Dragon> but as the very first step I want to use it somehow with the buttons 11.41.00 # we will have to change that anyway, sooner or later 11.41.12 # <[IDC]Dragon> without doing a UI overhaul first 11.41.49 # <[IDC]Dragon> yes, but when this thing moves, not before 11.42.03 # i understand 11.42.24 # <[IDC]Dragon> right now I can't write interactive test code 11.42.43 # <[IDC]Dragon> because I need buttons first 11.44.24 Join vadin2003 [0] (vadin2003@cmr-83-97-176-127.telecable.es) 11.45.26 Quit vadin2003 (Client Quit) 11.47.18 # LinusN: A completely different topic: There are a lot of patches in the tracker, dealing with language things, that are (auto- ?) assigned to quelsaruk. However, I haven't seen him around for a long time. Perhaps someone else should deal with these patches? 11.47.59 # yup 11.50.35 # lunch time 12.19.21 Join [av]bani [0] (~goemon@washuu.anime.net) 12.19.27 # <[av]bani> http://www.freescale.com/files/netcomm/software_tools/initialization/boot_code_generation/CFPLLCFG.zip 12.19.35 # <[av]bani> MCF5249 PLL Configuration Wizard 12.19.36 # <[av]bani> :D 12.20.14 # [IDC]Dragon: about repeat: you have two events: button-repeat and button-release. no need to make a complex state machine. 12.20.34 # <[IDC]Dragon> but a tiny one 12.20.40 # why? 12.21.10 # <[IDC]Dragon> because I get a regular buttonpress first, than repeated ones, then release 12.21.34 # yes. so if you get repeat, call repeat(), if you get release, call release(). nothing else required. 12.22.08 # getting release after repeat is not a problem, since you are no longer in the save switch 12.22.13 # same 12.22.25 # <[IDC]Dragon> but I still need to react on the normal (=short) press 12.22.33 # yes, that is release 12.23.08 # we are handling this already (albeit more complex) with the ON button on recorders for browser and pitch screen 12.23.09 # <[IDC]Dragon> ok, short press = release, long press = repeat 12.23.15 # exactly 12.23.44 # <[IDC]Dragon> but after a long press (repeat) I will also get a relaese (shot press) 12.24.02 # yes, but then you are no longer executing the same loop 12.24.17 # you have moved to the menu, for example 12.24.25 # ...which ignores release events 12.24.32 # <[IDC]Dragon> and somebody else may eat that realease, taking it as a short press 12.25.05 # yes, that can happen. but we see to it that it doesn't. 12.25.27 # <[IDC]Dragon> "see to it"? 12.25.30 # <[av]bani> http://www.microapl.co.uk/CFInit/cfinit_download.html 12.25.51 # not by general rule, but by making sure the code we call after repeat can handle a stray release 12.26.19 # [av]bani: nice 12.26.26 # <[av]bani> <3 12.27.44 # <[IDC]Dragon> hmm, but there is no way to tell a stray release from a short press 12.28.06 # <[IDC]Dragon> and there may be more repeat events in the queue 12.28.33 # <[IDC]Dragon> this is not clean yet,imho 12.28.45 # <[IDC]Dragon> but I got other issues first 12.28.49 # the queue can be emptied, and releases are only used when we combine long and short press 12.28.58 # ...which is pretty rare 12.29.16 # most places uses only single press 12.29.41 # this is UI code, it can never be clean ;) 12.30.00 # <[IDC]Dragon> haha 12.30.40 # <[IDC]Dragon> anyway, Ihave it compiling now with the Player buttons 12.31.18 # <[IDC]Dragon> sortes out several confusions about display and keymap not being independent 12.31.23 # <[IDC]Dragon> sorted 12.31.54 # <[IDC]Dragon> no extra code, just better #if's 12.32.09 # yes, i expect we have some bad ones 12.32.37 # <[IDC]Dragon> does anybody mind a commit of that? 12.32.48 # nope 12.33.23 # * [IDC]Dragon goes build-painting 12.35.09 # :) 12.45.46 *** Saving seen data "./dancer.seen" 13.02.36 # i can't find a gdb sim target for coldfire :-( 13.02.52 # does m68k not work? 13.03.02 # i can't find that either 13.03.17 # oh 13.06.12 # so we'll have to write one.. :-) 13.06.47 # i really thought there would be a 68k sim target... 13.06.54 # yeah 13.10.10 # LinusN: Luckily your area of expertise covers GDB stubs! :) 13.10.18 # And virtually everything else :) 13.10.37 # :-) 13.10.57 # yeah, i did patch the SH sim target to simulate the archos LCD 13.11.31 # * LinusN is thinking about designing a BDM wiggler 13.12.24 # <[IDC]Dragon> the Ondio is bad for gdb 13.12.26 # we'll need that sooner or later, so why not sooner 13.12.36 # <[IDC]Dragon> because the serial is taken for the MMC 13.12.37 # [IDC]Dragon: why? 13.12.42 # ah 13.13.13 # <[IDC]Dragon> let's hope I won't need gdb 13.19.47 # <[av]bani> linux kernel has some mcf5249-platform-specific code 13.20.03 # <[av]bani> an init routine at least 13.22.47 # <[av]bani> http://www.uclinux.org/pub/uClinux/archive/7545.html 13.22.55 # <[av]bani> somoene to talk to about 5249 :) 13.23.13 # nice! 13.23.42 # <[av]bani> This particular board is based around a Motorola ColdFire 5307 (@90MHz) design, fitted with 16MB of SDRAM, 2MB FLASH, 2 ethernet ports and 2 serial ports. 13.23.51 # <[av]bani> they are running uclinux in those constraints 13.23.58 # <[av]bani> so uclinux might not be such a bad starting point really 13.24.04 # yes, that's no problem. 13.24.15 # [IDC]Dragon: You were quite active with that Ondio challenge :) 13.24.42 # <[av]bani> you get a pre made multitasking kernel with full driver support already :) 13.26.02 # <[IDC]Dragon> amiconn: I still am 13.26.22 # <[av]bani> linux-2.6.8.1/arch/m68knommu/platform/5249/MOTOROLA/crt0_ram.S 13.28.44 # [IDC]Dragon: Two questions (1) The Ondio doesn't have an rtc? (2) Couldn't disassembling the archos fw help us? 13.29.11 # A related note: my Ondio is now on its way to me, via dpd... 13.29.35 # <[IDC]Dragon> (1) no RTC, (2) I don't think so 13.30.32 # [av]bani: yeah, but it's way too heavy to use for a simple mp3 player. 13.30.59 # but some of the drivers can be useful to look at 13.32.14 Join methangas [0] (methangas@0x50a4327e.virnxx10.adsl-dhcp.tele.dk) 13.33.14 Mode "#rockbox +o LinusN " by ChanServ (ChanServ@services.) 13.33.48 Topic "Sponsor the project: donate your broken iRiver iHP-1xx" by LinusN (~linus@labb.contactor.se) 13.37.29 # * ashridah notes that finding broken iriver players is likely to be a bit difficult until the average person's warranty is up. 13.37.40 # only early adopters are likely to have a broken unrepairable one. 13.38.57 Part [av]bani 13.39.30 # true 13.40.20 # darn. there's some broken flash iriver's on ebay, but that's it 13.42.00 # the warranty doesn't cover everything 13.42.04 # true 13.43.44 # they are selling very cheap new in the US. we could buy one there and have someone ship it. 13.44.28 # yeah 13.44.29 # yeah. the 1xx series is supposed to be discontinued, since they're primarily trying to sell the 3xx series. i imagine the 1xx's will get cheap, then rare, then expensive again :( 13.45.35 # cheapest i find is $275, which is about 60% of what we paid here 13.45.50 # if mine broke, i'd sell it to you guys for next to nothing plus shipping, provided you didn't want the hard drive (since if it was the hard drive that was broken, i'd just replace that, and keep it) 13.46.01 # $102.50! 13.46.22 # ? where? 13.46.23 # Zagor: are there any major differences between the 140 and 120 that you know of, minus the hard drive? 13.46.37 # http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=48683&item=5719792556&rd=1 13.46.47 # some pictures show different case color, but other than that I don't think so 13.47.19 # LinusN: yeah but that's just a bid, with 4 days to go. it will rise, nobody best this early. 13.47.23 # bids 13.47.27 # yeah, the casing is black paint, and some more recent kits come with a black leather cover, instead of brown. 13.47.44 # our 120 came with black leather 13.47.48 # http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=5719673428&category=48683&sspagename=rvi:1:2 13.48.16 # Zagor: did it? midly interesting. still, i imagine you guys got your own recently. 13.48.23 # yesterday 13.48.26 # yeah, yesterday :) 13.49.11 # yeah, the guy i know who got one with a black case got his a few months ago. mine is almost 6 months old now (bought it just after easter) 13.49.11 Quit maikeul ("Client exiting") 13.49.25 Join gromit`` [0] (~gromit@ALagny-151-1-45-137.w83-114.abo.wanadoo.fr) 14.00.16 Part LinusN 14.00.27 Join LinusN [0] (~linus@labb.contactor.se) 14.13.31 # [IDC]Dragon: #ifndef HAVE_NO_LED 14.13.38 # a bit backwards, isn't it? 14.13.51 # <[IDC]Dragon> ahem yes 14.13.55 # why now #ifdef HAVE_LED? 14.14.06 # not 14.14.09 # <[IDC]Dragon> should I change theother config files instead? 14.14.14 # absolutely 14.14.18 # <[IDC]Dragon> ok 14.14.35 # <[IDC]Dragon> no backlight is next ;-) 14.15.00 # <[IDC]Dragon> the LED was small, I put dummies in 14.15.15 # <[IDC]Dragon> but for the backlight, I don't like that too much 14.15.47 # [IDC]Dragon: Iirc we can get rid of the backlight thread? 14.16.26 # <[IDC]Dragon> but #ifdef bracketing every call to the backlight module also won't look good 14.16.59 # <[IDC]Dragon> any idea on how to carve this out the best way? 14.18.57 # you could put the #ifdefs in the backlight implementation, creating stubs instead 14.19.48 # <[IDC]Dragon> real stubs or empty macros (avoiding a call)? 14.20.15 # macros are fine with me 14.27.54 # [IDC]Dragon: I think emtpy macros are in fact a better way than #ifdefing everything. This could be used in a number of other places too (lcd_set_margins() comes to mind) 14.28.36 # <[IDC]Dragon> an empty inline function could give the same result, too 14.29.59 # One question is yet to solve: What if such an empty macro gets included into the plugin api struct? Does gcc generate a dummy function? 14.30.26 # <[IDC]Dragon> oops, sounds bad 14.30.41 # you will simply get a compile error 14.31.41 # Perhaps that works with the empty inline function approach. Iirc gcc does generate a non-inline variant for those cases where a pointer to that function is used 14.32.42 # A true empty function does only take 4 bytes (2 instrs) on sh1 (with gcc >= 3.3) 14.36.09 # We could in fact force the compiler to use the same empty function for all those cases by simply defining e.g. dummy_funct() { } and then defining macros for all other functions that are empty referring to dummy_funct() 14.36.40 # <[IDC]Dragon> bummer: my Ondio stuff was only compiling until I made a clean make :-( 14.37.09 # <[IDC]Dragon> now keyboard.c heavily fails for missing keys 14.40.37 # oops... 14.41.46 Nick midkay is now known as midk (~midk@c66-235-14-120.sea2.cablespeed.com) 14.42.38 # <[IDC]Dragon> defining them as the same like another will fail if both values are in a switch-case 14.45.49 *** Saving seen data "./dancer.seen" 14.52.44 # hmm, libmad uses memmove. not easy to workaround that... 14.53.27 # does the ondio use the same size screen, 112x64? 14.53.47 # <[IDC]Dragon> midk: yes 14.53.58 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 14.54.22 # hey bagder 14.54.27 # [IDC]Dragon: .rvf on the Ondio ;-) 14.54.36 # hi ho 14.56.29 # Zagor: memmove()...badness 14.56.54 # i'll just add it, it's a small function 14.56.59 # <[IDC]Dragon> overlapping, or why? 14.57.03 # yes 14.57.30 # doesn't look like a coincidence, it uses memcpy in other places and memmove in just two 14.57.31 # <[IDC]Dragon> ask amiconn, master of moving memory 14.57.45 # <[IDC]Dragon> maybe an oversight 14.57.58 # i don't think it is 15.00.20 # should we really fail scrambling when size >200kb? rolo can still load it. 15.00.45 # rockbox with libmad is 250kb 15.01.27 # methinks a warning should be enough 15.01.34 # <[IDC]Dragon> Zagor: are you testing if it compiles in our platform, or what's that for? 15.01.45 # precisely 15.02.08 # <[IDC]Dragon> won't run very fast ;-) 15.02.13 # i was also planning to let it decode a file to wav for testing 15.02.17 # how's the ondio work going? 15.02.21 # probably not, no :) 15.02.49 # <[IDC]Dragon> Bagder: fighting the special cases of having a recorder with limited keys 15.03.07 # so most of the drivers work then? 15.03.28 # <[IDC]Dragon> work? compile... 15.04.10 # <[IDC]Dragon> I'm gradually bringing in the differences for the port mapping 15.04.34 # <[IDC]Dragon> the parts I know of yet 15.04.56 # you're moving on fast, I like it 15.05.26 # <[IDC]Dragon> the bigger task is to write an MMC driver 15.05.41 # <[IDC]Dragon> API-compatible to our ATA 15.05.52 # ah, right 15.06.18 # <[IDC]Dragon> haven't started on that yet, but found nice code 15.06.26 Join kurzhaarrocker [0] (~knoppix@p508760AB.dip0.t-ipconnect.de) 15.08.31 # Just to restart an old flame war: When [IDC]Dragon experiences problems with the keys stuff - why not enhance the key api so that it supports _real_ hold_down_events and double_press events? 15.09.02 # <[IDC]Dragon> it may go that way 15.09.06 # how do you separate between hold_down and repeat? 15.09.57 # and even repeat and double-press 15.10.00 # and how do you separate single-click and double-click? 15.10.14 # gosh I really did start it :) 15.10.26 # we've had this discussion before 15.10.38 # but it's been a while 15.11.00 # Zagor: If it would be useful on SH1 too, I could extend memcpy.S to also include memmove. The memcpy routine could be reused for down-moving then, and the up-moving routine would use the same optimization techniques 15.11.08 # I remember that we had it. But my brain doesn't remember enything else about it, LinusN :) 15.11.16 # :-) 15.13.21 # Concerning repeat and hold_down: It would be the same thing, just the driver sending multiple events. Like pressed, hold_down, repeat, repeat, repeat..., released 15.13.29 # why? 15.14.26 # eg that handlers that are interested in hold_down only don't have to ignore consecutive repeat events 15.14.50 # the events will still come, even if we call them something else 15.15.30 # you're trying to solve a problem we don't have 15.15.46 # we have lots of real problems, i suggest you focus on them instead ;) 15.15.48 # yes, but then it would be the driver that filteres the events in one spont and not many event handlers that do the same filtering in many places. 15.16.05 # no the driver has no idea which events you want. it always sends all events. 15.16.11 # yes 15.16.56 # <[IDC]Dragon> you'll reach model-view-controller soon... ;-) 15.17.32 # <- admits that he is an oo programmer... 15.17.46 # :) 15.19.20 # But now that we want to support more platforms we might in fact want to introduce a layer of abstract events like ENTER_MENU that is generated by different hardware in different ways. 15.19.33 # * Bagder added the pretty pictures on the dl.cgi pages too 15.20.08 # yes, that is one option. we tried that in tree.c originally. it didn't work out 100% but it might be worth revisiting. 15.20.40 # <[IDC]Dragon> cu later 15.20.44 Quit [IDC]Dragon () 15.21.40 # the UI/button handling is actually one of the hairier issues, architecture wise, when adding new platforms 15.22.05 # LinusN: do you have an A-A usb cable? 15.22.15 # * kurzhaarrocker passes Zagor an electric shaver 15.22.31 # :) i could use a good one 15.23.39 # yes 15.23.45 # excellent 15.25.34 Join R3nTiL [0] (~zorroz@209-250-30-217.kgts.ru) 15.32.44 Quit Bagder ("Leaving") 15.35.04 # Zagor: Got my remark/ question concerning memmove? 15.35.44 Quit kurzhaarrocker ("Trillian (http://www.ceruleanstudios.com)") 15.41.21 Join karacho [0] (~d5c11321@labb.contactor.se) 15.42.06 # hi there 15.42.22 # everyone feelin comfortable ;) ? 15.42.46 # ? 15.43.11 # i've a question regarding spoken directories 15.43.25 # someone aware of that stuff? 15.45.33 # hm, myabe its a better bet to go with the mailinglist.... thx anyway 15.50.26 Quit karacho ("CGI:IRC") 15.53.49 # amiconn: yeah, but i don't think we'll need it for sh. if you're itching to optimise, look into the coldfire emac 15.55.15 # it is the key to good mp3, ogg and flac performance 15.57.27 Part LinusN 15.58.03 # my libmad image crashed horribly :) 15.58.22 # better fix it in the simulator first 15.59.46 # Fix fix! :D 15.59.49 # Hooray for Zag! 15.59.53 # Zagor makes the day! 16.00.08 # :) nice cheering 16.07.48 # Heja Zagor friskt humör, fixa iHP innan vi dör? :) 16.08.01 # Närå. Det behövs' it' 16.11.36 Join edx [0] (edx@pD9EAAF75.dip.t-dialin.net) 16.22.44 Quit R3nTiL () 16.26.57 # works nicely in the sim 16.31.07 # Hooray! 16.31.11 # Progress! 16.32.21 # gotta go 16.32.23 Part Zagor 16.40.25 Join [IDC]Dragon [0] (~idc-drago@pD9512274.dip.t-dialin.net) 16.41.35 # <[IDC]Dragon> Hey, I can browse the Rockbox menuonthe Ondio! 16.41.56 # <[IDC]Dragon> ..menu on the.. 16.42.45 # Great work! 16.43.19 # You're making the greased lightning appear like a bicycle when you're coding :) 16.43.39 # <[IDC]Dragon> no disk yet 16.43.46 # <[IDC]Dragon> USB mode to come 16.44.02 # <[IDC]Dragon> most workis left to do 16.44.13 # I'm thrilled you got it working this far :) 16.44.19 # <[IDC]Dragon> (sticky space bar) 16.45.53 *** Saving seen data "./dancer.seen" 16.56.23 # [IDC]Dragon: I guess PB14 and PB15 on Ondio are the same as with the jbrs. 16.57.11 # <[IDC]Dragon> probably 16.57.28 # <[IDC]Dragon> have you got you boy, or what leads you? 16.57.36 # <[IDC]Dragon> s/boy/box 16.58.37 # No box yet. Too bad this is sent via DPD, a bad solution to send something to someone's home 16.59.48 # I was lead to this by comparing the port pin tables for jbr and Ondio. All mas connections you discovered so far use the same port pins 17.02.52 Join webguest21 [0] (~91fee8b4@labb.contactor.se) 17.03.53 Quit webguest21 (Client Quit) 17.06.43 # ah, the joys of dodgy programming assignments ( http://yallara.cs.rmit.edu.au/~alpilley/snapshot4.png :) ) 17.08.05 # * ashridah notes he probably should have said that in #java, where he originally intended 17.12.45 # <[IDC]Dragon> ROM CRC is the well known one! 17.12.56 # <[IDC]Dragon> so I could uart-boot this 17.13.55 Join mecraw [0] (~lmarlow@69.2.235.2) 17.14.04 # [IDC]Dragon: You said uart boot is not possible because of the serial port already taken? 17.14.23 # <[IDC]Dragon> well, if you solder it away 17.14.48 # But then you'll have no mmc access, right? 17.14.55 # <[IDC]Dragon> maybe it can even be tapped at the MMC slot 17.15.10 Quit Lynx_ (" WOW! This IRC Client ownz! HydraIRC -> http://www.hydrairc.com <-") 17.15.14 # <[IDC]Dragon> uart_boot needs no MMC, gdb does 17.15.23 # <[IDC]Dragon> (maybe) 17.18.20 Join webguest30 [0] (~83a99624@labb.contactor.se) 17.19.38 Quit webguest30 (Client Quit) 17.26.48 # <[IDC]Dragon> I've uploaded an Ondio ajz now 17.29.04 # [IDC]Dragon: everything 17.29.09 # [IDC]Dragon: everything's working now? 17.29.40 # <[IDC]Dragon> haha 17.31.06 # why the haha? is _anything_ working yet? 17.31.37 # <[IDC]Dragon> see the twiki page, at the bottom 17.31.47 # <[IDC]Dragon> the main menu works 17.31.54 # that's a start 17.32.06 # <[IDC]Dragon> unless you do something which does disk I/O 17.32.21 # [IDC]Dragon: What flash id does the "hw info" menu item tell you? 17.33.06 # <[IDC]Dragon> BF D6 17.33.18 # <[IDC]Dragon> but I knew that, saw the chip 17.34.33 # <[IDC]Dragon> they are probably all flashable, since Archos provides a .ajz which does a flash upgrade 17.34.53 # <[IDC]Dragon> a flashable flash player ;-) 17.37.42 # a 1gb mmc card is only about $100 -- that is a nice player for that size. 17.38.28 # <[IDC]Dragon> a 40 GB disk is also ~$100 :-/ 17.42.22 Quit [IDC]Dragon () 17.49.27 Join Elemeno [0] (~4givn@dpc691997050.direcpc.com) 17.49.38 # Hi folks 17.50.39 # I'm looking for a replacement mic for my FM recorder. Any suggestions where to look? 17.54.34 Join Zagor [0] (~bjst@h254n2fls31o265.telia.com) 18.03.56 # whee, the produced pcm file actually sounds great 18.04.07 # now why does it crash on the sh... 18.07.34 # i wonder if the iriver firmware uses all 24 bits of the dac 18.11.45 # Zagor: Perhaps too small a stack? 18.12.21 # well the thing is my .ajz doesn't even boot, so it's not a problem with the libmad code per se. rather with the build. 18.12.43 # well it boots and shows the logo, but crashed before the browser 18.16.31 # ahh, worked a little better now. decoding started, then crashed on completion. 18.17.12 # that could be a stack issue. but the display is totally cleared, which is a bit odd 18.17.51 Join R3nTiL [0] (~zorroz@229-248-30-217.kgts.ru) 18.22.56 # Zagor: Stack issue usually cause all sorts of weird effects: When I implemented my improved screen_dump() I first tried to allocate the 1-row buffer on the stack as well. This lead to a stack overflow, and I got "IllInstr". Now the buffer is static 18.24.24 # i'm a bit worried about the absence of an error message though. the led is blinking but the screen is clear 18.30.46 # hahaaa, success. let's hear it... 18.31.05 # Perhaps it crashes in a way the breaks the lcd routine(s). If it crashes by an unhandled interrupt, the screen usually allows rolo reboot. However, this doesn't work most of the time... 18.31.19 # * ashridah hands zagor the cookie of success 18.31.19 # Zagor: I'm listening... 18.32.36 Quit ashridah ("sleep") 18.33.07 # gahh, typical. now my computer won't mount the usb disk :-{ 18.35.14 # wheee, works! 18.35.57 # it's horribly slow though... 18.36.41 # but that was expected 18.45.54 *** Saving seen data "./dancer.seen" 18.48.12 Quit Elemeno () 18.48.35 Quit R3nTiL (Read error: 104 (Connection reset by peer)) 19.53.42 Join LinusN [0] (~linus@labb.contactor.se) 20.37.49 Part LinusN 20.45.55 *** Saving seen data "./dancer.seen" 20.48.24 # hmmm, how about a mod player... 20.50.00 Join lImbus_ [0] (lImbus@103.184-200-80.adsl.skynet.be) 20.50.36 # Zagor: That would be really cool, too bad that we don't have access to that pcm pass-through module for the mas :( 20.50.47 # yeah :( 20.51.10 Join benschi [0] (~3edaa308@labb.contactor.se) 20.51.16 # But on iriver this sounds like it would be easy once the firmware runs 20.52.02 # Especially as the Iriver is coldfire, and the .mod format emerged from Amiga, which is 68k... 20.53.17 # well the format isn't particularly 68k-specific other than endianness 20.54.23 # mama mia. libmodplug is *huge*! 20.54.31 # * Zagor goes looking for something smaller 20.54.38 # zagor 20.54.40 # whats up? 20.54.44 Quit lImbus (Nick collision from services.) 20.54.48 # is everything running like it should? 20.54.55 Nick lImbus_ is now known as lImbus (lImbus@103.184-200-80.adsl.skynet.be) 20.55.20 # benschi: yeah, pretty much. i just got the mp3 decoder running in the simulator and on the archos 20.56.22 # we still don't know which display controller it is (although Dave Hooper has made a good guess that might work out) 20.56.54 # ...and we really would like to get our hands on a broken ihp to remove the cpu from, so we can make proper schematics 20.56.55 # Zagor: No, .mod isn't 68k specific, but there are many implementations for 68k, even space-saving ones 20.57.09 # true 20.57.56 # Remember that it was possible to play (4 channel mods) even on a stock Amiga 500 with only 512K of ram 20.58.16 # zagor, kewl.. 20.58.17 # yeah, mods require very little procesing 20.58.22 # sorry, i dont own a broken ihp 20.58.30 # and also nobody of my firends.. 20.58.35 # (i've actually written music with an amiga tracker myself) 20.58.55 # but, how long do you think, will it take to get the firmware running on the ihp? only calculations..?? 20.58.59 # Zagor: The only thing that needs additional processing on recent equipment is the stereo downmix 21.00.17 # once again, it might be worth to take a look at foobar's code :) Peter Pawloski is a huge fan of tracker tunes himself 21.01.17 # benschi: it will take time. months. 21.01.25 # ok :-) 21.01.33 # foobar, is that the winamp-clone by the nullsoft-developer ? 21.01.34 # hope you get the thing done! 21.01.53 # by ex nullsoft employee, PP yep 21.02.10 # and by that definition, anything that plays mp3 is a "winamp clone" 21.02.14 # pike: yeah, i have the fb2k code here too 21.02.41 # Zagor: The similarity between coldfire and 68k may even enable to play module formats which contain some replay code 21.02.48 # benschi: so do I :) 21.03.12 # and amiga demos ;) 21.03.29 # having been an amiga "addict" the 68k "stamp" doesnt exactly signal "speed" 21.03.44 # Zagor ;) 21.03.54 # the emac helps to speed up calculations a bit 21.04.23 # I remember the good ol' days.. mp3, downsampled to mono and 22.05 kHz and played back on my 68030 accelerated amiga 21.04.55 # I play mp3s with full resolution on my amiga :) 21.06.09 # have fun. bbl 21.10.04 # Zagor [OT]: Has dancer already reported been running on Windows2003 ? 21.10.30 # it quits before writing one line of logfile. but touches, and modifies dancer.users 21.10.46 # i don't know. i've only ran it on linux. 21.11.01 # sh*t 21.17.00 Join HenrikB [0] (~HenrikB@as4-2-2.sjom.b.bonet.se) 21.20.35 # Hi! 21.20.42 # hi 21.22.34 # I'm playing around with the check of the .rockbox dir on startup 21.22.55 # huh? "ColdFire FPU Instruction Set"??? -- CF Programmers Reference Manual 21.23.56 # I've goten the playlist code to play a playlist without a control.file 21.23.57 # HenrikB: anything in particular? 21.25.06 # and it shows the missing .rockbox dir message every time you play a playlist if .rockbox is missing 21.25.36 # You of course also get the message on startup 21.26.24 # ah, the 5400 series have fpu 21.28.37 # It is complaing on startup and every time you play a playlist but basics like navigating the disk and playing a single playlist/dirctory works 21.30.29 # HenrikB: sorry i'm not following you. what are you trying to do/fix/find? 21.32.30 # I'm trying to give better feedback to users who have forgotten to copy the .rockbox directory on installation 21.32.40 # ah, ok 21.34.45 # HenrikB: What's about our old patch, 848904 (modified boot file detection)? 21.37.20 # It saves the size and cluster of the bootfile in settings so bootfile detection also works when you power on with the usb cable connected 21.40.09 # I know what it does from the description, but it is still open... 21.42.10 # I think there was a feature when I created it and since I've not gotten much feedback I've not commited it 21.42.32 # I know, I should be onth IRC more to get feedback 21.42.53 # s/feature/feature freeze/ 21.48.25 # i don't think i ever really understood the purpose of patch #848904 21.50.54 # It's only a small improvment on the changed bootfile detection. 21.51.43 # Today if you poeron if the usb cable coneccted and copies a ajbrec file it is not detected as a new bootfile 21.52.04 # s/poeron/power on/ 21.53.18 # i know. i'm just not convinced we need to spend configuration data and code to fix that. the boot check was just a quick convenience hack during development. 21.54.04 # If you aren't going to commit that, you could close it instead. That's what I did with my asm-optimized memcmp(), as memcmp is only used in a few places. If somebody later decides that it would be useful, the patch will still be there 21.54.48 # Yeah I know, thats why I have'nt commited it. 21.54.59 # amiconn, I'll do that 22.01.55 Join scott666 [0] (~scott666@c-24-245-58-48.mn.client2.attbi.com) 22.07.03 Quit benschi ("CGI:IRC (Ping timeout)") 22.11.03 Quit silencer_ (Read error: 104 (Connection reset by peer)) 22.13.18 Join silencer [0] (~silencer@zen.via.ecp.fr) 22.31.15 # Zagor, amiconn Should I add the the .rockbox check to playlist so we get a "No .rockbox directory, Installation incomplete" message instead of "error accessing playlist control file" 22.31.37 # sounds like a good idea 22.34.03 # I agree, although the necessity of a .rockbox directory and continued complaints if it is missing could get very annoying on the Ondio 22.35.34 Join zeekoe [0] (~zeekoe@ip51cc69f6.adsl-surfen.hetnet.nl) 22.36.23 # got the mod player down to 108 kb 22.36.41 # (by removing support for lots of obscure formats) 22.37.07 Join Bagder [0] (~daniel@1-1-5-26a.hud.sth.bostream.se) 22.37.10 # amiconn, Of course, but the hard part is not removing the check, it is "downsizing" the playlist code for Ondio 22.37.21 # yo bro 22.37.25 # evening 22.41.58 # the bad thing about libmodplug is that it's written in c++... 22.44.52 # as usual it's mainly C in classes though, so it won't be much work to sanitize 22.45.57 *** Saving seen data "./dancer.seen" 22.54.19 Join amiconn_ [0] (~jens@pD95D1741.dip.t-dialin.net) 22.58.46 Quit amiconn (Nick collision from services.) 22.58.46 Nick amiconn_ is now known as amiconn (~jens@pD95D1741.dip.t-dialin.net) 23.11.00 # Bedtime, goodnight. 23.11.07 # night 23.14.03 Quit HenrikB ("Lämnar") 23.16.53 # * zeekoe is away: 23.32.36 # * zeekoe is back (gone 00:15:44) 23.45.20 Join _Lucretia_ [0] (~munkee@abyss2.demon.co.uk) 23.45.25 # <_Lucretia_> hi 23.45.39 # hi 23.45.41 # <_Lucretia_> does anyone know if the Xclef MT-500 will be supported at all? 23.45.53 # <_Lucretia_> the current firmware is pretty sucky 23.45.58 # it's impossible to say 23.46.05 # if someone digs up enough info, it might 23.46.09 # <_Lucretia_> well, i've emailed them 23.46.13 # <_Lucretia_> no response yet 23.46.13 # the hardware is quite similar to the iriver 23.46.18 # emailed who? 23.46.24 # <_Lucretia_> Xclef 23.46.27 # ok 23.46.33 # <_Lucretia_> for specs 23.46.44 # don't hold your breath :) 23.47.18 # <_Lucretia_> i'd do the work if I could 1) get the specs 2) be guaranteed that I can't fuck up the machine (I use it daily) 23.47.25 # <_Lucretia_> I'm not holding my breth 23.47.27 # <_Lucretia_> breath 23.47.43 # <_Lucretia_> I doubt I'll get it, but would love to see better firmware...oh well 23.47.58 # <_Lucretia_> I take it nobody has opened one up and checked the hw? 23.48.00 # 2) is pretty difficult to guarantee 23.48.13 # <_Lucretia_> depends 23.48.15 # we would all cheer and enjoy supporting xclef 23.48.25 # yes, it's pretty similar to the iriver. coldfire-based. 23.48.40 # <_Lucretia_> if the device is designed such that there is a basic firmware that cannot be overwritten and handles the writing on flash 23.49.00 # <_Lucretia_> on = of 23.49.07 # see http://rockbox.haxx.se/twiki/bin/view/Main/XclefInfo 23.49.11 # <_Lucretia_> then it it *should* be possible to not shag it 23.50.16 Quit edx ("go4ioi") 23.50.16 # <_Lucretia_> these are only hdd based devices, the mt-500 is solid state 23.51.00 # oh, ok 23.51.23 # we are mostly into hd-based units 23.51.23 Join Dma-Sc [0] (~Dma-Sc@ALagny-151-1-34-203.w83-114.abo.wanadoo.fr) 23.51.45 # hi 23.51.49 # hi 23.52.20 # not much to say, expecting that you guys rule damn big :) 23.52.36 # hehe 23.52.45 # :) thanks 23.53.12 # you made my Archos JB Player work like a breeze 23.53.56 # and now that it died and that i bought a H120, i read that you're working on it, so neat :) 23.54.47 # well, cross your fingers and hope for the best :) 23.55.22 # <_Lucretia_> Zagor, no reason not to support the solid state stuff tho ;-) 23.55.39 # <_Lucretia_> ...but anyways 23.55.46 # sidplay looks like it can be difficult to support. in "fast mode" it requires a pentium 166. 23.56.07 # zagor : eh yep, let's hope it won't use a chip you couldn't identify ;) 23.56.31 # zagor : is iriver like archos? giving no hw infos? 23.56.32 # Dma-Sc: we've found all of them except the display controller 23.56.48 # Dma-Sc: yes, like nearly all companies (except neuros) 23.57.22 # _Lucretia_: well our days only have 24 hours ;) 23.57.29 # kind of ironic the one single company who publicize their info uses a dead-expensive dev-environment 23.57.54 # Bagder: yeah. they are not happy about it either. 23.58.03 # Zagor: SID shouldn't be a problem on coldfire, since an 68060 @50 MHz can do it without much processor load 23.58.20 # those guys are so dumb, it save them some work if a great firmware is developped but no they don't give a shit about it 23.58.28 # amiconn: yeah, using 68k assembler