irclog2html for #elinux on 20060523

00:42.01*** join/#elinux TxRomeo (n=bob@65.170.133.242)
01:15.22MonMothaibot seen sorphin
01:15.34ibotsorphin <n=dans@mewp.captainrock.com> was last seen on IRC in channel #edev, 17d 23h 21m 20s ago, saying: 'because unless i get called, i've been off the clock since 5:30pm :)'.
01:16.22*** join/#elinux noclouds (n=mhfan@60.166.51.79)
01:29.22*** join/#elinux Tmob (n=total@c-24-6-95-52.hsd1.ca.comcast.net)
02:22.02*** join/#elinux Tmob (n=total@c-24-6-95-52.hsd1.ca.comcast.net)
03:11.55MonMothaibot seen sjhill
03:12.06ibotsjhill <n=sjhill@eth13.com-link.com> was last seen on IRC in channel #uclibc, 4d 9h 6m 16s ago, saying: 'that's my speculation'.
03:31.42ricmmMonMotha: I would recommend #mipslinux to contact sjhill, he seems to be there more often than anywhere else
03:31.45ricmmhe isnt there atm tho ;)
03:38.43MonMotharicmm: not surprising
03:38.54MonMothaI was looking for him for that purpose actually...had some MIPS questions
03:39.03ricmmyou can go in there
03:39.04MonMothayou know much about the NEC VR5432?
03:39.09MonMothatrue, I could :)
03:39.10ricmmplenty of MIPS gurus
03:39.51ricmmMonMotha: my field of experimentation doesnt go past VR4xxx series
03:39.53ricmm;)
03:40.42MonMotharicmm: ok, well, this is pretty basic stuff on those procs
03:41.07MonMothaI have a bunch of references to 0xBFAxxxxx.  It looks like some sort of memory mapped thingie given what's being written in there, but it could conceivably just be SRAM
03:44.26ricmmnever heard of specific mapping in those addresses, but let me recheck docs in case I missed something
03:44.32MonMothaok
03:44.37MonMothaI looked throught the stuff and didn't see anything
03:44.46MonMothait looks like init values for an MMU, but that's on coproc 0
03:47.54ricmmno, I can't recall any references to 0xBFAxxxxx on vr41xx line of processors
03:48.02ricmmperhaps its something specific on vr5xxx ?
03:48.14MonMothaI didn't see any references in the VR5xxx docs, either
03:48.23MonMothait could just be SRAM, but it really looks like register init
03:48.39ricmmwhat makes you think that
03:48.45ricmmwhere are you seeing those references?
03:49.27MonMothaDCT5000 boot ROM
03:49.39MonMothathere's this procedure that inits a bunch of processor bits, and it has a bunch of these refernces
03:49.59MonMothathen at the end goes and writes zero to a bunch of cp0 regs
03:51.02ricmmlogic would say register init
03:51.11ricmmbut perhaps its mapping something into ram?
03:51.46MonMothathat's what I'm wondering is if there's something memory mapped there
03:51.51MonMothaROM shows up at 0xBFC00000
03:52.00MonMothathat's where the cold boot exception handling vector is
03:52.38MonMothathere values it's poking are somewhat "magic".  Lots of large nice hex numbers
03:53.01MonMothathings like 0x80000000, 0xEE000000, et.
03:53.32*** part/#elinux TxRomeo (n=bob@65.170.133.242)
03:53.33ricmmthats weird, any chance on dumping those memory addresses after booting the thing?
03:55.02MonMothacan I do that via JTAG?
03:55.51ricmmyou got it identified in that thing?
03:56.17MonMothayeah, it's on a header
03:56.22MonMothaI don't have a connector handy, but i can get it
04:07.29ricmmMonMotha: sorry kind of busy atm, can ram be dumped from jtag on runtime?
04:07.48MonMothaI don't knwow
04:16.23MonMothathey could just be global variables, but they look like maybe initing an MMU or something
04:25.32MonMotharicmm: the VR5xxx is backwards compatible enough to the VR4xxx that I should be able to get Linux running on it as such, right?  That would seem to be the indication fromw aht I've read
04:55.58ricmmMonMotha: sorry, was on the phone with a friend, its her bday today
04:56.20ricmmbut I don't really know specs on the VR5xxx series, I would need to dig some docs for that and it's pretty late tonight
04:56.22MonMothaah, ok
04:56.28MonMothathat's fine
04:56.32ricmmbut as far as I know all the line of VR cpu's share a basically similar structure
04:56.38MonMothawhere are you at, btw?
04:56.41MonMothatimezone wise
04:57.00ricmmthe basic vr41xx code on the mips branch should give some signs of life with minimal memory mapping changes
04:57.09ricmmim on EST+1, if that makes any sense
04:57.18ricmm1am but I got class at like 7am so I should sleep, heh
04:58.50MonMothaah, so same time as here
04:59.10MonMothathere's a group of us on Wed. who are going to get together in a room with a couple projectors and start working through this
04:59.26ricmmah that sounds interesting
04:59.40ricmmare you still at Rose Hullman (or however its spelt)?
05:00.06MonMothayeah, Rose-Hulman
05:00.16MonMothawe'll probably chuck an IRC window up on one projector if we get some others interested
05:00.28MonMothaala hh dev conference (though we only have two screens)
05:00.34ricmmhehe
05:00.56ricmmI remember an old conference, probably the first that used vo-ip broadcasting and questioning
05:02.47ricmma hh conf that was
05:03.19MonMothayeah, I remember that one
05:04.17MonMothayeah, this part is definately compiler generated...
05:04.28MonMothaI could condense like 20 of these instructions that are playing with masks into a single constant
05:07.02T0mWricmm: naw, you cannot dump ram from a running cpu
05:08.30ricmmya thought so, it already sounded like a vicious idea
05:08.31ricmmheh
05:08.44T0mWyeah, a "siphon"
05:09.13T0mWnever hurts to ask though, heh
05:09.17*** join/#elinux Spetznaz (n=spetznaz@tac.mukachevo.net)
05:09.38T0mWibot: weather kabe
05:09.59T0mWsupposed to have frost tonight
05:11.49MonMothaT0mW: can you halt the CPU via the test interface to perform pin twiddle operations, then resume operation?
05:11.55MonMothathat would let you do the same thing :)
05:11.59T0mWyes
05:12.22MonMothayou could halt it, read the RAM manually, then put everything back the way it was and resume operation as if nothing happened
05:12.35T0mWwith the Abatron, I can halt the cpu, examine, alter memory, then tell it to 'go'
05:13.50T0mWDunno what the DRAM controller would be doing while I'm halting cpu though, the CPU as my current target is SRAM
05:15.29MonMothawell, as far as I can tell, this stuff would have to either be SRAM or some sort of memory mapped peripheral
05:15.43MonMothaunless the DRAM controller comes up initilized correctly for the RAM on this target, which I highly doubt
05:15.55MonMothaheck, the MMU isn't even configured yet
05:16.31T0mWIt might start in a "dead duck" mode, where it has a few K and slow timing?
05:16.33MonMothathe values just seem sorta odd to be stuffing in global variables.  They look more like things you might configure an MMU with, actually
05:16.44MonMothawell, there's plenty of SRAM on this board, but that is possible
05:17.01T0mWlots of flash on that board too
05:17.06MonMothaI guess I could go start trying to poke around to trip chick selects with the JTAG
05:17.16MonMothayeah, though they're storing to these locations, so it can't be flash as they aren't flash commands
05:18.04T0mWSPI port maybe?
05:18.27MonMothayou know...it may be the DRAM controller
05:18.32T0mWYou trying to reverse the boot rom?
05:18.39MonMothayeah
05:18.46MonMothaI'm trying to see if there might be a way to not have to replace it
05:19.02MonMothaI can't for the life of me find a place to buy the flash equiv part, and it would be nice for the others if that were not required
05:19.18T0mWdoesn't that unit come up dumb, init the RF modules, then signon to a remote controller to get it's runtime program?
05:19.23MonMothaif I could buy the flash equiv part (and program it in system via JTAG or otherwise), that would be REALLY nice
05:19.26ricmmVR's user manuals are nice
05:19.29MonMothayeah, that's what it appears to want to do
05:19.36MonMotharicmm: yup, I've got them up
05:19.51ricmmthey are rather "complete"
05:19.54MonMothaindeed
05:20.10ricmmwhile you see some controllers that would merit a good 500 pages of docs they only get like 90
05:20.20ricmmthe vr4121 has a 830 pages um x.x
05:20.36T0mWheh
05:20.55MonMothaT0mW: if I could replace that ROM, I could just chuck a kernel right in the ROM and let it try to boot itself, though I'm not entirely sure how the serial port is hooked up (looks like probably through that PC "southbridge" chip that handles the parport and IDE)
05:21.06T0mWsounds like you would need to have a team just to handle the vr4121 stuff
05:21.18ricmmpretty much
05:21.19ricmmits a bible
05:21.39T0mW"In the beginning, there was germanium..."
05:21.58ricmmheh
05:22.10T0mW"and a cats' wisker"
05:22.30ricmmok I should really go to bed
05:22.31ricmmgood night
05:22.52*** join/#elinux angom_h (n=angom@red-corp-201.130.156.80.telnor.net)
05:22.53T0mWMonMotha: I couldn't identify the ROM, I was able to get "close" and read from it.
05:23.12T0mWthe data looked reasonable
05:24.26MonMothaT0mW: I've got an image.  It's on elinux.org
05:24.40T0mWyeah, that's the one I sucked in, I think.
05:24.48MonMothathere's also a flash part suggested that I cannot locate a place to buy it from.  The really old 16Mbit EPROMs would work, but they're 5V only and this runs at 3
05:25.16MonMothaI could make a little board with a bunch of buffers and such, but then I might as well just start stacking smaller flash chips up
05:25.24MonMothaa drop-in replacement would be very nice
05:26.23T0mWwell, if you do use a 5v flash, the address lines should be okay with the 3.3v drive levels.  Depends.
05:26.50T0mWwhere you would need to be carefull is on the data lines, they would have to be clipped to 3.3volts max
05:27.25T0mWI would run some, what, 100ohm, 400ohm resistors in series with the mainboard Databus signals.
05:27.38MonMothaoh, and just run the chip at 5V?  hum, that would work I gues
05:27.47MonMothawoudl remove my ISP ability though since those old parts are UV erase
05:28.03MonMothaand I lack an EPROM programmer unless I'm at school, which I won't be by the end of this week
05:28.14T0mWthen, use 1N4148 diodes at the "far end" (farthest from the 5volt flash) to 'clip' the voltage up to the 3.3v supply.
05:28.47T0mWthen the only power would be that dissappated via the 400 ohm resistors * excess voltage
05:29.32T0mWuse carbon comp resistors
05:29.39T0mWno film
05:30.10T0mWah, film should be ok
05:30.54MonMothaheh, it's not running THAT fast :)
05:31.00T0mWMonMotha: I wasn't that interested in MIPS to do anything with the DCT5000
05:31.10MonMothaT0mW: well, I just want to egt this stuff working at this point
05:31.16MonMothaand all the ARM stuff already has Linux ported to it :)
05:31.22T0mWheh
05:51.18*** join/#elinux FireEgl (i=Atlantic@Atlantica.US)
06:04.55MonMothaMIPS has a reasonably standardized memory layout, right?
06:05.09MonMotha8xxxxxxx is RAM, axxxxxxx is uncached RAM, etc?
06:05.15MonMotha(most of the time, of course)
06:06.29T0mWsjhill is the MIPS lackey
06:07.23MonMothaI know
06:13.40T0mWbut, I'll take their money
06:15.19*** join/#elinux derkling (n=derkling@213-140-6-119.ip.fastwebnet.it)
06:33.32*** join/#elinux ignatoff (n=ignatov@c1-30-13.rrba.isadsl.co.za)
06:59.21MonMothaok, so I was right
06:59.37MonMotha0xBFAxxxxx is the base of the memory mapped registers for the memory controller
06:59.43MonMothaso it's doing DRAM init, chip select setup, etc.
06:59.47MonMothawhcih is what it lookedl ike
07:54.49derklingwhat stand for "relocation truncated to fit: R_ARM_PC24 rpl_malloc"
07:54.50derklingI'm doing a crosscompilation with --build=i686-pc-linux-gnu --host=arm-linux)
07:58.42T0mWmeans you went too far
07:59.16T0mWgenerally means the branch is too far to the target addr
07:59.31T0mWlike trying to jump to RAM from Flash memory
08:01.11T0mWderkling: ping
08:01.12MonMothaholy hell
08:01.26T0mWMonMotha: what's up Batman?
08:01.40MonMothathis thing is nothing more than a NEC DDS5476 dev board with some more stuff thrown on
08:01.46MonMothaand that board is (somewhat) supported by linux
08:01.57MonMothathe flash has been moved, btu that's fixable
08:02.07T0mWhow did you figure that out?
08:02.08MonMothathe southbridge chipset is the same
08:02.15MonMothaamongst other things
08:02.23MonMothaDRAM is in the same place
08:02.47MonMothait doesn't have all the hardware that's ont he dev board, but mostly it's the same as far as I can tell
08:02.53MonMothacomparing VRC5476 init values
08:03.12MonMothaso now I just need to be able to get a program on the darn board and convince it to boot it
08:03.18T0mWNEC DDB5476
08:03.22MonMothayup
08:03.29MonMothathat's what I meant
08:03.31T0mWhuh
08:03.33MonMothaI guess I typed S instead of B
08:03.34T0mWinteresting
08:04.04T0mWI'm trying to get this *()&*ing program done tonite, I WANT TO PLAY TOO! WAHHH!
08:04.06MonMothalooks like the two flash banks are at 0x1C000000 and 0x1F000000 on this board
08:04.19MonMothaeverything else is likely dangling off PCI
08:04.31MonMothaand that should be discoverable once Linux is booting
08:04.43T0mWprolly, don't re-invent the wheel if you can purchase one ready-made
08:04.47MonMothayeah
08:04.58MonMothathe SRAM appears to all be hooked up to various peripherals, looking at the board
08:05.04MonMothaso probably none available to the OS
08:05.20T0mWheh, like the ZipIt, it is a collection of Appnotes
08:05.33MonMothathe webpal is the PS7500 dev kit in a box
08:06.11T0mWyeah, it is, I had the CL_PS7500-FE EVB, paid $1500 for that trash
08:06.35T0mWthat is where it is today, in the local landfill
08:06.38MonMothahehe
08:06.43T0mW:(
08:06.46MonMothamight as well just buy a webpal
08:07.01MonMothaeven has most of the stuff brought out to IOs of some form
08:07.11T0mWwell, I bought it about 2000 (2001?)
08:08.17MonMothaah, ok
08:08.43T0mWcool
08:09.10MonMothaT0mW: you wouldn't happen to know where I could acquire a copy of the VRC5476 manual?
08:09.31T0mWthinking about the DCT5000 distracted me enough to realize my programming error.  All fixed now.
08:09.32MonMothahaving to reverse engineer the behavior of the thing from the linux source (which is not well commented at all) and the disassembly is tough
08:09.36MonMothaah, there you go
08:09.39T0mWno, I don't
08:09.40MonMothasee, I was beneficial :)
08:09.59T0mWibot: give MonMotha a snack
08:10.01ibotACTION gives a snack to MonMotha
08:10.09T0mW:D
08:10.51MonMothaawesome! :)
08:11.05T0mWtime for a break, maybe run down to the local pitstop (gas n go) to get a granola bar or something
08:11.42T0mWI've got a few more functions to code & test, then shovel this code into the target system and test it.
08:12.19T0mWMonMotha: then invoice the customer and I can buy food again
08:13.13MonMothahey, that's always good
08:13.24MonMothaI've actually got a stint at On this summer making eval/demo boards
08:13.26MonMothashould be fun
08:13.38MonMothahey, I've got an init sequence here
08:13.47MonMothathink you could look at it really quick and see ify ou recognize what it might be?
08:14.03MonMothaI think it may be some sort of flash, but I could be completely wrong.  It's mapped straight off the MMU into a 2MB space
08:14.18T0mWpaste it up
08:15.27T0mWMonMotha: Lineo did the original linux port on that board, and you know they weren't terribly smart people, heh
08:15.35MonMothaheh
08:15.44MonMothathis is coming from the disassembly from the DCT5000
08:15.47MonMothalet me get this typed up
08:16.36MonMothahttp://gigapet.monmotha.net/~monmotha/mysteryinit.txt
08:17.02T0mWthats a Flash dance
08:17.13MonMothaok, I figured
08:17.26T0mW28 or 29 series flash
08:17.27MonMotharecognize any specifics, what it might be doing?  Which chip it might be talking to (would be AMD or Intel)?
08:17.37MonMothayeah, that would be what's on this board :)
08:17.46T0mWIntel I think, AMD did similar dances
08:17.47MonMothaAMD 29 series and Intel 28 series
08:18.04MonMothahave you seen the DCT5000?
08:18.06T0mWyeah, looks like intel 28
08:18.09MonMothaok
08:18.13T0mWMonMotha: I've got one here
08:18.18MonMothahandy?
08:18.23MonMothamind taking a brief look at something for me?
08:18.28T0mWok
08:18.37MonMothathere's two "sets" of flash, right?
08:19.00MonMothaone set is two large Intel 28 series chips, while the other set is two smaller chips mixed between 28 series Intel and 29 series AMD
08:19.35MonMothaany thoughts?  their physical proximity and the fact that I have two chip selects being generated leads me to believe they are being mapped separately, but why mix the Intel and AMD?
08:22.30T0mWok, i've got it opened up
08:23.19MonMothasee above?
08:24.09T0mWI have always thought that U7 & U9 are for the main processor
08:24.20T0mWwith U5 & U6 going to the broadcom chip
08:25.22MonMothaah, you're right
08:25.29MonMothamaybe
08:25.38T0mWU6 is 8bit
08:25.52MonMothathere's a goodly number of lines to the U21 going down towards the other stuff, nearer to the proc
08:26.02MonMothato the left of the screw
08:26.20MonMothaU21 is 16bit, just found a datasheet
08:26.57T0mWyou mean u6, not u21
08:27.15T0mWsame thing
08:27.37T0mWare you sure, that is the 44 pin TSOP, isn't it?
08:27.39MonMothaindeed, what is U21 referrign to there?
08:27.45MonMothayeah it looks too small
08:27.55MonMothabut the datasheet for that part with full matching number (C3 suffix) says 16 bit
08:28.02T0mWit is a double purpose footprint: u21 or u6
08:28.10MonMothaah, ok
08:29.03T0mWAhhhhh, I think you are correct.  IIRC, the E28F320's are StrataFlash.
08:29.16MonMothaIntelĀ® Advanced+ Boot Block Flash Memory (C3) according to the datasheet
08:29.30MonMothathe J5 is x8/x16
08:29.32T0mWStrataFlash doesn't do the 'dance', it has a different algorithm
08:29.37MonMothaok
08:29.59T0mWthen you must be dancing the u6 (u21)
08:30.05T0mWor u5
08:30.20T0mWIIRC, the 29F series also danced
08:30.22MonMothaok
08:31.22MonMothaso all those Intel parts would not use that algorithm?
08:31.27T0mWhmmm, SW900 looks interesting, eh?  SPST switch
08:31.34MonMothaSW900 is reset
08:31.48MonMothasame as a power cycle, at least with the stock firmware
08:31.48T0mWI don't think so, it's been a while.
08:32.03MonMotha<PROTECTED>
08:34.27T0mWhttp://download.intel.com/design/flcomp/datashts/30666608.pdf
08:35.51T0mWTo perform a write operation, both CE# and WE# are asserted while RST# and OE# are deasserted.
08:35.51T0mWDuring a write operation, address and data are latched on the rising edge of WE# or CE#,
08:35.51T0mWwhichever occurs first. Table 19, ?Command Bus Cycles? on page 50 shows the bus cycle
08:35.52T0mWsequence for each of the supported device commands, while Table 20, ?Command Codes and
08:35.52T0mWDefinitions? on page 51 describes each command. See Section 7.0, ?AC Characteristics? on
08:35.52T0mWpage 33 for signal-timing details.
08:36.28*** part/#elinux derkling (n=derkling@213-140-6-119.ip.fastwebnet.it)
08:36.38T0mWit uses hardware bitline sequencing + command mailbox to program strataFlash, no dance
08:37.44MonMothaok
08:41.24T0mWWell, there is a way via JTAG to program the Flash.  We used the Boundry Scan Chain to program the TuxScreen that way.
08:41.46T0mWproblem has been that boot rom
08:42.14T0mWas in, wtf is it and can we get any of them?
08:42.15T0mWheh
08:42.19MonMothayeah, I'm familiar with that procedure
08:42.24MonMothaexactly
08:42.34MonMothathere's got to be a way to convince that ROM to run what's in flash
08:42.36MonMothaI'm trying to find it
08:42.45MonMothaI have some ideas right now
08:43.27MonMothait checks for a magic value in flash.  If it doesn't find it, it sets that magic value, and copies some program (which appears to just bang at the DRAM controller indefinately) and jumps into it
08:44.10MonMothaif it does find it, it writes back a DIFFERENT value, goes on to init the processor some more, and I haven't gotten any further
08:44.41T0mWyeah, reversing compiled code is "interesting"
08:44.59T0mWIts not hand written assembler is it?
08:45.27MonMothanot past the first few lines
08:45.33T0mWk
08:45.35MonMothasome of it is VERY obviously compiler generated
08:45.52MonMothalike 20 instructions worth of masks that could be condensed into 4 if you wanted to
08:46.09*** join/#elinux HJBIII (n=HJBIII__@c1-30-13.rrba.isadsl.co.za)
08:46.33Zta...damn.  T0mW turned out not to be Tom Waits after all.
08:46.38T0mWheh, one customer wanted me to implement some security in his new board because he was afraid someone could reverse engineer 150K of compiled ARM C code.
08:47.05MonMothahahaq
08:47.15MonMothayeah, you can...if you have infinite, worthless time on your hands
08:47.15T0mWyeah, idiot
08:47.29MonMothabasically, just make sure the startup is reasonably secure if you're afraid and most people will just plain give up
08:47.46T0mWOh, he thought there was a utility that would do it for you: reconstitute C from machine code
08:48.36MonMothanot in any intelligent manner
08:48.41T0mWheh
08:48.52MonMothaif you know the compiler well, you can start to piece things together fairly quickly, but even then it's hard to automate
08:49.02MonMothaat best you can pull out basic loop constructs with no-name variables
08:49.14T0mWI did reverse 28K of Turbo C generated code once.  That took me a couple of weeks, but I knew that compiler and how it gen'ed code
08:49.23MonMothaIda can sometimes put together switch statements for you
08:49.37MonMothaI don't know what compiler this was, certainly not GCC as far as I can tell
08:49.58T0mWwell, turn on -Os and try to reverse that
08:50.20T0mWI cannot even debug that when I have the source files!
08:50.52T0mWI selectively turn on -O0 to do debugging
08:53.32T0mW`candy_storeTomW.com is for sale $4,088.00
08:53.44T0mW`candy_storewho are they kidding?
08:53.46T0mW`candy_store!
08:54.13MonMothahaha
09:15.10T0mWI got a brownie
09:39.15MonMothawell, I got to go to bed :)
09:39.30MonMothathough a brownie sounds nice
09:40.30T0mWand the apple strudul was good too
09:47.37*** join/#elinux noclouds (n=mhfan@60.166.48.24)
11:33.06*** join/#elinux jayakumar2 (n=jayakuma@203.121.47.18)
11:38.43chouimatmorning
11:39.10*** join/#elinux tuxmaniac (n=aanjhan@60.254.67.17)
13:18.52*** join/#elinux cbrake (i=user103@216.144.26.242)
13:34.44*** join/#elinux Crofton (n=balister@hc6521dcb.dhcp.vt.edu)
13:38.12*** join/#elinux gcl (n=gcl@S0106001346b91f0f.cg.shawcable.net)
14:03.48*** join/#elinux kris (n=Asier@197.Red-80-38-245.staticIP.rima-tde.net)
14:21.54CosmicPenguinmorning
14:27.25*** part/#elinux kris (n=Asier@197.Red-80-38-245.staticIP.rima-tde.net)
14:29.19*** join/#elinux chouimat (n=dieu@kde/developer/chouinard)
15:14.39*** join/#elinux bbart (n=bbart@p54BDFDC5.dip.t-dialin.net)
15:19.47*** join/#elinux ctaylor (n=ctaylor@static-70-106-125-178.pskn.east.verizon.net)
15:22.19ctayloranyone know what controls when buildroot decides to make the filesystem, I'm having a problem where it is making the jffs2 filesystem image before it has finished compiling all the components.
15:28.04*** join/#elinux eggers (n=eggers@bi01p1.co.us.ibm.com)
15:53.29*** join/#elinux likewise (n=chatzill@82-171-189-134.dsl.ip.tiscali.nl)
15:53.36*** part/#elinux likewise (n=chatzill@82-171-189-134.dsl.ip.tiscali.nl)
16:09.14*** join/#elinux mallum (n=mallum@host86-141-47-51.range86-141.btcentralplus.com)
16:09.15*** mode/#elinux [+v mallum] by ChanServ
16:09.54mallumhey file
16:24.46*** join/#elinux lyakh (n=lyakh@85.197.31.25)
16:44.36*** join/#elinux hufnus (n=slonsiki@DSL135-086.labridge.com)
16:58.32*** join/#elinux tuxmaniac (n=aanjhan@60.254.67.17)
17:00.43CosmicPenguinmallum: greets
17:14.43mallumhey CosmicPenguin
17:16.33kergothmorning
17:19.21CosmicPenguinmallum: everything going well over at ol' o-hand?
17:21.04mallumCosmicPenguin: yeah pretty well
17:42.23ricmmkergoth: hello there
20:14.53*** join/#elinux ctaylor (n=ctaylor@static-70-106-125-178.pskn.east.verizon.net)
21:28.55*** join/#elinux Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net)
21:39.55*** join/#elinux FireEgl (n=FireEgl@Atlantica.IRCNut.Com)
22:26.56*** join/#elinux andersee (n=andersen@codepoet.org)
22:26.56*** mode/#elinux [+o andersee] by ChanServ
22:37.47kergothchouimat: ping
22:39.57CosmicPenguinpivot you rat bastard!
23:42.26chouimatkergoth: pong

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.