--- Log for 02.11.103 Server: zelazny.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16p1 Started: 7 days and 20 hours ago 00.01.47 Quit track ("Leaving") 00.08.46 # bbiab 00.08.53 # gl on the patching 00.08.57 Quit Kontakt501 ("[I was using Polaris 2002] Version:[1.0] Webpage:[http://www.polaris-central.com]") 00.13.25 Quit cjnr11 () 00.20.52 Quit edx () 00.24.54 Join scott|sleeep [0] (scott666@c-24-245-58-245.mn.client2.attbi.com) 00.27.29 Join man-e [0] (man-e@bzq-218-37-19.cablep.bezeqint.net) 00.27.38 # hello 00.27.42 # hey 00.27.48 # how r u all ? 00.28.26 # mmm.. I guess all r sleeeeepy, eh ? 00.28.44 # thats about it 00.29.14 # well, atleast ur alive! 00.29.19 # :) 00.29.38 # hooray 00.30.08 # say, are u speaking to anyone on the channel right now ? (cept me) 00.31.16 # o....k.... 00.31.21 # oh, silence 00.31.34 # makes you wonder 00.31.38 # about things 00.32.34 # ok, bye 00.32.48 Quit man-e () 00.37.32 Join man-e [0] (man-e@bzq-218-37-19.cablep.bezeqint.net) 00.41.15 Quit man-e (Client Quit) 00.45.58 Quit midknight2k3 (Read error: 110 (Connection timed out)) 00.57.26 Join track [0] (jirc@ACBDBF1A.ipt.aol.com) 01.03.46 Quit track ("Leaving") 01.06.26 *** Saving seen data "./dancer.seen" 01.11.41 Quit Dogger ("Client Exiting") 01.33.05 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 01.33.18 Part mad8k 01.33.28 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 02.06.51 Join midknight2k3 [0] (midknight2@12-229-204-15.client.attbi.com) 02.07.02 # hi 02.58.50 Quit midknight2k3 ("Time to go now...") 02.58.57 Quit top_bloke (Read error: 104 (Connection reset by peer)) 02.59.02 Quit k3no (Read error: 54 (Connection reset by peer)) 03.00.26 Join k3no [0] (mcbc@80.178.44.168.forward.012.net.il) 03.06.28 *** Saving seen data "./dancer.seen" 03.28.52 Join top_bloke [0] (~Email@dsc02-chc-il-209-109-230-61.rasserver.net) 04.13.05 Join midknight2k3 [0] (midknight2@12-229-204-15.client.attbi.com) 04.13.14 # linus, aer you around? 04.14.11 Quit top_bloke (Read error: 104 (Connection reset by peer)) 04.30.45 Quit mad8k (Read error: 110 (Connection timed out)) 04.34.05 Join k3no_ [0] (~hosted@80.178.44.168.forward.012.net.il) 04.34.06 Quit k3no (Read error: 54 (Connection reset by peer)) 04.51.24 # ok, anyone here who can program? 04.51.25 Quit k3no_ (Read error: 104 (Connection reset by peer)) 04.51.52 Join k3no_ [0] (azsg@80.178.44.168.forward.012.net.il) 04.53.54 # hi k3no_ 04.59.33 Nick midknight2k3 is now known as midk2k3 (midknight2@12-229-204-15.client.attbi.com) 05.06.30 *** Saving seen data "./dancer.seen" 05.29.39 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 05.42.52 Join k3no [0] (~hosted@80.178.44.168.forward.012.net.il) 05.43.13 Quit k3no_ (Read error: 104 (Connection reset by peer)) 06.11.07 # AHAHAHAHAH! 06.11.09 # I GOT IT! 06.11.11 # BWAHA! 06.19.39 Quit mad8k (Read error: 60 (Operation timed out)) 07.06.32 *** Saving seen data "./dancer.seen" 07.16.02 # linus! 07.39.28 Quit k3no (Read error: 110 (Connection timed out)) 07.40.59 Join Dogger [0] (~jimmy@cpc2-colc1-5-0-cust169.colc.cable.ntl.com) 07.42.55 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 08.20.45 Quit midk2k3 ("Time to go now...") 08.42.43 Quit Dogger ("Client Exiting") 08.43.13 Join k3no [0] (~hosted@80.178.44.204.forward.012.net.il) 08.46.50 Join midknight2k3 [0] (midknight2@12-229-204-15.client.attbi.com) 08.46.53 # hello! 09.06.33 *** Saving seen data "./dancer.seen" 09.58.20 Join mad9k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 10.01.14 Quit midknight2k3 ("Time to go now...") 10.01.15 Join midk2k3 [0] (midknight2@12-229-204-15.client.attbi.com) 10.01.17 Quit midk2k3 (Read error: 54 (Connection reset by peer)) 10.01.30 Join midknight2k3 [0] (midknight2@12-229-204-15.client.attbi.com) 10.06.52 Quit mad8k (Read error: 60 (Operation timed out)) 10.23.35 Join edx [0] (edx@pD9EAA638.dip.t-dialin.net) 10.24.24 # hi edx 10.24.32 # yo 10.25.02 # :>) 10.26.13 # : :<>() 10.28.51 Join cjnr11 [0] (nmp@l01m-56-20.d1.club-internet.fr) 10.30.02 # hello 10.32.07 Quit mad9k (Read error: 60 (Operation timed out)) 10.34.22 # hi 10.40.21 Quit k3no (Read error: 54 (Connection reset by peer)) 10.43.27 Join k3no [0] (~hosted@80.178.44.204.forward.012.net.il) 10.58.35 Quit midknight2k3 ("midknight2k3 yawns a lot") 11.01.24 Join k3no_ [0] (~hosted@80.178.44.204.forward.012.net.il) 11.01.50 Quit k3no (Read error: 104 (Connection reset by peer)) 11.06.37 *** Saving seen data "./dancer.seen" 11.06.58 Quit adi|home (zelazny.freenode.net irc.freenode.net) 11.06.58 NSplit zelazny.freenode.net irc.freenode.net 11.08.25 NHeal zelazny.freenode.net irc.freenode.net 11.08.25 NJoin adi|home [0] (~adi|home@as5300-9.216-194-23-188.nyc.ny.metconnect.net) 11.25.56 Join track [0] (jirc@ACBBAD94.ipt.aol.com) 11.29.16 Quit track (Client Quit) 11.42.23 Join track [0] (jirc@ACBBAD94.ipt.aol.com) 11.42.27 # hi 11.45.43 # hi webmiond 12.07.33 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 12.09.40 # hi 12.14.38 Join k3no [0] (~hosted@80.178.44.225.forward.012.net.il) 12.25.12 Nick LinusN|brb is now known as LinusN|away (~linus@labb.contactor.se) 12.28.56 Quit track ("Leaving") 12.29.48 Quit k3no_ (Read error: 110 (Connection timed out)) 13.06.39 *** Saving seen data "./dancer.seen" 13.09.39 Join dsg [0] (~david@pasky.xs4all.nl) 13.18.12 Quit mad8k (Read error: 60 (Operation timed out)) 13.26.33 Join Dogger [0] (~jimmy@cpc2-colc1-5-0-cust169.colc.cable.ntl.com) 13.54.32 Quit Dogger ("Client Exiting") 14.20.41 Quit dsg (Read error: 110 (Connection timed out)) 14.25.47 Join dsg [0] (~david@pasky.xs4all.nl) 14.28.39 Quit cjnr11 (Client Quit) 14.28.40 Join cjnr11 [0] (nmp@l01m-56-20.d1.club-internet.fr) 14.28.45 Quit cjnr11 (Client Quit) 14.28.57 Join cjnr11 [0] (nmp@l01m-56-20.d1.club-internet.fr) 14.29.02 Quit cjnr11 (Client Quit) 14.29.18 Join cjnr11 [0] (nmpjhb@l01m-56-20.d1.club-internet.fr) 14.30.28 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 14.33.29 Join mjh [0] (isildur@tel22.newn.cam.ac.uk) 14.37.27 Quit MKoool ("[BX] The Invisible Man uses BitchX, you just can't see it!") 14.42.47 Nick LinusN|away is now known as LinusN (~linus@labb.contactor.se) 14.49.59 # does anyone happen to know whether Zagor ever managed to get hold of a PortalPlayer spec sheet? 14.50.03 # (further to "15.03.19 # elinenbe: yes, I noticed. I just signed up for a PortalPlayer data sheet :-)" at http://rockbox.haxx.se/irc/rockbox-20030204.txt) 14.51.44 # no idea 14.51.59 # what is a portalplayer? 14.52.46 # the ARM-based chipset used in iPods 14.53.01 # oh 14.53.17 # there was a short flurry of discussion as to whether rockbox could ever run on them a while back (as per that log, which I just found through Google) 14.54.01 # aha, i haven't heard anything 14.54.27 # * mjh nods 14.54.31 # fair enough :) 14.55.48 Join k3no_ [0] (~hosted@80.178.33.189.forward.012.net.il) 15.06.42 *** Saving seen data "./dancer.seen" 15.13.49 Join [IDC]Dragon [0] (~idc-drago@pD9E34F60.dip.t-dialin.net) 15.14.06 Quit k3no (Read error: 104 (Connection reset by peer)) 15.14.10 # <[IDC]Dragon> Hi there! 15.14.59 # <[IDC]Dragon> Linus, do you read? 15.15.37 # <[IDC]Dragon> In case you will: 15.16.03 # <[IDC]Dragon> I'm looking at the settings load/save, being desperate for RTC bits. 15.16.44 # <[IDC]Dragon> I want to mave the charging settings there, to have them avail. before disk spinup. 15.17.04 # <[IDC]Dragon> s/mave/move 15.19.19 # <[IDC]Dragon> I have an idea of how to make this load/save code more simple and efficient (Some days ago I was discussing this with Zagor): 15.19.48 # <[IDC]Dragon> Use the 44 bytes as a stream of bits, not caring for byte boundaries. 15.20.07 # <[IDC]Dragon> Then write each item with the number of bits it needs. 15.20.53 # i'm listening 15.20.57 # <[IDC]Dragon> This way we don't "waste" bits. 15.21.06 # <[IDC]Dragon> ;-) 15.21.53 # <[IDC]Dragon> Why is this checking for 0xFF in each byte? Either the settings are checksummed valid or not. 15.22.15 # the checksum is calculated on all bytes, unused or not 15.22.20 # unused bytes are 0xff 15.22.21 Quit mad8k (Read error: 60 (Operation timed out)) 15.22.47 # so when we introduce a new option, the byte may be empty==unused, but the checksum is still valid 15.23.06 # however, bumping the revision solves that problem 15.23.25 # <[IDC]Dragon> yes, I thought you do this each time. 15.23.42 # we originally had the intention not to bump the revision 15.24.00 # so yes, we can make this much simpler 15.24.08 # <[IDC]Dragon> How would you like my bitstreaming? 15.24.28 # <[IDC]Dragon> I'll code it, don't worry 15.24.36 # sure, if it is elegant 15.24.54 # <[IDC]Dragon> There could be a table with all entries 15.25.06 # <[IDC]Dragon> and a generic code that walks it. 15.25.49 # performance? 15.26.05 # <[IDC]Dragon> Is that an issue here? 15.26.52 # not really 15.27.18 # the resume function writes to the RTC every other second or so 15.27.57 # <[IDC]Dragon> Why do the non-RTC values start so late, at 0xA8 ? 15.30.06 # <[IDC]Dragon> Something inbetween I'm missing? 15.30.14 # the top values grow backwards 15.30.35 # <[IDC]Dragon> Ah, I see. 15.31.24 # <[IDC]Dragon> I'm also missing the resume filename, which would be a variable length entry. 15.32.34 # why variable? 15.32.56 # <[IDC]Dragon> or at least limited size. 15.33.25 # <[IDC]Dragon> could be a very long pathname 15.33.37 # it is in a separate sector, iirc 15.36.37 # i am silly 15.36.44 # we don't save the file name 15.37.14 # <[IDC]Dragon> I could make a rtc_write_multiple, that would probably increase the save time a lot. 15.37.24 # that would be nice 15.38.46 # <[IDC]Dragon> No filename? I thought Zagor mentioned it, as the "clean" solution opposed to a sector # 15.38.59 # <---braindead 15.41.56 # <[IDC]Dragon> ??? 15.42.53 # the dynamic playlists changes the resume behaviour 15.43.33 # <[IDC]Dragon> another "???" 15.43.40 # the resume track info is in the .playlist_control file 15.43.44 # <[IDC]Dragon> but perhaps I should not worry. 15.44.05 # <[IDC]Dragon> Then I don't worry. 15.44.22 # only the index and time offset is in RTC 15.47.04 # moin 15.47.10 # moo 15.47.59 # <[IDC]Dragon> So, would it be OK to go ahead with my serialization? 15.48.27 # if it makes the code simpler, yes 15.48.40 # <[IDC]Dragon> it shure does ;-) 15.49.12 # <[IDC]Dragon> The question coming up again it: what do we do withnew values growing in? 15.49.36 # we will move to a config file approach 15.49.47 # only "real-time" values will stay in RTC 15.49.56 # like the resume info 15.50.08 # <[IDC]Dragon> and the "early" stuff 15.50.24 # ...will be moved to the config file 15.50.32 # some day 15.50.46 # if you like, you can work on that as well 15.50.47 # <[IDC]Dragon> which you can't read befor you have HD 15.51.13 # values you will need before the HD can be read must stay in RTC 15.51.40 # remember that Players don't have RTC 15.51.58 # <[IDC]Dragon> but they also have no charge control 15.52.07 # true 15.52.30 # <[IDC]Dragon> It's the charging I'm trying to fiy here in the first place. 15.52.41 # <[IDC]Dragon> s/fiy/fix 15.53.14 Nick [OFF]BtT is now known as [GoE]BENtheTEN (~quasi@80.238.199.45) 15.53.37 # <[IDC]Dragon> OK, thanks for your time. 16.00.24 Join uski [0] (~moo@gandalf.digital-network.org) 16.00.36 # hi 16.01.15 # hi 16.01.35 # <[IDC]Dragon> hi 16.06.10 # <[IDC]Dragon> Linus, I assume that bool values in a struct won't get packed? Meaning, I can pass pointers to those? 16.06.37 # i believe so 16.07.19 # i'm trying to figure out why you can't charge a flashed recorder with flat batteries 16.07.36 # <[IDC]Dragon> FM or Rec? 16.07.39 # rec 16.08.12 # <[IDC]Dragon> because it's too weak to start the CPU part? 16.08.20 Join striders [0] (nobodie@languedoc-1-82-66-83-142.fbx.proxad.net) 16.08.23 # hi all 16.08.27 # it shouldn't be too weak 16.08.34 # the cpu can run from the AC alone 16.08.39 # hi striders 16.08.55 # <[IDC]Dragon> I'm not shure where to sort those postings, if flashing really made something worse. 16.09.02 # sorry to bother u again 16.09.24 # but is it worse and worse 16.09.31 # what is? 16.09.36 # i cannot boot my archos anymore 16.09.47 # <[IDC]Dragon> Is that our subject? 16.09.49 # I format it through Win2k sp4 in fat32 16.10.02 # <[IDC]Dragon> then it isn't. 16.10.20 # ok i let u finish 16.10.39 # striders: player or recorder? 16.10.40 # sorry about that 16.10.48 # <[IDC]Dragon> Go ahead. 16.10.54 # Jukebox recorder 20 16.11.02 # [IDC]Dragon: it doesn't look like it is charging at all... 16.11.14 # striders: what does the archos say? 16.11.26 # when the archos is booting (os version 1.28), really bad noise of the hard drive 16.11.32 # read access error 16.11.38 # can't access hard drive 16.11.42 # striders: hardware problem ? i.e. defectuous drive ? 16.11.48 # i think so 16.11.50 # plus clairement, ton disque est niqué ? 16.11.51 # :) 16.11.52 # the bad noise could be a bad hard drive or bad batteries 16.11.52 # but it is a brand new archos 16.11.52 # <[IDC]Dragon> sounds like harware problem 16.12.02 # i return my former archos for a similar problem 16.12.09 # striders: yea but new archos might have problems 16.12.09 # the send me a new one 16.12.12 # lol perhaps they returned you the same 16.12.39 # when i start to test it, i full the hard drive but at the end of the copy 16.12.49 # striders: is it different when you boot with the charger attached or not? 16.12.49 # windows said me unable to copy... 16.12.57 # i try 16.13.12 # battery charging 16.13.19 # now i press the button on 16.13.59 # nope, only creaking of the hard drive :/ 16.14.14 # wow, and connecting it via USB works? 16.14.20 # nothing 16.14.31 # because i cannot reach this state 16.14.37 # then hod did you format the drive? 16.14.40 # how 16.14.48 # what does happen if you connect the HDD on the USB port ? 16.14.53 # the archos i mean 16.14.53 # i try 16.14.57 # ok, try 16.15.05 # i format the hard drive through win2k 16.15.11 # and after do a scandisk 16.15.41 # you mean that you removed the hard drive and put it in your PC? 16.15.47 # nope 16.15.52 # i reboot 16.15.55 # striders: tu es français ? 16.15.59 # ui 16.16.05 # pv, i will translate 16.16.21 # <[IDC]Dragon> LinusN: did you experience the non-charging? Was that with Rockbox or Archos charging screen? Or trying to startup with HD? 16.16.47 # not sure now, it seems to be charging 16.17.05 # <[IDC]Dragon> Yours? 16.17.05 # i inserted a set of batteries that i knew were flat 16.17.26 # i connected the charger and it started charging, everything seemed ok 16.17.46 # after a while, i discovered that the jukebox had shut off 16.17.53 # and now it can't boot 16.18.19 # it works with a set of non-flat batteries 16.18.21 # <[IDC]Dragon> It should not shut off. 16.18.27 # i know :-) 16.18.42 # <[IDC]Dragon> Can't boot even into charging screen? 16.18.45 # i guess something is draining the batteries 16.18.48 # nope 16.18.55 # the green led blinks 16.18.58 # ead screen 16.18.59 # dead 16.19.26 # <[IDC]Dragon> I've never tried with flat cells. 16.19.31 # when i insert the charger with fresh batteries, i can hear the hd beginning to spin up 16.19.42 # then it stops when the charging screen appears 16.19.52 # perhaps the firmware tries to start the HDD, thus killing the power from the batteries ? 16.20.09 # <[IDC]Dragon> Maybe I should switch on charging within the bootloader 16.20.20 # no 16.20.41 # we should rewrite the power management code 16.20.50 # it takes it up to a minute to start charging 16.20.53 # <[IDC]Dragon> Are you shure it got there? 16.20.55 # silly 16.21.09 # got where? 16.21.19 # <[IDC]Dragon> into the power code 16.21.53 # not sure 16.22.12 # well, i think it's power_init() that starts the hd 16.22.40 # <[IDC]Dragon> Oops: 16.22.52 # <[IDC]Dragon> The HD is on since the bootloader. 16.23.08 # <[IDC]Dragon> The charging sreen shuts it down again. 16.23.31 # what does the boot loader do with the ata power pin? 16.23.49 # <[IDC]Dragon> Nothing, the disk is on by hardware default. 16.24.06 # how silly 16.24.19 # we should turn it off asap 16.24.19 # <[IDC]Dragon> I liked it, gives faster start. 16.24.44 # [IDC]Dragon: why not turning the HDD on or off, depending of the voltage of the battery ? 16.25.03 # <[IDC]Dragon> yes, that might be an idea. 16.25.18 # i'm not all fond of that idea 16.25.28 # <[IDC]Dragon> But it makes the bootloader too intelligent. 16.25.36 # the battery voltage measurement is not all that accurate 16.25.58 # and i don't like when the code is, like [IDC]Dragon said, too intelligent 16.26.55 # you could make sure that the voltage is well higher than the margin of error 16.27.08 # that's what i mean 16.27.17 # hmm 16.27.27 # yes but currently 16.27.32 # if you don't do this in the bootloader 16.27.35 # then the user won't be able to use the hd, even if his batteries might have been sufficient 16.27.36 # you cannot fix the issue 16.27.43 # => power => start hdd => voltage drop => boom 16.28.06 # we can't init it later? 16.28.17 # that's what we are discussing 16.28.32 # the boot loader should shut if off as soon as possible 16.28.38 # yes 16.28.44 # could we move the init to after the charging screen finishes? 16.28.45 # <[IDC]Dragon> There's nothing bad if the bootloader leaves with the HD off, it just has to be turned on again later. Boot time is a bit longer than. 16.28.48 # and the "main" code should check the voltage, or start charging 16.28.50 # scott|sleeep: that's where it is 16.29.03 Nick scott|sleeep is now known as scott666 (scott666@c-24-245-58-245.mn.client2.attbi.com) 16.29.21 # the HD is on by mistake as it is today 16.29.50 # [IDC]Dragon: is the boot loader in cvs? 16.30.07 Quit striders ("Thanx RockBox !!") 16.30.18 # <[IDC]Dragon> no, but available in my source pack. 16.30.23 # (fyi, striders will send back his archos) 16.30.41 # uski: ok 16.30.44 # <[IDC]Dragon> http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_sourcecode.zip 16.31.27 # wow, the sourceforge anon cvs is up-to-date again 16.32.30 # [IDC]Dragon: i leave it up to you to fix it, just make sure that the hd is off by default 16.33.42 # <[IDC]Dragon> Hmm, what a pit for the boot time. Probably costs an extra second. 16.33.46 # <[IDC]Dragon> pity 16.33.50 Quit uski ("BRB") 16.34.10 # probably... :-( 16.34.35 # <[IDC]Dragon> How about powering it down only when I detect the charger? 16.34.53 # sure 16.35.38 # <[IDC]Dragon> That's a nice one, independent of voltage readings, etc. 16.35.52 # yeah 16.37.03 # <[IDC]Dragon> Next thing to fix is probably us powering up the disk, not shure that's done. 16.37.39 # should be done in ata_init 16.37.47 # <[IDC]Dragon> agreed. 16.38.27 # <[IDC]Dragon> I'm not shure how this disk powering goes for all the platforms. 16.38.43 # <[IDC]Dragon> I've been very unsuccessful with the Player. 16.38.45 # oh, it is already done when charging_screen() exits 16.39.02 # ide_power_enable(true); 16.39.03 # <[IDC]Dragon> Ah yes, I needed that. 16.39.40 # power_init() shuts it off 16.39.52 # <[IDC]Dragon> Player to be clarified... 16.39.55 # when it sets the data direction 16.40.07 # i'll work on the player 16.40.56 Nick [GoE]BENtheTEN is now known as [OFF]BtT (~quasi@80.238.199.45) 16.43.49 # <[IDC]Dragon> OK, I'll work on the bootloader. 16.43.56 # good 16.44.15 # <[IDC]Dragon> Everybody would have to do a full reflash then to bring it in :-( 16.44.27 # bummer 16.45.11 # <[IDC]Dragon> firmware_flash.rock 16.48.39 # <[IDC]Dragon> I should check in the flash tools to cvs. 16.49.19 # definitely 16.49.24 # <[IDC]Dragon> So far I didn't because the directory struct should be agreed on first. 16.49.46 # i suggest we add a directory called "flash" 16.49.51 # like with the gdb 16.50.02 # <[IDC]Dragon> I have a dir "flashtools" next to apps, firmware etc. 16.50.25 # is the boot loader in there? 16.50.31 # <[IDC]Dragon> shure. 16.50.51 # then i think "flashtools" isn't the best name 16.51.03 # since the boot loader isn't really a tool, is it? 16.51.03 # <[IDC]Dragon> look in the zip file 16.52.33 # <[IDC]Dragon> I have bootloader, extract (grab .ajz out of Archos dump), make_firmware (authoring), minimon (code downloaded for UART boot), RockFlash (the PC counterpart) 16.53.23 # <[IDC]Dragon> we can call it "flash", not to be cofused with MacroMedia 16.55.28 # why only 14400 for the Player monitor? 16.56.00 # <[IDC]Dragon> because the higher one is not matching the clock 16.56.10 # 38400 works for me 16.56.26 Join mad8k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 16.56.46 # <[IDC]Dragon> iirc, it would need a .5 divider 16.57.13 # i use that when i run gdb on my player 16.57.14 Quit k3no_ (Read error: 54 (Connection reset by peer)) 16.58.18 # <[IDC]Dragon> lemme calculate the error... 16.58.46 # #ifdef RECORDER 16.58.46 # BRR1 = 2; /* 115200 */ 16.58.46 # #else 16.58.46 # BRR1 = 9; /* 38400 */ 16.58.46 # #endif 16.59.03 Join k3no_ [0] (ecuh@80.178.33.189.forward.012.net.il) 16.59.20 # <[IDC]Dragon> so the true baudrate for BRR=9 is? 16.59.42 # can't remember 17.02.00 # <[IDC]Dragon> You'd need a BRR of 8.76 17.03.07 # that's a 3.7% deviation 17.03.08 # <[IDC]Dragon> Versus for 14400 baud you need BRR 25.04 17.04.03 # i think you can deviate up to 10% 17.04.18 # <[IDC]Dragon> 5% should be acceptable, but I didn't like it too much. 17.04.39 # as long as you don't send the bytes back to back, you should be allright 17.05.16 # <[IDC]Dragon> jitter must not be more than half a bit at the end of a byte (= 9 bit) 17.05.18 # never mind 17.05.46 # <[IDC]Dragon> The monitor has a command to switch baudrate anyway. 17.05.54 # as long as it works...it is only the monitor 17.05.58 # <[IDC]Dragon> It's just the starter 17.06.21 # <[IDC]Dragon> Well, if I flash with the monitor I want it to be reliable. 17.06.28 # exactly 17.06.43 *** Saving seen data "./dancer.seen" 17.08.06 # <[IDC]Dragon> the really tricky part with UART boot is generating 2300 baud (player) or 2120 baud (recorders) 17.09.06 # ouch 17.09.35 # <[IDC]Dragon> The boot ROM sets BRR to a stupid value which results to these. 17.10.31 # <[IDC]Dragon> Then the first byte of the UART boot protocol will be written into BRR. 17.10.49 # idiots 17.11.36 # <[IDC]Dragon> My challenge was to have the PC generate something that viewed with this stupid rate looks like a byte that gives us a BRR value we can continue with. 17.13.09 # <[IDC]Dragon> So I ended up drawing diagrams how 2 bytes with 4800 baud would be sampled at those baudrates. 17.14.06 # :-) 17.14.38 # <[IDC]Dragon> The unavoidable stop bit messed it up. Was only solveable with some wild interface settings for stop bits and parity. 17.18.02 # hehe, nice work 17.19.04 # <[IDC]Dragon> first I thought this is impossible, I need a microcontroller inbetween. 17.21.33 # <[IDC]Dragon> for the charging: I wonder where Archos switches off the HD. 17.22.56 # me too 17.23.13 Join top_bloke [0] (sgogln@dsc02-chc-il-209-109-231-102.rasserver.net) 17.23.34 # <[IDC]Dragon> They can't be too fast, descramble their way bigger loader first. 17.24.39 # all that needs to be done is to set the data dir of port a 17.25.46 # the data register is probably 0 by default 17.25.55 # <[IDC]Dragon> Yes, but since the boot ROM is not doing it, they can't do it earlier than in the loader. 17.26.16 # true 17.27.42 # <[IDC]Dragon> the descrambler in the boot rom is very inefficient, thus slow to descramble ~9k 17.32.35 # interesting 17.33.09 # <[IDC]Dragon> it reads 5 times from flash to process 1 byte 17.33.28 # however, it seems that my set of test batteries were bad, because it measured over 6V when charging 17.33.48 # <[IDC]Dragon> ? 17.33.57 # i have unpacked a fresh set of batteries to try with 17.34.05 # <[IDC]Dragon> overvoltage, how come? 17.34.09 # i dunno 17.35.47 Join mbr [0] (~mb@stlx01.stz-softwaretechnik.de) 17.37.03 # i gotta go now 17.37.31 # <[IDC]Dragon> shure, was a productive chat! 17.38.20 # cu around 17.38.26 Nick LinusN is now known as LinusN|away (~linus@labb.contactor.se) 18.19.38 Join uski [0] (~moo@gandalf.digital-network.org) 18.20.10 # hi 18.21.32 Join mad9k [0] (~mad8k@h-68-164-44-230.DNVTCO56.dynamic.covad.net) 18.28.10 Quit mad8k (Read error: 60 (Operation timed out)) 18.32.53 Join DJBaz [0] (Barry@modem-2074.lion.dialup.pol.co.uk) 18.35.37 # anyone know of nice custom wps's on the web? 18.37.40 # just make your own 18.37.54 # its easy 18.39.39 # yeh 18.39.50 # but over ppls work would be better than mine 18.39.50 # lol 18.40.47 # ah 18.43.05 Quit k3no_ (Read error: 104 (Connection reset by peer)) 18.43.34 # top_bloke ever used JB_Sync ? 18.43.46 # no 18.44.25 # k 18.44.41 # <[IDC]Dragon> Is there anybody with a flashed FM here? 18.46.11 # this may be silly but does the FM also work with AM? 18.46.53 # i dont think so 18.47.07 # unless you hack it or something 18.47.08 # <[IDC]Dragon> then it woudn't be an FM 18.47.16 # <[IDC]Dragon> no, it can't. 18.47.22 # yeah i'd be am/fm 18.47.22 # kk 18.49.10 # anyone here know of any features the developers r working on for rockbox recorder? 18.53.33 # <[IDC]Dragon> can't speak for the 3 swedes, but I've some things in mind. 18.53.54 # gdgd 18.54.16 # <[IDC]Dragon> flashing the player 18.54.25 # <[IDC]Dragon> merge of talkbox 18.54.26 # im thinking about buying a usb2 card, how long would it take to transfer 70meg on usb2? 18.54.33 # <[IDC]Dragon> audible seek 18.54.55 # cool 18.54.58 # <[IDC]Dragon> recording with the disk off as long as possible 18.55.10 # <[IDC]Dragon> (for short clips via mic) 18.55.13 # what is talkbox? 18.55.42 # <[IDC]Dragon> better charging algorithm 18.55.57 # oh 18.56.07 # <[IDC]Dragon> and the big one: emulating an Alpine CD changer 18.56.10 # i thought it meant rockbox would talk or something lol 18.56.17 # lol 18.56.26 # alpine cd charger? 18.56.37 # changer 18.56.51 # ah 18.56.55 Quit mjh () 18.56.57 # what would that benefit, i dnt understand 18.56.57 # <[IDC]Dragon> talkbox is a batch to play mp3 "thumbnails" as directory names 18.57.33 # people who have alpine head units 18.57.44 # kk 18.57.57 # that would be sweet 18.58.10 # [IDC]Dragon has talkbox been coded as a plugin/ 18.58.11 # ? 18.58.17 # controlling rb through your car stereo 18.58.32 # <[IDC]Dragon> DJBaz: no, it can't 18.58.59 # kk 18.59.09 # dragon do u have a 2meg recorder? 18.59.16 # so it DOES talk 18.59.29 # i tought i was stupid thinking that 18.59.33 # <[IDC]Dragon> DJBaz: no, 8MB 19.00.41 # i only have 2mb :| 19.02.06 Join k3no_ [0] (~hosted@80.178.33.189.forward.012.net.il) 19.02.11 # any features rockbox will have in the 8meg but not in the 2meg? 19.03.15 # <[IDC]Dragon> no, just more buffer for mp3, to playlonger without disk spinup. 19.03.52 # good good 19.03.54 # heh 19.04.03 # someone should start a business upgrading jbs to 8mb 19.04.29 # and throw in an 80GB drive while at it 19.05.18 # heh 19.06.44 *** Saving seen data "./dancer.seen" 19.10.28 # bbl 19.10.30 Quit DJBaz () 19.15.50 Join Dogger [0] (~jimmy@cpc3-colc1-5-0-cust13.colc.cable.ntl.com) 19.20.14 Quit edx (Read error: 110 (Connection timed out)) 19.30.30 Part LinusN|away 19.33.41 Quit dsg (Read error: 110 (Connection timed out)) 19.37.51 Join dsg [0] (~david@pasky.xs4all.nl) 19.53.13 Join dsg_ [0] (~david@pasky.xs4all.nl) 19.55.42 Quit dsg (Read error: 104 (Connection reset by peer)) 19.56.25 Quit Dogger ("Client Exiting") 20.06.13 Quit uski ("Fermeture du client") 20.06.17 Quit top_bloke (Read error: 104 (Connection reset by peer)) 20.17.06 Join edx [0] (edx@pD9EAA788.dip.t-dialin.net) 20.18.23 Join midknight2k3 [0] (LeLaLeLA@AC887C7E.ipt.aol.com) 20.21.31 Nick midknight2k3 is now known as me (LeLaLeLA@AC887C7E.ipt.aol.com) 20.21.43 Nick me is now known as midknight2k3 (LeLaLeLA@AC887C7E.ipt.aol.com) 20.21.51 # sucks 20.22.01 # hello [IDC]Dragon 20.27.14 # dragon: i have a flashed FM 20.41.34 Join AciD`` [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net) 20.42.49 # hi acid 20.46.00 # hi 20.55.17 # dragon, are you around 21.02.03 Join top_bloke [0] (~Email@dsc01-chc-il-209-109-240-44.rasserver.net) 21.02.37 # hi top 21.02.46 # hi 21.03.07 # whats UP 21.03.27 # nothing 21.06.47 *** Saving seen data "./dancer.seen" 21.06.58 Join dsg [0] (~david@pasky.xs4all.nl) 21.06.59 Quit dsg_ (Read error: 104 (Connection reset by peer)) 21.18.50 Join Dogger [0] (~jimmy@cpc3-colc1-5-0-cust13.colc.cable.ntl.com) 21.18.58 # hey 21.19.00 # hey dogger 21.19.26 # have a good idea now 21.19.32 # I make a worm game say for the av3xx 21.19.35 # I dont release it 21.19.43 # okay 21.19.44 # I just do a video of me playing worm on my av3xx 21.19.45 Quit top_bloke ("wasted 0 seconds online") 21.19.48 # then post it everywhere 21.20.01 # hehe 21.20.04 # with a link saying 'if you want this on your archos, tell them to stop being silly' 21.20.12 # or similar 21.20.15 # ohhhhhhh 21.20.16 Join top_bloke [0] (~Email@dsc01-chc-il-209-109-240-44.rasserver.net) 21.20.17 # i get it! 21.20.20 # haha 21.20.20 # then I am certainly not breaking the law, 21.20.27 # and they will get tons of livid customers 21.20.33 # and they will realize that you are doing good things! 21.20.42 # and they will say ok, go ahead 21.20.51 # then they get more customers! 21.20.54 # its good idea! 21.20.54 # perhaps :) 21.20.57 # good good! 21.21.03 # I finished my packer anyway 21.21.08 # cool 21.21.11 # so I can run code on the avxxx now 21.21.21 # can you put up the current code? 21.21.23 # av mm20, av1xx av3xx 21.21.31 # nope 21.21.40 # archos would start legal precedings 21.21.49 # but wait! 21.28.45 Quit k3no_ (Read error: 60 (Operation timed out)) 21.30.45 Quit [OFF]BtT (Read error: 110 (Connection timed out)) 21.32.24 Join [OFF]BtT [0] (~quasi@80.238.199.45) 21.32.30 Join dsg_ [0] (~david@pasky.xs4all.nl) 21.32.40 Join k3no_ [0] (~hosted@80.178.36.47.forward.012.net.il) 21.44.25 # <[IDC]Dragon> midknight2k3: I'm back! 21.44.45 # <[IDC]Dragon> Dogger: sorry for your grounded research. 21.45.05 # yeah its a pain 21.45.06 # [IDC]Dragon: cool 21.45.11 # I'm still working though 21.45.13 # did you need a flashed fmr? 21.45.15 # it's just a hitch 21.45.25 # lol 21.45.35 # ill send em a piece of my mind 21.45.38 Quit dsg (Read error: 110 (Connection timed out)) 21.45.39 # <[IDC]Dragon> midknight2k3: not need, i'd just like to ask something. 21.45.46 # sure.. 21.45.51 # i got one right here 21.46.02 # <[IDC]Dragon> Do you charge with Rockbox' charging screen? 21.46.09 # yeah 21.46.13 # usually 21.46.19 # although i dont like that it keeps the disk going 21.46.21 # <[IDC]Dragon> Is the disk spinning while you do? 21.46.25 # yup 21.46.28 # constantly 21.46.28 # <[IDC]Dragon> Ah. 21.46.38 # <[IDC]Dragon> That was my question. 21.46.54 # sometimes i use f1+on, so i don't make the disk wear down 21.46.57 # is there a way around it? 21.47.05 # <[IDC]Dragon> Powering down the disk works only for recorders. 21.47.14 # <[IDC]Dragon> I have to find a way. 21.47.38 # why can't we do it in fmr's? 21.47.44 # i liked that option when i had a recorder 21.48.07 # <[IDC]Dragon> is does not give hardware control over the disk power. 21.48.14 # <[IDC]Dragon> it 21.48.25 # the recorders did? 21.48.47 # <[IDC]Dragon> Yes, they have a transistor for that, controlled by a port. 21.48.52 # oh 21.49.09 # you should make animated menus 21.49.32 # <[IDC]Dragon> Today Linus had a problem charging his recorder with flat batteries, read the log if you like. 21.49.42 # i did 21.49.56 # <[IDC]Dragon> I fixed it now, but the same will apply to FMs. 21.50.52 # <[IDC]Dragon> Dogger: Do you have an address from Archos where we could write to? 21.51.11 # I just emailed tech support 21.51.21 # then it got forwarded to the ownder/ceo/founder 21.51.26 # <[IDC]Dragon> Hacking the box gives customers, they seem to be unaware of that. 21.51.33 # yeah 21.51.40 # makes me wanna take mine back to the shop 21.52.00 # <[IDC]Dragon> Currently I'm not buying one becaude there's nothing to "do" with it. 21.52.19 # yeah there is, 21.52.21 # for me ;) 21.52.26 # I can run code on mine 21.52.30 # :P so ner 21.53.00 # animated mennuuus! 21.54.34 Quit dsg_ (Read error: 60 (Operation timed out)) 21.58.02 Quit AciD`` (Connection timed out) 21.58.48 Join dsg [0] (~david@pasky.xs4all.nl) 22.05.32 Join midk2k3 [0] (LeLaLeLA@AC823824.ipt.aol.com) 22.07.21 Quit midknight2k3 (Read error: 104 (Connection reset by peer)) 22.07.49 Nick midk2k3 is now known as midknight2k3 (LeLaLeLA@AC823824.ipt.aol.com) 22.16.39 Quit dsg ("foo") 22.21.28 # hey mk 22.21.37 # hey 22.21.49 # whats goin on? 22.21.57 # not much 22.21.59 # you? 22.22.04 # same 22.22.23 # * midknight2k3 needs to work on homework and a review of the chiba 256 22.22.33 # chiba? 22.22.39 # rio chiba 22.22.44 # ? 22.22.50 # rioaudio.com 22.23.23 # ahh 22.23.32 # did you buy one? 22.23.44 # i got a chiba 256 yeah 22.24.16 # its a bird, a plane... 22.24.22 # revolverlution... 22.25.02 # damn, theyre $200 22.25.13 # i want that karma 22.25.22 # yeah 22.25.26 # i'd love a karma 40 22.25.36 # they gave up on the 40gig model 22.25.44 # really?? 22.25.45 # fuck 22.25.49 # i know 22.25.57 # i guess the 20 didn't sell well or something 22.26.00 # i have more than 20gb now 22.26.06 # Karma 20 comes in black on light gray 22.26.12 # it used to say, Karma 20 comes in black on light gray 22.26.20 # Karma 40 comes in black on dark gray 22.26.26 # they omitted that part already 22.26.43 # they might have a 60gb in the works or 80gb maybe 22.26.45 # not sure 22.26.49 # some new model i think 22.26.59 # their site has false advertisment! 22.27.06 # since when 22.27.19 # *1 GB equals 1,000,000,000 bytes 22.27.24 # yes 22.27.25 # that's right 22.27.40 # no, its 2^30 bytes 22.28.12 # whatever 22.28.19 # my HD says its 120GB 22.28.30 # it has 120,000,000,000 bytes 22.28.35 # its 11.3GB 22.28.36 # so is 1,000,000,000 bytes more or less than what it really is? 22.28.45 # 113gb you mean 22.28.48 # *111 22.28.49 # teag 22.28.50 # lol 22.28.55 # *yeah 22.29.00 # lol 22.29.16 Quit dwihno (Read error: 110 (Connection timed out)) 22.29.18 # raptivism 22.29.19 # thats good 22.29.34 # The tight, original design houses... 22.29.36 # tight? 22.29.54 # lol 22.29.56 # its more obvious on a larger scale, but still, thats 9GB i could be using 22.30.03 # be back in a few 22.30.07 # i got a 120gb too 22.30.12 # bbiaf 22.30.25 # i wish theyd actually label them properly 22.30.30 Quit midknight2k3 (Read error: 54 (Connection reset by peer)) 22.34.15 Join AciD` [0] (~acid@longchamp44-1-82-67-133-87.fbx.proxad.net) 22.44.43 Quit [IDC]Dragon () 22.49.37 Join Guest [0] (~jirc@ndn-64-191.telkomadsl.co.za) 22.49.47 # hi 22.49.50 # bye 22.49.51 Quit Guest (Client Quit) 22.51.22 # fantastic news 22.51.24 # eurika 22.53.15 Quit scott666 (Read error: 60 (Operation timed out)) 22.53.40 Join scott666 [0] (scott666@c-24-245-58-245.mn.client2.attbi.com) 23.04.58 Quit cjnr11 () 23.06.51 *** Saving seen data "./dancer.seen" 23.09.31 Quit Dogger ("Client Exiting") 23.20.11 # !list 23.21.00 # any torrents for nba live 2004? 23.25.59 Quit AciD` (Connection timed out) 23.33.08 # eek wrong chan 23.35.03 Join cyberia [0] (none@host65.FASTdial.net) 23.39.02 Quit cyberia (Client Quit) 23.41.04 Join LinusN [200] (~linus@labb.contactor.se) 23.43.17 Quit edx ()