**** BEGIN LOGGING AT Thu Jan 12 02:59:57 2012
Jan 12 04:44:32 <builder_> build #115 of ps3 is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/ps3/builds/115
Jan 12 05:15:11 <builder_> build #116 of ramips is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/116
Jan 12 05:44:46 <Olipro> nbd: is there a function I can call in the linux kernel that will set the CU0 bit of the status register to 1 (MIPS)
Jan 12 05:44:59 <Olipro> or do you know of a way to read the timer count register from coprocessor 0 in usermode
Jan 12 06:02:03 <builder_> build #115 of pxcab is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/115
Jan 12 06:06:46 <russell--> fwiw, i'm not seeing the ath5k gain calibration failure on r28165 atheros build
Jan 12 06:07:16 <russell--> circa mid-november
Jan 12 06:12:41 <builder_> build #109 of ppc44x is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/109
Jan 12 06:12:50 <russell--> -PKG_VERSION:=2011-11-04
Jan 12 06:12:51 <russell--> +PKG_VERSION:=2011-12-01
Jan 12 06:41:06 <CIA-84> swalker * r29714 /packages/ (6 files in 3 dirs): [packages] add libimobiledevice, libplist & usbmuxd for iPhone tethering (#10157)
Jan 12 08:23:02 <builder_> build #112 of rb532 is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/112
Jan 12 08:51:02 <builder_> build #102 of avr32 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/102
Jan 12 09:18:23 <CIA-84> loswillios * r29715 /packages/sound/pulseaudio/Makefile: [packages] pulseaudio: make configfiles readable by user pulse (#10728)
Jan 12 09:18:24 <CIA-84> loswillios * r29716 /packages/sound/pulseaudio/Makefile: [packages] pulseaudio: sync with recent avahi changes (#10727)
Jan 12 09:23:15 <CIA-84> loswillios * r29717 /packages/sound/pulseaudio/Makefile: [packages] pulseaudio: fix r29716
Jan 12 09:24:18 <builder_> build #107 of uml is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/107
Jan 12 09:27:49 <loswillios> {Nico}: was there a specific reason to let pulseaudio run as user pulse/pulse? it can't access sound hardware anymore now (/dev/snd/ is root-only)
Jan 12 09:46:50 <builder_> build #108 of x86 is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/108
Jan 12 10:15:18 <CIA-84> nbd * r29718 /trunk/target/linux/generic/files/drivers/net/phy/ar8216.c: ar8216: do not strip vlan tags when running with vlan_enable=0
Jan 12 10:15:19 <CIA-84> nbd * r29719 /trunk/target/linux/generic/files/drivers/net/phy/ar8216.c:
Jan 12 10:15:19 <CIA-84> ar8216: use vlan configuration for connecting ports (forced to be untagged) even with vlan_enable=0, but keep them isolated before the switch has been configured
Jan 12 10:15:19 <CIA-84> this makes enable_vlan=0 practical for vlan passthrough
Jan 12 10:15:22 <CIA-84> nbd * r29720 /trunk/package/libnl-tiny/src/unl.c: libnl-tiny: fix a potential memleak in an error path
Jan 12 10:15:25 <CIA-84> nbd * r29721 /trunk/toolchain/gcc/common.mk: gcc: always explicitly link against libstdc++, fixes build errors on some hosts that refuse to link it in implicitly (should fix #10587)
Jan 12 10:34:19 <jow_laptop> loswillios: the general idea was to move services to users
Jan 12 10:34:31 <jow_laptop> loswillios: we can fix the /dev/snd permissions in the hotplug2 rules
Jan 12 10:34:46 <jow_laptop> though there should be a sounds group
Jan 12 10:34:59 <jow_laptop> so pulse:sound instead of pulse:pulse
Jan 12 11:00:37 <CIA-84> jow * r29722 /packages/net/miniupnpd/ (Makefile files/miniupnpd.init): [packages] miniupnpd: convert netmask to prefix and write listen address in CIDR notation (#10767, #10770)
Jan 12 11:17:32 <loswillios> jow_laptop: so it should be root:audio for /dev/snd?
Jan 12 11:17:42 <blogic> hi at74
Jan 12 11:17:43 <loswillios> (seeing there's already an audio group present)
Jan 12 11:17:47 <blogic> in your openwrt tree you have this file --> target/linux/ramips/files/drivers/net/ramips_esw.c
Jan 12 11:17:50 <jow_laptop> loswillios: yes
Jan 12 11:17:55 <blogic> this is the faile you need to modify
Jan 12 11:18:01 <loswillios> ok
Jan 12 11:18:17 <at74> hi
Jan 12 11:24:13 <loswillios> jow_laptop: any idea why this doesn't work? http://pastebin.com/zxMnC5fY
Jan 12 11:24:45 <jow_laptop> loswillios: let me check the hotplug2 source
Jan 12 11:25:51 <loswillios> ah, found http://code.google.com/p/hotplug2/source/browse/trunk/docs/rules/hotplug2-complex-ownership.rules
Jan 12 11:25:56 <jow_laptop> loswillios: chgrp audio /dev/...
Jan 12 11:26:09 <loswillios> ok
Jan 12 11:26:11 <jow_laptop> chown does not understand user:group tuples, just user
Jan 12 11:26:33 <alextai> blogic: hi again (at74 and alextai is the same - different computers)
Jan 12 11:26:56 <alextai> I had a look in esw
Jan 12 11:27:24 <alextai> honestly... seems that I would better first read some book on MIPS
Jan 12 11:27:26 <blogic> ok
Jan 12 11:27:31 <blogic> hehe
Jan 12 11:27:36 <alextai> currently have too many questions
Jan 12 11:27:36 <blogic> that wont help for your problem
Jan 12 11:27:44 <blogic> do you have a datasheet for the rt3050 ?
Jan 12 11:27:56 <blogic> the doc you need is the datasheet
Jan 12 11:28:00 <blogic> without it it will never work
Jan 12 11:28:10 <alextai> not yet - I think it is under NDA
Jan 12 11:28:17 <blogic> yes
Jan 12 11:28:21 <blogic> you need a nda then
Jan 12 12:30:16 <builder_> build #102 of xburst is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/102
Jan 12 12:50:27 <alextai> blogic: I will try to get this datashit
Jan 12 12:50:35 <alextai> datasheet :)
Jan 12 12:50:53 <blogic> alextai: good
Jan 12 12:51:00 <blogic> it will help you setup the esw
Jan 12 12:51:07 <blogic> imo that driver is missing some stuff
Jan 12 12:51:14 <blogic> there is basic esw support
Jan 12 12:51:27 <blogic> but if you want double vlaning i think you need to tweak the code
Jan 12 12:51:36 <alextai> anyway... I need to know how to "speak" with hardware
Jan 12 12:51:42 <blogic> the actual mapping of whch port becomes wan/lan uses vlans
Jan 12 12:51:55 <blogic> so if you want to have a vlan come out of a lan port ......
Jan 12 12:52:11 <alextai> I saw some wllll and llllw mapping... so I guess that it is somewhere ther
Jan 12 12:52:58 <alextai> the wierd part that it seems that MAC addresses are being retrieved from flash... can this be true?
Jan 12 12:53:20 <blogic> yes
Jan 12 12:53:36 <blogic> ralink units have a 0x200 byte size eeprm
Jan 12 12:53:41 <blogic> normally located at 0x40000
Jan 12 12:53:47 <alextai> is this part of flash should be documented somewhere?
Jan 12 12:53:55 <blogic> nope
Jan 12 12:54:18 <blogic> the 0x200 byte blob always start with 0x3050 for a 3050 unit
Jan 12 12:54:26 <blogic> followed by the calibration data of the wifi
Jan 12 12:54:32 <blogic> and the mac address mappings
Jan 12 12:56:29 <alextai> hm... how then it comes that it works for some  subtargets (like asus dlink and other boards based on the same chipset) and does not work for others (I get MACs like 00:11:22:...)
Jan 12 12:56:31 <alextai> ?
Jan 12 12:57:19 <blogic> looks like a default mac addr
Jan 12 12:57:31 <blogic> is it a custom board you have ?
Jan 12 12:57:41 <blogic> and did you add a mach-*.c file already ?
Jan 12 12:58:01 <alextai> not for both questions
Jan 12 12:58:27 <alextai> the board from some chineese vendor (do not have the casing)
Jan 12 12:58:36 <alextai> and I didn't add mach* files
Jan 12 12:58:42 <blogic> what image do you boot ?
Jan 12 12:59:20 <alextai> one for omni-emb
Jan 12 12:59:52 <builder_> build #102 of ixp4xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/102
Jan 12 13:00:33 <alextai> almost everything is working there for me except switch
Jan 12 13:00:38 <blogic> call this command please
Jan 12 13:00:50 <blogic> hexdump -C /dev/mtd2
Jan 12 13:00:55 <blogic> and pastebin the output
Jan 12 13:01:03 <blogic> that will show us if the eeprom is loaded
Jan 12 13:01:19 <alextai> all of it?
Jan 12 13:01:34 <blogic> well
Jan 12 13:01:38 <blogic> how much does it show you
Jan 12 13:01:45 <blogic> te first 10 lines are enough really
Jan 12 13:01:46 <alextai> a LOT
Jan 12 13:01:49 <blogic> ok
Jan 12 13:01:57 <blogic> in that case that i snot a eeprom :D
Jan 12 13:02:33 <at74> cat /proc/mtd | grep mtd2
Jan 12 13:02:33 <at74> mtd2: 00050000 00010000 "factory"
Jan 12 13:02:42 <blogic> yep
Jan 12 13:02:43 <blogic> http://pastebin.com/6RaRfzNi
Jan 12 13:02:48 <blogic> that is what a eeprom looks like
Jan 12 13:02:56 <blogic> notice the 3050 at the start
Jan 12 13:03:04 <blogic> ok it says 5030 due to endianess
Jan 12 13:03:37 <alextai> but the begging looks alike
Jan 12 13:03:42 <blogic> ok
Jan 12 13:03:49 <alextai> I will pastebin first 30-50 lines
Jan 12 13:03:51 <blogic> show me the frst few lines please
Jan 12 13:03:53 <blogic> ok
Jan 12 13:04:49 <at74> http://pastebin.com/uefJGZWE
Jan 12 13:05:03 <alextai> ok... it is 3052 then
Jan 12 13:05:24 <blogic> yes
Jan 12 13:06:06 <blogic> ah
Jan 12 13:06:07 <blogic> 00050000
Jan 12 13:06:22 <blogic> looks like your eeprom is at a different location
Jan 12 13:06:36 <at74> this is like a MAC I have for eth0 0f 02 22 00 50
Jan 12 13:07:15 <blogic> ok so it does load the right mac
Jan 12 13:07:16 <at74> 00 0f 02 22 00 50
Jan 12 13:07:31 <blogic> if it fails to load the eeprom your mac will be         .mac = { 0x00, 0x11, 0x22, 0x33, 0x44, 0x55 },
Jan 12 13:07:34 <at74> eth0      Link encap:Ethernet  HWaddr 00:0F:02:22:00:50
Jan 12 13:07:36 <blogic> ok
Jan 12 13:07:47 <blogic> so it loads the eeprom
Jan 12 13:07:57 <blogic> i am afraid i need to leave now ....
Jan 12 13:08:01 <blogic> i am starving
Jan 12 13:08:32 <alextai> where does this config comes from?
Jan 12 13:08:38 <alextai> from the manufacturer?
Jan 12 13:09:22 <blogic> yes
Jan 12 13:09:38 <blogic> during manufacturing it is loaded to the flashing
Jan 12 13:11:39 <alextai> So basically I the company signs NDA I should get this data?
Jan 12 13:14:18 <blogic> yes
Jan 12 13:14:45 <alextai> ok... I will write an email to manufacturer
Jan 12 13:19:29 <builder_> build #100 of kirkwood is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/100
Jan 12 13:20:08 <loswillios> jow_laptop: can you commit this? http://pastebin.com/2SqrtarN
Jan 12 13:28:26 <jow_laptop> loswillios: will look later
Jan 12 13:28:31 <loswillios> thanks
Jan 12 13:53:08 <integer`> how i can put musb on n8x0 in host mode by default?
Jan 12 14:51:27 <fullstop> In working with a small arm micro which has a USB HS controller, I see that this specific ARM has support for a maximum of 12 endpoints...
Jan 12 14:51:46 <Chocky> moo
Jan 12 14:51:49 <fullstop> Does such a limitation exist on ar71xx platforms?
Jan 12 14:52:00 <fullstop> I'm merely curious -- no practical application here.
Jan 12 14:52:09 <Chocky> I doubt it, should be a full linux USB setup, right?
Jan 12 14:52:27 <fullstop> Yes, and there's my disconnect...
Jan 12 14:52:43 <fullstop> I'm not really clear on exactly how the host controller and linux are paired.
Jan 12 15:56:34 <Chocks> moo
Jan 12 16:14:37 <builder_> build #102 of ar71xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/102
Jan 12 16:22:13 <Chocks> buffalo u-boot sources are a mess. typical
Jan 12 16:22:16 * Chocks tries to build
Jan 12 16:32:35 <Chocks> toolchain too new. blah
Jan 12 16:42:56 <builder_> build #97 of au1000 is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/97
Jan 12 16:51:46 <Chocks> needed -fpic
Jan 12 16:51:56 * Chocks pats fullstop
Jan 12 16:52:31 <builder_> build #95 of iop32x is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/95
Jan 12 16:52:45 <fullstop> Chocks: There might still be some "unknown" elements present in their sources..
Jan 12 16:52:54 <Chocks> quite.  well, I have a binary now
Jan 12 16:53:00 * Chocks tries it
Jan 12 16:54:22 <Chocks> kexec doesn't like it
Jan 12 17:14:40 <Chocks> probably some comedy linker crap
Jan 12 17:14:49 <Chocks> I'm not sure this is a great route.
Jan 12 17:31:31 <russell--> i am trying to help debug a problem with ath5k, how do you load ath5k with module options?
Jan 12 17:36:16 <jow_laptop> edit /etc/modules.d/*-ath5k
Jan 12 17:45:12 <russell--> just append the options to the line in there?
Jan 12 17:49:21 <jow_laptop> yes
Jan 12 17:50:43 <russell--> cool, working, thanks!
Jan 12 18:22:06 <Chocks> woo
Jan 12 18:22:10 * Chocks pokes fullstop
Jan 12 18:32:16 <fullstop> ja?
Jan 12 18:37:12 <Chocks> got trunk u-boot to run on g300nh
Jan 12 18:37:22 <Chocks> crashes now tho. odd
Jan 12 18:37:26 <Chocks> trying to fix up flash handling
Jan 12 18:41:46 <fullstop> \o/
Jan 12 18:43:50 <builder_> build #94 of etrax is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/etrax/builds/94
Jan 12 19:38:10 <builder_> build #92 of ep93xx is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/92
Jan 12 19:38:11 <builder_> build #89 of gemini is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/89
Jan 12 19:38:14 <builder_> build #88 of rdc is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/rdc/builds/88
Jan 12 19:38:16 <builder_> build #88 of adm5120 is complete: Exception [exception interrupted]  Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/88
Jan 12 22:22:48 <dadada> hey
Jan 12 22:23:16 <dadada> I'm having problems with overlay and mmc device in trunk, just wanted to know if there's something like a known problem
Jan 12 22:23:30 <jow_laptop> missing symbols in dmesg?
Jan 12 22:23:32 <jow_laptop> yes
Jan 12 22:24:17 <dadada> jow_laptop, yes, that's what's happening to me??
Jan 12 22:24:20 <dadada> so this is known?
Jan 12 22:24:38 <jow_laptop> yeah, some issue with xattrs and overlayfs
Jan 12 22:24:49 <dadada> workaround?
Jan 12 22:26:06 <jow_laptop> don't know one
Jan 12 22:26:12 <jow_laptop> full root maybe
Jan 12 22:27:06 <dadada> how does it make sense, isn't a mmc device basically just like an usb stick in different clothing?
Jan 12 22:27:52 <jow_laptop> not if you use it with extroot
Jan 12 22:28:21 <dadada> yeah, but I assume that usb stick as extroot works...
Jan 12 22:29:26 <jow_laptop> did you copy and *.ko files to your mmc fs?
Jan 12 22:29:35 <jow_laptop> that will break it for sure
Jan 12 22:30:06 <dadada> only the files from /overlay
Jan 12 22:30:18 <dadada> as in only the addon stuff
Jan 12 22:30:33 <jow_laptop> I don't know what was in your /overlay
Jan 12 22:30:57 <dadada> iptables wasn't in it, and now it complains about missing symbols for iptables and nat
Jan 12 22:31:01 <dadada> for example
Jan 12 22:31:15 <jow_laptop> so did you copy any *.ko files?
Jan 12 22:31:19 <dadada> but when you go to /lib/... you find them all
Jan 12 22:31:39 <dadada> jow_laptop: yes, the stuff that I installed with opkg install like kmod-sound-core
Jan 12 22:31:57 <jow_laptop> yeah, thats whats breaking it
Jan 12 22:32:04 <dadada> I just did it like in the wiki for extroot where you copy /overlay to /newoverlay
Jan 12 22:32:08 <jow_laptop> some odd xattr/overlayfs/whiteout issue
Jan 12 22:32:39 <jow_laptop> what filesystem did you put on the mmc?
Jan 12 22:32:44 <dadada> ext4
Jan 12 22:36:14 <jow_laptop> if you do  ls -l /lib/modules/  , does it look normal?
Jan 12 22:37:47 <dadada> root@OpenWrt:~# ls -l /lib/modules
Jan 12 22:37:47 <dadada> drwxr-xr-x    1 root     root             0 Jan 12 19:03 2.6.39.4
Jan 12 22:37:54 <dadada> it does to me
Jan 12 22:38:23 <jow_laptop> oops, I mean including the version subdirectory of course
Jan 12 22:40:29 <dadada> ok, wait... I'll lose internet again, as long as I test this..
Jan 12 22:40:32 <dadada> brb
Jan 12 22:51:38 <dadada> jow_laptop: http://pastebin.com/JRPpB0WY
Jan 12 22:51:40 <dadada> looks normal
Jan 12 22:52:29 <jow_laptop> nf_conntrack.ko is missing
Jan 12 22:52:45 <jow_laptop> others too
Jan 12 22:53:09 <jow_laptop> I bet if you do  ls /lib/modules/2.6.39.4/nf_conntrack.ko it is accessible
Jan 12 22:53:12 <dadada> ok, don't know enough about that
Jan 12 22:53:16 <jow_laptop> but not part of the listing
Jan 12 22:53:26 <dadada> yeah, wait, brb
Jan 12 22:53:27 <jow_laptop> which is exactly one symtom of the overlfs bug
Jan 12 22:53:43 <jow_laptop> while you're at it, please make a full recursive listing of /overlay
Jan 12 22:58:18 <dadada> jow_laptop: you were on the money
Jan 12 22:58:35 <dadada> ls -l /lib/modules/2.6.39.4/nf_conntrack.ko
Jan 12 22:58:36 <dadada> -rw-r--r--    1 root     root         59212 Jan  9  2012 /lib/modules/2.6.39.4/nf_conntrack.ko
Jan 12 22:58:46 <dadada> http://pastebin.com/5NE84c4E
Jan 12 22:59:22 <jow_laptop> interesting
Jan 12 22:59:41 <jow_laptop> the intersection between overlay files, missing files and visible files seems random
Jan 12 23:00:05 <dadada> in IT nothing really is random ...
Jan 12 23:01:10 <jow_laptop> yeah true, its probably some off-by-one or another funny issue in overlayfs
Jan 12 23:01:22 <dadada> didn't you think it's strange that the files of nf_conntrack_* were there?
Jan 12 23:01:39 <dadada> I mean, it looks like the "_" and the "similar" names were the issue
Jan 12 23:01:52 <dadada> maybe also the name length?
Jan 12 23:02:46 <dadada> do you see any other files missing?
Jan 12 23:04:15 <jow_laptop> http://pastebin.com/ML23KZmZ
Jan 12 23:04:53 <jow_laptop> ignore line 32, that was a sed fail
Jan 12 23:06:09 <dadada> not sure how to read this
Jan 12 23:06:30 <jow_laptop> gree are files in /rom but not /overlay
Jan 12 23:06:40 <jow_laptop> red are files in /overlay but not /rom
Jan 12 23:06:46 <jow_laptop> grey are in both
Jan 12 23:08:44 <dadada> I only see green and black, but I may be color blind
Jan 12 23:09:04 <jow_laptop> line 61 and 63
Jan 12 23:09:35 <dadada> ok
Jan 12 23:09:49 <dadada> but there's no problem when a file is only in one of both
Jan 12 23:10:01 <dadada> as long as the right files are in /
Jan 12 23:10:35 <dadada> so far I see this nf_conntrack.ko is clearly missing from the list using *
Jan 12 23:10:48 <dadada> it's a strange issue
Jan 12 23:11:04 <dadada> who's working on overlayfs?
Jan 12 23:11:21 <jow_laptop> nobody
Jan 12 23:11:35 <jow_laptop> thats one of the reasons why it is still broken :)
Jan 12 23:11:43 <jow_laptop> I mean nobody is working on it in openwrt
Jan 12 23:11:45 <dadada> not nice
Jan 12 23:12:07 <dadada> do similar issues appear with non-mmc devices?
Jan 12 23:12:12 <jow_laptop> yes
Jan 12 23:12:34 <dadada> is overlayfs in linus-kernel?
Jan 12 23:12:48 <KanjiMonster> dadada: no, not yet
Jan 12 23:13:12 <KanjiMonster> ETA unknown -> https://lkml.org/lkml/2011/8/4/348
Jan 12 23:13:41 <jow_laptop> is our patchset still the most recent?
Jan 12 23:13:54 <jow_laptop> last time I wanted to look into it the kernel.org git was down
Jan 12 23:13:55 <KanjiMonster> jow_laptop: no
Jan 12 23:14:13 <jow_laptop> maybe we should simply upgrade then and it'd be already solved
Jan 12 23:14:20 <jow_laptop> apparently there is a reliable testcase
Jan 12 23:15:27 <dadada> that would be me? :-)
Jan 12 23:15:45 <jow_laptop> well forums are full with similar reports too, and there are tickets on it as well
Jan 12 23:15:46 <KanjiMonster> jow_laptop: I can test how far I can update it; the last time I tried I failed for 2.6.37 since v10 required some fs RCU changes that were only present in 2.6.38+
Jan 12 23:16:28 <dadada> KanjiMonster: according to your post there's at least v11 and this was 4 months ago
Jan 12 23:18:10 <KanjiMonster> dadada: current is v12 (-> http://lwn.net/Articles/473217/ resp. http://git.kernel.org/?p=linux/kernel/git/mszeredi/vfs.git)
Jan 12 23:19:54 <dadada> there was a fix for overlayfs over overlayfs :-)
Jan 12 23:19:58 <dadada> that might be the problem
Jan 12 23:20:36 <KanjiMonster> oh, indeed, that sounds like a plausible one
Jan 12 23:20:59 <dadada> yeah
Jan 12 23:21:08 <dadada> which version are we using anyways?
Jan 12 23:24:47 <builder_> build #87 of mpc52xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/87
Jan 12 23:27:21 <dadada> who is responsible for overlayfs in openwrt, or is it THE team?
Jan 12 23:28:40 <KanjiMonster> dadada: there is no clear responsibility, so it's the team
Jan 12 23:28:56 <dadada> ok, GO TEAM GO TEAM ;-)
Jan 12 23:28:58 <KanjiMonster> usually whoever touched it last is "it" ;)
Jan 12 23:29:28 <dadada> heh
Jan 12 23:32:49 <dadada> KanjiMonster: 1) download sources 2) merge 3) compile 4) patch 3) 5) success??!
Jan 12 23:34:53 <KanjiMonster> dadada: for 2.6.37 it was for me ... 2) merge 3) fail to compile 4) notice that it depends on fs locking/api changes 5) try to work around it 6) try more 7) ??? 8) profit
Jan 12 23:35:30 <KanjiMonster> but maybe v12 is a bit more coorparative to 2.6.38+
Jan 12 23:35:51 <dadada> see, there's profit at the end.. should be motivating ;-)
Jan 12 23:36:10 <KanjiMonster> yeah, but there is also the big "???" ;)
Jan 12 23:36:20 <dadada> it's the challenge
Jan 12 23:36:27 <dadada> the great one
Jan 12 23:37:29 <builder_> build #126 of s3c24xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/s3c24xx/builds/126
Jan 12 23:40:59 <builder_> build #130 of brcm63xx is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/130
Jan 12 23:41:10 <builder_> build #84 of octeon is complete: Failure [failed compile_6]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/84
Jan 12 23:42:00 <nbd> profit is what happens by itself when not thinking about it ;)
Jan 12 23:42:20 <dadada> :-)
Jan 12 23:42:22 <dadada> good night
Jan 12 23:56:27 <builder_> build #123 of ubicom32 is complete: Failure [failed compile_3]  Build details are at http://buildbot.openwrt.org:8010/builders/ubicom32/builds/123
Jan 13 00:10:06 <Chocks> fullstop: poke
Jan 13 00:16:59 <Chocks> nbd: pong
Jan 13 00:19:16 <builder_> build #125 of at91 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/125
Jan 13 00:54:35 <CIA-84> jow * r29723 /trunk/package/iwinfo/ (Makefile src/iwinfo_nl80211.c): [package] iwinfo: plug memory leak in nl80211 backend, nl80211_close() did not put the family pointer
**** ENDING LOGGING AT Fri Jan 13 02:59:57 2012