**** BEGIN LOGGING AT Thu Jul 26 02:59:56 2007
Jul 26 04:35:23 <CIA-12> nbd * r8165 / (2 files in 2 dirs):
Jul 26 04:35:23 <CIA-12> brcm47xx-2.6: add a few nops here, some irq saving there, blast the full cache on page icache flushes
Jul 26 04:35:23 <CIA-12> i really hate the broadcom cpu bugs, but it's much more stable now.
Jul 26 04:35:23 <CIA-12> PS: A /* Ouch */ in the original source showed me the way ;)
Jul 26 05:32:42 <sn9> i no longer have wifi connected to the internet
Jul 26 05:33:53 <sn9> i had to take the dg834g out of service
Jul 26 05:39:35 <sn9> earth to {Nico} ...
Jul 26 06:17:28 <glp> [mbm]: are you here?
Jul 26 06:27:51 <{Nico}> sn9: {Nico} to ground control...
Jul 26 06:28:38 <sn9> {Nico}: can you please explain the @ in changeset 8107?
Jul 26 06:30:39 <{Nico}> sn9: @ is to keep make commands silent
Jul 26 06:31:01 <sn9> a silent comment?
Jul 26 06:31:11 <{Nico}> try removing just the @
Jul 26 06:31:23 <sn9> it breaks the build unless i remove the @
Jul 26 06:31:42 <{Nico}> it works if you keep the comment?
Jul 26 06:33:09 <sn9> only without the @
Jul 26 06:33:29 <sn9> the # still has to be there
Jul 26 06:36:21 <{Nico}> ok, i'll commit the change then
Jul 26 06:37:12 <sn9> i have no idea why non-rdc builds haven't been reported as broken
Jul 26 06:43:29 <CIA-12> nico * r8166 /trunk/include/image.mk: remove the @ and change the comment from [8107] (closes: #2122)
Jul 26 09:08:21 <CIA-12> florian * r8167 /trunk/package/uvcvideo/ (. Makefile): Add uvcvideo driver (#1997)
Jul 26 09:11:43 <CIA-12> florian * r8168 /packages/multimedia/uvc-streamer/ (. Makefile): Add uvc-streamer (#2120)
Jul 26 09:40:26 <sn9> [florian]: ping
Jul 26 09:43:03 <[florian]> sn9: pong
Jul 26 09:43:10 <sn9> http://homepage.mac.com/danielg4/rdc.patch
Jul 26 09:43:43 <sn9> try it with http://homepage.mac.com/danielg4/rdc.config
Jul 26 09:44:57 <[florian]> thanks, does it boot now with the rewritten x86 code ?
Jul 26 09:46:04 <sn9> unknown; it booted fine prior to the most recent change (turning napi back on after testing without), but i am unable to test this iteration
Jul 26 09:46:39 <sn9> the only change i made since it booted ok was turning napi back on
Jul 26 09:47:03 <[florian]> you mean, even with a .21 kernel it booted ?
Jul 26 09:47:08 <sn9> .22
Jul 26 09:47:40 <[florian]> oh, nice, I did not get anything booting between .19.2 and .22
Jul 26 09:48:01 <sn9> neither did i, until this patch
Jul 26 09:48:59 <sn9> oh, there was a second thing i changed that i also intended to test
Jul 26 09:50:00 <sn9> with FW_LOADER compiled in, rt61 would not load firmware, so i wanted to try it as a module
Jul 26 09:50:42 <sn9> try the patch as is, with this .config, and report back
Jul 26 09:50:51 <[florian]> will tell you
Jul 26 10:04:40 <CIA-12> nbd * r8169 /tags/kamikaze_7.07/target/linux/x86-2.6/config/default: add missing config options
Jul 26 10:09:39 <CIA-12> olli * r8170 /packages/net/lighttpd/ (Makefile patches/500-configure_cross.patch):
Jul 26 10:09:39 <CIA-12> lighttpd:
Jul 26 10:09:39 <CIA-12>  * Update: 1.4.15 > 1.4.16
Jul 26 10:09:39 <CIA-12>  * Cleanup Makefile
Jul 26 10:09:39 <CIA-12>  * Refresh patches
Jul 26 11:32:11 <CIA-12> nbd * r8171 / (2 files in 2 dirs): ignore filenames that can cause problems for the recursive dependency handling
Jul 26 11:46:17 <CIA-12> kaloz * r8172 /tags/kamikaze_7.07/package/ (6 files in 5 dirs): backport avr32 fixes from trunk
Jul 26 11:49:08 <CIA-12> kaloz * r8173 /tags/kamikaze_7.07/target/linux/avr32-2.6/: add back avr32 to 7.07
Jul 26 11:50:28 <Kaloz> .win 42
Jul 26 11:52:39 <CIA-12> kaloz * r8174 /tags/kamikaze_7.07/target/linux/avr32-2.6/config/default: currently we only support usb host mode, and that isn't available on avr32
Jul 26 11:54:07 <CIA-12> kaloz * r8175 /tags/kamikaze_7.07/target/linux/avr32-2.6/config/default: fix typo - I'm too tired
Jul 26 13:00:41 <CIA-12> nbd * r8176 /tags/kamikaze_7.07/package/spca5xx/Makefile: add a missing dependency
Jul 26 13:04:53 <CIA-12> nbd * r8177 /tags/kamikaze_7.07/package/spca5xx-le/Makefile: this one needs it as well
Jul 26 14:09:00 <CIA-12> nbd * r8178 /tags/kamikaze_7.07/target/linux/adm5120-2.6/: remove adm5120 from 7.07 branch - too early, not release quality yet
Jul 26 14:45:38 <CIA-12> olli * r8179 /packages/utils/mc/ (. Makefile): Add mc package
Jul 26 14:49:48 <CIA-12> olli * r8180 /packages/utils/mc/Makefile: mc: add a better title and description
Jul 26 15:02:55 <cosmo1t> does 7.07 have added support for wrt350n?
Jul 26 15:03:11 <cosmo1t> i know it's something to do w/ the driver
Jul 26 15:10:49 <[florian]> cosmo1t: I think it has not, it lacks support for the gige driver
Jul 26 15:13:09 <cosmo1t> ya..
Jul 26 15:13:09 <cosmo1t> dammit
Jul 26 15:13:19 <cosmo1t> i wish i knew how to find source for those drivers
Jul 26 15:13:23 <cosmo1t> sucks they bundle only the .o files
Jul 26 15:13:28 <cosmo1t> in the linksys  packages
Jul 26 15:13:49 <nbd> the tg3 driver can be used
Jul 26 15:13:52 <nbd> the open source one
Jul 26 15:14:02 <nbd> just have to add a few gpio fixups and test it properly
Jul 26 15:14:14 <nbd> the problem is finding the time to do it
Jul 26 15:14:22 <cosmo1t> id' do it, but i have no way to test it really
Jul 26 15:14:32 <cosmo1t> i have a 300n and a 350n
Jul 26 15:14:44 <cosmo1t> so i suppose i could load up the 300n, swap out the 350 w/ the 300
Jul 26 15:14:47 <cosmo1t> and use that to test
Jul 26 15:14:54 <cosmo1t> do i need a jtag cable in case the driver doesn't work?
Jul 26 15:15:01 <nbd> you need a serial cable
Jul 26 15:15:02 <cosmo1t> or would i be able to reflash via the wireless?
Jul 26 15:15:16 <nbd> and you can reflash over the wired
Jul 26 15:15:21 <nbd> if something goes wrong
Jul 26 15:15:24 <nbd> using the boot loader
Jul 26 15:15:35 <cosmo1t> even if the gige driver doesn't wokr?
Jul 26 15:16:06 <cosmo1t> do you guyz usually solder a pin header into the board?
Jul 26 15:16:08 <[florian]> of course
Jul 26 15:16:32 <[florian]> the bootloader can handle the ethernet driver, just the ethernet driver needs to be tested from a linux kenrel
Jul 26 15:16:50 <cosmo1t> i'm totally n ew to the terminology here.. pio is an interrupt input/output mode correct?
Jul 26 15:16:53 <[florian]> what you can do, is load a ramdisk image, once in, try to load the modified tg3 driver and reload it
Jul 26 15:16:53 <cosmo1t> so what is gpio then?
Jul 26 15:17:11 <[florian]> pio, yes, gpio is general purpose input ouput
Jul 26 15:17:29 <cosmo1t> ah.. and the tg3 driver is coded for an older version of gpio?
Jul 26 15:17:35 <cosmo1t> i'm assuming gpio is a standardized library?
Jul 26 15:17:45 <[florian]> no, the tg3 is coded to be used with pci/pci-e cards
Jul 26 15:18:11 <[florian]> it basically means that the tg3 does not know how to control your ethernet device
Jul 26 15:18:19 <cosmo1t> and pci/pci-e is in itself a input/output protocol..
Jul 26 15:18:29 <cosmo1t> so do you have a wrapper that converts pci/pci-e to teh gpio?
Jul 26 15:18:29 <[florian]> it is a bus
Jul 26 15:18:48 <cosmo1t> well what commadns would the tg3 issue on the bus to the device
Jul 26 15:19:41 <cosmo1t> instead of wasting your time do you have a reference url you guys use?
Jul 26 15:19:42 <[florian]> better than having a wrapper, it could use the gpio lines directly to probe and control the device
Jul 26 15:19:50 <[florian]> I do not think so
Jul 26 15:20:39 <cosmo1t> because there is no real bus.. i get it now, sorry
Jul 26 15:20:58 <[florian]> well, there is a bus, which is ssb
Jul 26 15:21:03 <[florian]> another kind of bus
Jul 26 15:21:19 <cosmo1t> designed for smaller usage? less complex..?
Jul 26 15:21:40 <[florian]> designed to plug intellectual property cores of functionnalities
Jul 26 15:21:46 <[florian]> for that I can give you something to read
Jul 26 15:22:01 <cosmo1t> propietary..
Jul 26 15:22:03 <cosmo1t> lovely
Jul 26 15:23:16 <[florian]> not necesseraliy proprietary
Jul 26 15:23:32 <[florian]> it is meant to be used within an electronic design, so yes, it can be proprietary
Jul 26 15:23:45 <[florian]> http://voodoowarez.com/bcm5365p.pdf
Jul 26 15:24:56 <cosmo1t> ok cool, now to setup the ram disk.. i currently have dd-wrt on the 350n (sorry), i could setup the ram disk in there?? or do i need to get it flashed w/ openwrt, just no ethernet driver?
Jul 26 15:25:08 <cosmo1t> and then what part of the codebase would the edits have to go in
Jul 26 15:25:22 <cosmo1t> i've checked out the code from svn, but i dont' fully understand the layout of the code
Jul 26 15:25:25 <[florian]> you have to build your firmware from trunk/ choose brcm47xx-2.6
Jul 26 15:25:37 <[florian]> you will understand ;)
Jul 26 15:26:03 <cosmo1t> so in svn, do you have repo setup for each architecture?
Jul 26 15:26:12 <cosmo1t> or does open-wrt have a main code base, then architecture plug ins?
Jul 26 15:26:40 <cosmo1t> i'm sorry for all these questions, but i do want to help out..
Jul 26 15:26:49 <cosmo1t> next.. what IDE do you use, or are u just pure VI :)
Jul 26 15:26:52 <[florian]> we have a specific kernel for every architecture
Jul 26 15:27:02 <[florian]> we use vi or emacs or whatever in general
Jul 26 15:27:18 <[florian]> there is not really sense in using an ide such as eclipse for instance
Jul 26 15:27:39 <[florian]> and the key feature of openwrt is that it behaves the same way on every hardware you install
Jul 26 15:27:41 <cosmo1t> hmm cause thats what i had checked it out.. but i agree, the makefile stuff seemed pointeless
Jul 26 15:27:47 <[florian]> no matter what architecture/processor/wifi card it uses
Jul 26 15:27:58 <cosmo1t> so in order to make the kernel work on each piece of hardware
Jul 26 15:28:20 <cosmo1t> do yo uhave to build it using a specific set of chain tools?
Jul 26 15:28:47 <[florian]> well, there are targets like : arm, mips, mipsel, x86
Jul 26 15:28:50 <cosmo1t> i dont' think 98% of the popel that use open-wrt or dd-wrt have any idea how difficult all this stuff can be
Jul 26 15:28:57 <CIA-12> nbd * r8181 / (6 files in 6 dirs): add source feed rev to menuconfig, set 8180 as default rev for kamikaze 7.07
Jul 26 15:29:04 <cosmo1t> so x86, would be just to turn it on any box
Jul 26 15:29:09 <[florian]> and for every single target, you need a compiler, standard library and assembler for that
Jul 26 15:29:15 <cosmo1t> wow
Jul 26 15:29:33 <[florian]> openwrt eases the work of creating such a toolchain, because it can be annoying
Jul 26 15:29:34 <cosmo1t> if for example, you are compiling on an x86 processor, do yo u have to compile the specific compiler for that arch?
Jul 26 15:29:44 <cosmo1t> (like mips)
Jul 26 15:29:47 <nbd> openwrt uses uclibc
Jul 26 15:29:47 <[florian]> yes
Jul 26 15:29:51 <nbd> so it has to create a cross compiler
Jul 26 15:30:01 <nbd> since you can't compile for uclibc with the one on the host
Jul 26 15:30:06 <[florian]> nbd: it would have to create one if we used libc as well
Jul 26 15:30:30 <[florian]> cosmo1t: by default your x86 compiler produces x86 code
Jul 26 15:30:38 <cosmo1t> does the cross compiler create an intermideate set of data (like bytecode) that then can get processed by the specific arch compiler?
Jul 26 15:30:43 <cosmo1t> right florian i know that ;)
Jul 26 15:30:47 <cosmo1t> thats why i was asking
Jul 26 15:31:02 <cosmo1t> fascinating stuff
Jul 26 15:31:04 <[florian]> cosmo1t: not bytecode, because we deal with c/c++ so it is only object files (ELF)
Jul 26 15:31:34 <cosmo1t> but the cross compiler since it's compiled on the host, knows how to read those ELF files and then create teh appropriate object files for the specific architecture
Jul 26 15:31:42 <[florian]> absolutely
Jul 26 15:31:48 <cosmo1t> kick ass.
Jul 26 15:31:54 <cosmo1t> i've never had to deal w/ cross compilers
Jul 26 15:32:01 <cosmo1t> i've been coding c++ for a long time too.
Jul 26 15:32:36 <[florian]> well, you can code c++ or c without even knowing the mechanics behing though you might face big issues
Jul 26 15:33:04 <[florian]> I would not recommend so, but it can happen
Jul 26 15:33:04 <cosmo1t> well i started coding c++ on sun sparc boxes
Jul 26 15:33:13 <[florian]> ah, at school or ?
Jul 26 15:33:24 <cosmo1t> at shcool it was just x86.. but didn't learn much
Jul 26 15:33:33 <cosmo1t> my first real job was doing back end batch financial processing in c++
Jul 26 15:33:43 <cosmo1t> i converted all teh old c programs to OO based extendeable systems
Jul 26 15:33:56 <cosmo1t> but that code puked hard w/ seg faults on x86 boxes when we "upgraded"
Jul 26 15:34:06 <cosmo1t> plus teh damn sys admins like upgrading the gcc, whcih of course casues nightmares
Jul 26 15:34:30 <cosmo1t> ah well.
Jul 26 15:34:33 <[florian]> it should not if your code is ansi C :)
Jul 26 15:34:39 <[florian]> anyway, I see
Jul 26 15:34:43 * cosmo1t coughs
Jul 26 15:34:55 <cosmo1t> so how would u recommend doing the ram disk on the 350n?
Jul 26 15:35:09 <[florian]> well, do you have a serial cable for it ?
Jul 26 15:35:21 <cosmo1t> i'm going to make one. i've got some conversion thing i bought a while ago
Jul 26 15:35:31 <cosmo1t> maxxus 350b or something. it's downstairs
Jul 26 15:35:33 <[florian]> if so, when in the bootloader, just load the vmlinux image it produces
Jul 26 15:35:36 <cosmo1t> i know how to solder, etc
Jul 26 15:36:19 <cosmo1t> does teh serial cable allow you to control the booting of the box? i thought it was just to transfer images, etc
Jul 26 15:36:47 <[florian]> yes, you can interrupt the booting process
Jul 26 15:36:52 <[florian]> diagnose the board
Jul 26 15:37:01 <[florian]> load a kernel, whatever
Jul 26 15:37:12 <cosmo1t> kick ass.
Jul 26 15:37:24 <cosmo1t> well i gotta build the cable. i suppose google will tell me where, unless your wiki has a link on it
Jul 26 15:37:44 <[florian]> it is a preriquisite to real hacking :)
Jul 26 15:37:51 <[florian]> you named it
Jul 26 15:37:57 <nbd> cosmo1t: if you can, get a cheap siemens s45 usb datacable off ebay
Jul 26 15:38:12 <nbd> doesn't have to be siemens, i think there's a list of other cables that work somewhere
Jul 26 15:38:20 <nbd> it just should be the usb variant
Jul 26 15:38:35 <nbd> it contains an usb2serial chip that can deal with the correct voltage level of the board
Jul 26 15:38:40 <cosmo1t> ok i'll go dig around. do you actually have links to constructing your own?
Jul 26 15:38:58 <nbd> i always use cell phone cables because they're cheaper
Jul 26 15:39:25 <[florian]> I personnaly order samples of ttl converters at sipex.com
Jul 26 15:40:17 <cosmo1t> i've actually got a garmin serial to usb converter
Jul 26 15:43:56 <CIA-12> olli * r8182 /packages/utils/mc/ (Makefile patches/ patches/100-fix-missingsyntax.patch): mc: add a patch to fix the annoying error message about missing Syntax file (#2133)
Jul 26 15:48:12 <[florian]> cosmo1t: something for your to read : http://bcm-specs.sipsolutions.net/BackPlane
Jul 26 15:53:01 <cosmo1t> cool thanks, i have the ad233bk 233a ver 4 kit here already, so i'll just build my own serial kit
Jul 26 15:53:35 <cosmo1t> but what i do need to know, is can i load openwrt on teh 300n and have the packges supported (i mean 7.06) or if 7.07 is out soon, i'll use that
Jul 26 15:54:58 <cosmo1t> i've read mixed things on teh forum
Jul 26 16:14:10 <CIA-12> nbd * r8183 /trunk/scripts/metadata.pl: fix a prereq bug
Jul 26 16:23:17 <sn9> [florian]: did you try the patch with that .config yet?
Jul 26 17:42:29 <sn9> ejka: you do a lot of ar7 stuff right?
Jul 26 17:43:37 <sn9> s/stuff/stuff,/
Jul 26 18:15:41 <[florian]> sn9: back online
Jul 26 18:22:59 * loswillios leans back and enjoys
Jul 26 19:56:56 <[florian]> sn9: ping /
Jul 26 20:00:22 <CIA-12> florian * r8184 /trunk/package/rt2x00/ (31 files in 2 dirs): Add rt2x00-mac80211 snapshot (#1916)
Jul 26 20:05:33 <[florian]> sn9: tested your rdc patch, does not seem to get the device booting
Jul 26 20:54:03 <[florian]> sn9: ok, got the board booting with a smaller kernel and no lzma, now trying with the lzma stuff
Jul 26 20:59:29 <sn9> [florian]: i had it booting exactly as submitted, expect without NAPI, and with FW_LOADER compiled in instead of a module
Jul 26 21:00:40 <sn9> but rt61 refused to load, complaining about firmware, so i wanted to test without FW_LOADER
Jul 26 21:08:44 <[florian]> sn9: weird
Jul 26 21:10:49 <[florian]> sn9: anyway, I will merge your changes, this is not the first time I mess up the kernel config
Jul 26 21:11:28 <sn9> i will be able to test in a few minutes
Jul 26 21:12:17 <[florian]> you also have an ar525w right ?
Jul 26 21:13:35 <sn9> yes, but i will be testing on someone else's borrowed ar525w. i can do no further testing on my ar525w in the short term
Jul 26 21:14:43 <sn9> the solder mask is too damaged to be able to tap into serial without soldering directly to the cpu, and i'm gonna need help with that
Jul 26 21:15:33 <[florian]> you could probably buy another one ?
Jul 26 21:15:47 <sn9> i've borrowed another one
Jul 26 21:16:06 <sn9> i will be hooking it up in a minute
Jul 26 21:16:07 <[florian]> the lzma loader seems to prevent my device from booting here
Jul 26 21:16:17 <sn9> lzma worked on mine
Jul 26 21:16:53 <[florian]> nbd told me there was some decompression problems with kernels > 19
Jul 26 21:17:13 <sn9> it worked with .22 with that patch
Jul 26 21:17:37 <[florian]> I trust you, just mine seems to behave differently
Jul 26 21:17:44 <[florian]> or my build is messed up, I do nont know
Jul 26 21:18:10 <sn9> i will know shortly
Jul 26 21:18:19 <CIA-12> florian * r8185 /trunk/target/linux/rdc-2.6/ (5 files in 2 dirs): Use the new x86 code, thanks sn9 !
Jul 26 21:18:48 <[florian]> will rebuild a full target
Jul 26 21:19:12 <[florian]> I am thinking of a second stage bootloader/loader for this device
Jul 26 21:21:27 <sn9> flashing now
Jul 26 21:22:42 <sn9> no boot
Jul 26 21:23:23 <sn9> i will rebuild
Jul 26 21:25:19 <[florian]> it does not boot either ?
Jul 26 21:25:31 <[florian]> the kernel config is very touchy
Jul 26 21:25:36 <sn9> right. one of my last changes hosed it
Jul 26 21:27:45 <[florian]> I go to bed, will test tomorrow
Jul 26 21:27:49 <[florian]> thanks for your work
Jul 26 21:27:58 <[florian]> let's get this device stable in the time now ;)
Jul 26 21:28:20 <sn9> if you hang on for about 20 min, i'll have it working again
Jul 26 21:28:33 <[florian]> ok, fine with 20 mins :)
Jul 26 21:31:04 <sn9> it will take an estimated 3 iterations of config/make/flash
Jul 26 21:31:34 <nbd> that was the same problem i had back then when i ported the lzma loader to x86-2.6 and tried to clean it up
Jul 26 21:31:40 <nbd> most builds would crash but sometimes i had a working one
Jul 26 21:32:21 <[florian]> nbd: the main problem is that if you disable lzma, you have to cut down the kernel dramatically :/ like not net stack
Jul 26 21:32:34 <nbd> yeah, lzma needs to be fixed
Jul 26 21:32:47 <sn9> i had it working
Jul 26 21:33:09 <sn9> strange thing was, that /proc/cpuinfo said "unknown"
Jul 26 21:33:59 <[florian]> not even 486 ?
Jul 26 21:34:04 <[florian]> well, weird
Jul 26 21:34:17 <sn9> yes, 486, unknown stepping
Jul 26 21:34:37 <sn9> it always had the cyrix id before
Jul 26 21:35:24 <sn9> nbd: last night i had to put my very first router back into service
Jul 26 21:36:11 <sn9> the dg834g began to behave very strangely, and i need to know whether the problem is hardware or software
Jul 26 21:37:37 <sn9> whenever anything that's powered on is plugged into ethernet, the dsl keeps losing synch
Jul 26 21:38:27 <sn9> if only connected over wifi, it's fine
Jul 26 21:38:31 <CIA-12> nbd * r8186 /trunk/target/linux/adm5120-2.6/files/arch/mips/pci/ops-adm5120.c: protect the adm5120 pci ops with a spinlock - fixes race conditions that happened in combination with madwifi and more than one card
Jul 26 21:40:41 <loswillios> fyi openwrt.org still says Latest release: 7.06 on the right
Jul 26 21:43:58 <nbd> i think i have to wait for mbm to change that one
Jul 26 21:44:58 <sn9> nbd: any idea wrt that dg834g problem?
Jul 26 21:45:57 <nbd> no
Jul 26 21:47:42 <sn9> i guess it will finally give me the opportunity to try the ar7 port on it, which is ironically why i originally got it
Jul 26 21:48:02 <nbd> there will be a 2.6.22 update for ar7 soon
Jul 26 21:48:06 <nbd> i suggest trying it after that
Jul 26 21:48:41 <sn9> i just won't be able to test the dsl part, at least not reliably
Jul 26 21:49:00 <sn9> unless, of course, it "just works"
Jul 26 21:54:38 <sn9> [florian]: flashing
Jul 26 21:55:54 <sn9> no go. 2nd iteration...
Jul 26 22:02:38 <sn9> [florian]: you can sleep if you wish
Jul 26 22:42:06 <sn9> btw, here's the transcript of when it booted successfully: http://pastebin.ca/635232
Jul 27 00:27:56 <sn9> ok, who's around who can commit a patch?
Jul 27 00:39:33 <{Nico}> sn9: i am!
Jul 27 00:40:00 <sn9> http://homepage.mac.com/danielg4/rdc.patch
Jul 27 00:41:26 <sn9> it makes the kernel actually boot
Jul 27 00:43:50 <sn9> do i hear CIA-12 say r8187?
Jul 27 00:44:12 <{Nico}> any credit you would like to see in the commit message?
Jul 27 00:44:55 <sn9> [florian] usually just puts "sn9" despite previous requests to use my name
Jul 27 00:46:06 <{Nico}> give me your name and i'll just put a "<your name> aka sn9" in there
Jul 27 00:46:42 <sn9> ok. i'm the last guy who edited http://wiki.openwrt.org/RDCPort -- my name is in the log there
Jul 27 00:49:50 <CIA-12> nico * r8187 /trunk/target/linux/rdc-2.6/config/default: update rdc-2.6 config (thanks to Daniel Gimpelevich)
Jul 27 00:50:11 <{Nico}> sn9: happy? :)
Jul 27 00:50:15 <sn9> thanx
Jul 27 00:59:46 <CIA-12> nico * r8188 /trunk/target/linux/ar7-2.6/files/arch/mips/ar7/vlynq.c: cosmetic fix (indent and use c-style comments)
Jul 27 01:48:10 <sn9> nbd: i'm sorry, you were right. the problem does lie in the lzma after all
Jul 27 01:49:28 <sn9> every now an then, a build works, but other times, it doesn't, EVEN IF THERE WERE NO CHANGES WHATSOEVER
**** ENDING LOGGING AT Fri Jul 27 02:59:56 2007