Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

#rockbox log for 2002-12-17

00:06:39 Join dudadical [0] (~thecopes@rdu163-120-098.nc.rr.com)
00:06:52dudadicalhey
00:07:05dudadicaldoes anyone know when Rockbox 2.0 will come out?
00:07:54dudadicalhey, is anyone here?
00:08:26 Quit laotan (Read error: 60 (Operation timed out))
00:08:27 Join laotan [0] (~jesse@markham.openflows.org)
00:08:35miahwhen its ready?
00:09:12dudadicalyes
00:09:16dudadicalwhen?
00:10:39 Quit NiarkY ("leaving by all :)")
00:11:08MrSnazzGreetings, brothers! I have come from... The future!
00:11:17dudadicalhey, Is anyone frikkin here?
00:11:27MrSnazzIt is known to myself, and other time travellers, that rockbox v2.0 will be released on...
00:11:37dudadicalwhen?
00:11:49MrSnazzI was going to tell you, but since you said "frikkin", I won't.
00:12:01dudadicaldude........come on!
00:12:13MrSnazzask nicely
00:12:27dudadicalplease
00:13:10MrSnazzIt'll be released on february 31st of 2003
00:13:17MrSnazzif everything goes according to plan
00:13:38dudadicalyou are probably bull shitting me
00:13:41MrSnazznope
00:13:45MrSnazzI'm totally serious
00:13:47BoD[]hey
00:13:50dudadicalare you a developer?
00:13:53MrSnazzyes
00:14:07BoD[]you should never tell an information from the future
00:14:16MrSnazzBoD[]: I know the risks, but I had to take the chance
00:14:24dudadicalcuz, I bet you just give answers, that are fake.
00:14:29***Saving seen data "./dancer.seen"
00:14:38MrSnazzthat's nice, its the best answer I have.
00:14:41BoD[]now that they know the date, the developpers won't do anything
00:15:02BoD[]since they know it'll be released anyway on this date
00:15:06MrSnazzoh no!
00:15:45dudadicalhey, have any of you ever put on the Chip8 games patch?
00:15:50BoD[]you might have created a time paradoc
00:15:52BoD[]x
00:16:22MrSnazzBoD[]: muhahaha! I'm secretly an iPod developer!
00:16:27dudadicalwell, gotta go, you bull shitter
00:16:30 Quit dudadical ()
00:16:31MrSnazzbye dud
00:16:42MrSnazzI'm amazed that he didn't pick up on the fact that there *is* no February 31st
00:16:55BoD[]:)))))
00:31:54 Join wallie [0] (~wallie@h-69-3-129-54.LSANCA54.covad.net)
00:33:00walliedoes anyone know if rechargeable lithon battery works in Jukebox Recorder?
00:33:12MrSnazznot supposed to use those..
00:33:44walliei know that it voids warranty...but has anyone tried it out?
00:33:58MrSnazzthere are electrical reasons not to do it...
00:34:03MrSnazzI don't know if anybody has tried though
00:34:07wallieah I c
00:34:12MrSnazzyou might be the first :)
00:34:15walliehehe
00:35:03 Join probonic [0] (~probonic@host217-39-18-2.in-addr.btopenworld.com)
00:39:48BoD[]what about combustion batteries
00:40:18 Join LinusN [0] (~linus@labb.contactor.se)
00:40:24MrSnazzre LinusN
00:41:19LinusNyo
00:42:12wallieit's a shame that lithon battery can't be used
00:42:36MrSnazzit has to do with the ferocious nature of lion batteries
00:42:40LinusNwallie: why that?
00:42:51 Quit probonic ("Client Exiting")
00:43:34walliethe mileage of my batteries took a dive after just a week of usage
00:43:48walliei suppose it's the memory issue
00:43:53Jet8810hardeep you there?
00:44:18LinusNwallie: memory issue? on NiMh? I doubt it
00:44:40wallieyou have suggestion then Linus?
00:45:01LinusNwallie: what did you do? what archos model do you have?
00:45:01walliejukebox recorder 20
00:45:18LinusNdid you charge them fully before you used them the first time?
00:45:23wallieyes
00:45:24walliebut
00:45:29wallieon the 3rd use
00:45:55wallieI did plugged in the ac adapter after about 1/2 of the power left in battery
00:46:08wallieso that I can use it to record a 4-hour recording
00:46:32LinusNthat shouldn't make any difference
00:47:07walliemaybe the batteries are just bad?
00:47:16LinusNi guess so
00:47:21LinusNdid you use the standard charger?
00:47:54wallieyep
00:48:50LinusNthen i guess you got a bad battery cell
00:49:13hardeepJet8110: yes, I am here (sorta)
00:49:23wallieyeah...time to hit Radio Shack..hehe
00:49:40LinusNwallie: yeah, too bad
00:49:52walliethx Linus
00:49:53LinusNwas the recorder brand new?
00:50:06wallieabout a month old
00:50:47LinusNyou should complain
00:50:49BoD[]I *gave* one of my two spare batteries to a guy for he can *sell* his old player for he can *buy* a multimedia
00:50:53BoD[]i'm too kind :)
00:51:03LinusNBoD[]: you're a saint
00:51:24BoD[]h ahahaha :))
00:51:52 Quit JimmyDurante3 (Read error: 54 (Connection reset by peer))
00:52:15 Part wallie
00:52:24BoD[]I have to go to bed now
00:52:28LinusNnite
00:52:29BoD[]bye !!
00:52:37 Join wallie [0] (~wallie@h-69-3-129-54.LSANCA54.covad.net)
00:52:51 Quit BoD[] ("cheufeule")
01:00
01:00:28 Quit hardeep ("[BX] Reserve your copy of BitchX-1.0c19 for the Atari 2600 today!")
01:08:18 Part LinusN
01:19:11 Join hardeep [0] (hardeeps@208.247.65.237)
01:27:25 Join edx [0] (~edx@pD9EABE1B.dip.t-dialin.net)
01:27:27 Quit edx (Remote closed the connection)
01:29:08 Part wallie
02:00
02:00:01 Join edx [0] (~edx@pD9EABE1B.dip.t-dialin.net)
02:00:05 Quit edx (Remote closed the connection)
02:12:06 Join elinenbe [0] (]I[-97881@user-0cev121.cable.mindspring.com)
02:12:12elinenbehardeep: you here?
02:14:32***Saving seen data "./dancer.seen"
02:23:02hardeepelinenbe: every now and then heh
02:24:17elinenbehardeep: how is the queuing coming?
02:26:39hardeepelinenbe: implementation is complete. There is a bug either in the file writing code or the way I use it that needs to be fixed before it's submitted
02:27:11elinenbeoh... okay.
02:27:20elinenbedo you have a build based on the latest CVS?
02:27:34hardeepyou're welcome to try it if you want: hardeeps.freeshell.org/ajbrec.ajz
02:27:52hardeepdiff at: http://hardeeps.freeshell.org/queue_function_7.diff
02:28:05elinenbedoes that compile include the trickle charge changes?
02:28:17hardeepit's almost latest cvs, i think uwe made a few changes today that aren't in
02:28:30hardeepyeah, trickle charge stuff is in, I updated last night
02:28:50elinenbenice :)
02:28:59elinenbeyeah, I saw those.
02:29:19elinenbedoes the resume work at this point?
02:29:34hardeepyeah
02:29:42hardeepwell, as much as i've test i should say. :)
02:29:47elinenbeyou should wrtie up a document to explain the exact method of the queuing −− like if you go back to a previous song, or move to the next...
02:30:08hardeepheh, i'm not much of a documenter but you're right, i should
02:30:26elinenbeI think it would clear up a lot of confusion.
02:30:38elinenbeuwe's charging documentation is great!
02:31:01hardeepright now, previous will take you to the song before you began queuing
02:31:12hardeepnext will delete the queued song from the list
02:31:37hardeeponce a queued song is removed (normally once it has been played) it's no longer "remembered"
02:31:44elinenbeand move on to the next queued song −− right?
02:31:50hardeepyeah, if there is one
02:32:01elinenbeif you shut it off, does it remember the current playlist with the queue list?
02:32:17hardeepyes, and it stores the correct index into the current playlist
02:32:25elinenbethat is nice.
02:35:08hardeepas soon as we track down this last bug I'm going to submit the code to the list for review
02:36:26elinenbesounds great.
02:36:44elinenbeI noticed that the last line of the .queue_file in many cases is wrong.
02:36:59hardeepyeah, that's the bug
02:37:16hardeepthe data is being corrupted as it's written to disk
02:37:20elinenbeoh...
02:37:27hardeepbut only at sector boundaries
02:38:19elinenbehmmm....
02:38:24elinenbehmmmmmm........
02:38:42hardeep?
02:39:04elinenbeI am thinking.
02:39:08elinenbe;)
02:39:12hardeeplaugh
04:00
04:03:36 Quit ken0_ (Read error: 54 (Connection reset by peer))
04:14:35***Saving seen data "./dancer.seen"
04:15:06 Join JimmyDurante3 [0] (~durant3@dhcp03242.resnet.unc.edu)
04:40:08 Quit hardeep ("BitchX: not from concentrate")
04:40:08 Quit JimmyDurante3 (Read error: 54 (Connection reset by peer))
05:00
05:02:41 Join [keno] [0] (marklar2@80.178.33.34)
05:29:19 Join hardeep [0] (hardeeps@208.247.65.237)
05:37:29hardeepwoo, found the bug
05:38:30elinenbeWOO!
05:38:36elinenbecommit the code... commit the code :)
05:38:52hardeepheh, there won't be commits any time soon... need to be reviewed first
05:39:10hardeepplus I need to confirm with Zagor the file fix
05:45:34elinenbepost the infos to the list...
05:46:11hardeepyeah, i will shortly
05:46:42hardeepbut, dinner first. :)
05:46:51 Nick hardeep is now known as hardeep|away (hardeeps@208.247.65.237)
06:00
06:05:02 Join Josh_ [0] (~Josh@adsl-153-120-221.mia.bellsouth.net)
06:05:45 Join ken0 [0] (marklar2@80.178.33.34)
06:08:10 Quit [keno] (calvino.freenode.net irc.freenode.net)
06:08:10NSplitcalvino.freenode.net irc.freenode.net
06:08:10 Quit Jet8810 (calvino.freenode.net irc.freenode.net)
06:08:10 Quit Bryant (calvino.freenode.net irc.freenode.net)
06:08:56NHealcalvino.freenode.net irc.freenode.net
06:08:56NJoin[keno] [0] (marklar2@80.178.33.34)
06:08:56NJoinJet8810 [0] (~Josh@adsl-153-120-221.mia.bellsouth.net)
06:08:56NJoinBryant [0] (twogluon@it-vlan-2-77.flexabit.net)
06:09:22 Quit Jet8810 (Read error: 104 (Connection reset by peer))
06:09:47 Quit [keno] (Read error: 104 (Connection reset by peer))
06:14:37***Saving seen data "./dancer.seen"
06:27:36 Nick seb-away is now known as seb-sleep (Sean@bgp420584bgs.union01.nj.comcast.net)
07:00
07:41:16 Nick dw|gone is now known as dwihno (dwihno@Bald067.Baldakinen.Umea.SE)
08:00
08:03:42 Quit elinenbe (Read error: 110 (Connection timed out))
08:14:38***Saving seen data "./dancer.seen"
09:00
09:03:16 Join Zagor_ [242] (~bjst@labb.contactor.se)
09:16:42 Nick hardeep|away is now known as hardeep (hardeeps@208.247.65.237)
09:16:45hardeepheya zagor
09:16:56Zagor_hi
09:16:59 Nick Zagor_ is now known as Zagor (~bjst@labb.contactor.se)
09:17:18hardeepi found the bug i told you about last night
09:17:26Zagoryay!
09:17:46hardeepit's in the file writing code: file.c:~360
09:18:08hardeepthe headbytes write is writing into the wrong sector (not seeking back to the previous sector like flush_cache() does)
09:18:20Zagorah!
09:18:29hardeepI have a potential fix at: http://hardeeps.freeshell.org/file_write_fix.diff
09:18:37hardeepnot sure if it's completely valid though, works for me heh
09:18:47hardeep(not all that familiar with the file writing code)
09:18:57Zagori'll look
09:19:57Zagorlooks a bit strange. if file->dirty is always true, we will try to flush the cache on close()
09:20:14hardeepit's done right after that if
09:20:48Zagoryes, but now you always set dirty to true, even if the sector cache is empty
09:21:41hardeephmmmm, flush_cache() sets it to false
09:22:04hardeepi was just avoiding duplicating code... we could make it explicit inside the headbytes if
09:22:23Zagoryes. but if the code at ~362 is executed, we should not call flush_cache, since the cache is empty.
09:22:50Zagoror am I missing something?
09:22:59hardeepoh, laf, i'm dumb, never mind
09:23:02hardeepi was doing a write twice
09:23:08Zagoryes
09:23:08hardeepit worked! but that's silly
09:23:11Zagorhehe
09:23:41Zagorthe write at 361 should seek first, I guess
09:24:04Zagori'm not sure why that happens though
09:24:07hardeepactually, maybe we could just remove the write and call flush?
09:24:16Zagorwe shouldn't have passed the correct sector before this
09:24:24hardeepi do a seek just before the write, maybe that's changing something?
09:24:46Zagoryes, that could be it
09:25:00Zagorflush_cache seems the right thing to do
09:25:32Zagorexcept seeking is expensive in big files. i was hoping not to have to do it all the time.
09:26:33 Join matsl [0] (~matsl@dhcp91.contactor.se)
09:27:24hardeephmmm, in most cases won't the seek do nothing?
09:27:45hardeepif you're writing sequentially without closing
09:29:10hardeepoh, i guess not, it looks like seek always starts at the beginning of the file
09:29:29hardeephmmm, could we optimize that a bit (fat_seek that is) ?
09:30:22hardeepif (file->lastcluster == cluster) or somesuch
09:30:42Zagoryes
09:36:56Zagor'about 3/64" thick' - how can americans build anything with measurements like that? :-)
09:40:31hardeepstubborness can get you a long way. :)
10:00
10:14:41***No seen item changed, no save performed.
10:17:11hardeepzagor: alright, i think i've done as much as I can for queueing... how did you want me to send the changes:
10:17:25hardeepa) sf patches b) mailing list c) html link d) all of the above
10:17:45Zagorsf patch is good
10:17:50hardeep'kay
10:19:11*dwihno gets Zagor some choklad
10:56:54hardeepif anyone's bored and wants to try out the patch i just submitted binaries are at: http://hardeeps.freeshell.org/archos.mod and http://hardeeps.freeshell.org/ajbrec.ajz
11:00
11:09:39hardeepsleep time
11:09:41 Quit hardeep ("[BX] Reserve your copy of BitchX-1.0c19 for the Nintendo 64 today!")
11:56:10 Join TotMacher [0] (tot@p5084B647.dip.t-dialin.net)
12:00
12:14:45***Saving seen data "./dancer.seen"
12:47:15 Join kSADerfos [0] (e-potis@vdp026.ath08.cas.hol.gr)
12:47:24 Part kSADerfos
12:49:15 Quit TotMacher ()
13:00
13:03:16 Join LinusN [0] (~linus@labb.contactor.se)
13:09:34 Join elinenbe [0] (]I[-2787@user-0cev121.cable.mindspring.com)
13:10:03elinenbemorning
13:15:00 Part LinusN
13:17:51 Join LinusN [0] (~linus@labb.contactor.se)
13:44:14 Quit matsl ("Client Exiting")
13:58:05 Part LinusN
13:58:08 Join LinusN [0] (~linus@labb.contactor.se)
13:58:22 Part LinusN
14:00
14:00:21 Nick seb-sleep is now known as seb-school (Sean@bgp420584bgs.union01.nj.comcast.net)
14:14:46***Saving seen data "./dancer.seen"
14:37:41 Quit Josh_ (Read error: 54 (Connection reset by peer))
14:59:24 Join Geudin [0] (~ablancha@212.234.51.85)
14:59:28Geudinhi !
14:59:33 Nick Geudin is now known as Disciple1 (~ablancha@212.234.51.85)
14:59:38dwihnoHej
15:00
15:48:53 Quit Disciple1 ("Go Go Go !!!")
16:00
16:14:47***Saving seen data "./dancer.seen"
16:58:47 Join edx [0] (~edx@pD9EAB1E1.dip.t-dialin.net)
16:59:11 Nick dwihno is now known as dw|gone (dwihno@Bald067.Baldakinen.Umea.SE)
17:00
17:13:26 Join TotMacher [0] (tot@p508DAE66.dip.t-dialin.net)
17:22:15 Join hardeep [0] (hardeeps@sdf.lonestar.org)
17:24:24 Part Zagor
17:46:51 Quit Bryant (calvino.freenode.net irc.freenode.net)
17:46:51NSplitcalvino.freenode.net irc.freenode.net
17:52:43NHealcalvino.freenode.net irc.freenode.net
17:52:43NJoinBryant [0] (twogluon@it-vlan-2-77.flexabit.net)
18:00
18:14:50***Saving seen data "./dancer.seen"
18:25:29 Quit hardeep ("Leaving")
18:28:04 Join SillyFly [0] (~luk@80.179.66.137)
18:28:33 Quit SillyFly (Client Quit)
19:00
19:07:46 Join ken0_ [0] (marklar2@80.178.33.34)
19:08:31 Quit ken0 (Read error: 54 (Connection reset by peer))
19:35:09 Join Triple-z [0] (~Mp3@212.116.168.47.knet.co.il)
19:39:36Triple-zhello
19:40:13 Quit elinenbe ()
19:42:33Triple-zbidiscroll was addad?
19:55:35ken0_DAMNIT
19:55:47ken0_who's up?
19:55:52ken0_linus/zagor ?
19:55:58 Nick ken0_ is now known as [keno] (marklar2@80.178.33.34)
20:00
20:01:06adi|workwhats the problem?
20:14:53***Saving seen data "./dancer.seen"
20:24:50 Join quelsaruk [0] (~zaknafein@faerun.ugr.es)
20:25:01quelsarukhi
21:00
21:31:56 Quit quelsaruk ("KVIrc 3.0.0-beta1 "Eve's Avatar"")
21:55:31 Quit edx ()
22:00
22:14:57***Saving seen data "./dancer.seen"
22:36:15 Join ken0 [0] (marklar2@80.178.32.73)
22:40:31 Quit [keno] (Read error: 104 (Connection reset by peer))
23:00
23:06:31 Join BoD[] [0] (~BoD@m131.net81-67-41.noos.fr)
23:06:55BoD[]Hello, world!
23:20:12 Join hardeep [0] (hardeeps@208.247.65.237)
23:26:41Triple-zwhos alive?
23:28:11 Join Jet8810 [0] (~Josh@adsl-153-120-221.mia.bellsouth.net)
23:31:27adi|workwhats up?
23:32:01Triple-zas usual
23:32:03Triple-z:P
23:32:06Triple-zyou?
23:32:51Triple-zgot a new AMD athalon XP 2000+, man USB 2.0 RoXX
23:35:18adi|work:)
23:35:19adi|workworking
23:40:28Triple-zMerged Uwe Freese's bidirectional scrolling patch. Added configurable scroll step size and scroll start delay
23:40:36Triple-zon 16/12
23:40:46Triple-zhow can i use it you know?
23:47:30adi|workhow can you use what?
23:47:34adi|worki don't get your questions
23:47:38adi|workquestion rather
23:48:23Triple-zthe bidirectional scrolling patch
23:48:29adi|workyeah.. i get that...
23:48:35adi|work"how can i use it you know"
23:48:39adi|workthats the part i don't get?
23:48:53Triple-zits the the wps
23:49:05Triple-zwhats the %thing of it
23:49:17Triple-zin the wps i mean
23:55:18 Join DisciTV [0] (admin@ASte-Genev-Bois-104-1-3-160.abo.wanadoo.fr)
23:55:22DisciTVHi !
23:55:26 Nick DisciTV is now known as Disciple1 (admin@ASte-Genev-Bois-104-1-3-160.abo.wanadoo.fr)

Previous day | Next day