**** BEGIN LOGGING AT Thu Jan 02 02:59:58 2014
Jan 02 03:30:20 <builder> build #415 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/415
Jan 02 05:35:47 <builder> build #457 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/457
Jan 02 05:40:22 <builder> build #425 of avr32 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/425
Jan 02 05:53:03 <builder> build #472 of ramips is complete: Failure [failed shell_14]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/472
Jan 02 06:30:48 <builder> build #45 of mxs is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/45
Jan 02 08:04:30 <builder> build #363 of iop32x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/363
Jan 02 10:49:09 <zajec> nbd: i have no idea there is anything going on to work with DD-WRT
Jan 02 10:49:14 <zajec> nbd: sounds interesting :)
Jan 02 11:02:49 <blogic> zajec: so oyu just saw the talk ? :)
Jan 02 11:07:47 <zajec> blogic: :)
Jan 02 11:08:50 <zajec> blogic: too bad it wasn't in Berlin
Jan 02 11:09:05 <zajec> blogic: Berlin is so close to me, I could driver morning and even get back to home evening
Jan 02 11:09:08 <blogic> it was a good talk
Jan 02 11:09:12 <zajec> blogic: a bit over 300km from Poznan
Jan 02 11:09:20 <zajec> blogic: but at least it was recorded :)
Jan 02 11:10:12 <zajec> blogic: and they whole idea sounds pretty sane... i don't see why DD-WRT couldn't be based on OpenWrt now
Jan 02 11:10:23 <zajec> apart from ARM device ofc
Jan 02 11:14:31 <builder> build #46 of mvebu is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/46
Jan 02 11:41:09 <OpenWrt-Commits> cyrus r39184 trunk/package/network/ ipv6/6relayd/files/6relayd.init ipv6/6relayd/Makefile * 6relayd: try to workaround race condition at startup
Jan 02 11:42:53 <builder> build #446 of x86 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/446
Jan 02 11:57:47 <OpenWrt-Commits> jow r39185 trunk/package/ utils/jsonpath utils/jsonpath/Makefile
Jan 02 11:57:47 <OpenWrt-Commits> Add jsonpath - a command line utility to extract values from JSON data using XPath-like expressions
Jan 02 12:16:31 <Devastator> zajec please, don't tell me dd-wrt is going to infect the pureness of openwrt :(
Jan 02 12:22:29 <KanjiMonster> Devastator: without having heard the talk yet, I think it's the other way round; openwrt's pureness could infect/improve dd-wrt ;)
Jan 02 12:22:58 <Devastator> KanjiMonster heheh, improve, sure
Jan 02 12:23:44 <Devastator> I'm just afraid of a merge and have a "single" 3rd party firmware with ugly hacks as you know
Jan 02 12:24:07 <jow_laptop> its unlikely to happen
Jan 02 12:24:44 <Devastator> jow_laptop thanks, I guess I can sleep normally tonight
Jan 02 12:27:36 <Devastator> the only good thing I can think about dd-wrt is their access to broadcom source and is not that good after all, because broadcom itself isn't that good
Jan 02 12:33:16 <zajec> Devastator: i guess DD-WRT will just take OpenWrt and add Broadcom binaries for wireless
Jan 02 12:33:20 <zajec> i can't imagine anything else
Jan 02 12:33:39 <zajec> why should they use Broadcom's kernel with flash driver, partitioner, etc.?
Jan 02 12:33:54 <jow_laptop> well dd-wrt's biggest feature is its ui
Jan 02 12:34:24 <jow_laptop> which in turn is interleaved with the nvram and broadcom specific library mess inherited from the old original sdks
Jan 02 12:34:31 <zajec> Devastator: http://media.ccc.de/browse/congress/2013/30C3_-_5497_-_en_-_saal_g_-_201312271400_-_10_years_of_fun_with_embedded_devices_-_nbd.html
Jan 02 12:34:34 <zajec> Devastator: 0:44:32
Jan 02 12:34:37 <jow_laptop> if they want to base it on openwrt they need to rewrite most stuff
Jan 02 12:35:17 <Devastator> I agree dd-wrt is more "friendly", but even without using luci I can say it has a much cleaner code
Jan 02 12:35:24 <jow_laptop> or simply take the kernel and keep the messy userspace
Jan 02 12:35:42 <jow_laptop> but they'll hit some hard limits with their architecture at some point
Jan 02 12:39:48 <Devastator> well, I've discussed it with BrainSlayer several times and he said he wanted to support as many devices as he could
Jan 02 12:40:11 <Devastator> my personal opinion is to support less devices, but support with quality
Jan 02 12:40:13 <jow_laptop> yes, and he can do this by staying close to the sdk
Jan 02 12:40:28 <jow_laptop> which on the other hand prevents him from having a clean, sane architecture
Jan 02 12:40:38 <Devastator> exactly
Jan 02 12:40:53 <Devastator> by sdk I guess you mean broadcom's sdk?!
Jan 02 12:41:07 <jow_laptop> broadcoms, ralinks, ...
Jan 02 12:41:50 <Devastator> I can only speak for broadcoms, my first ralink I touched I ported to openwrt as you might have seen
Jan 02 12:42:10 <Devastator> excuse me for saying this but.. what a shitty sdk broadcom have
Jan 02 12:42:56 <Devastator> sometimes I don't know if I can blame BrainSlayer for dd-wrt mess buildroot or broadcom sdk
Jan 02 13:44:10 <Devastatr> zajec thanks for the link of the video
Jan 02 13:44:48 <Devastatr> if Felix can convince Sebastian to use openwrt and stop hacking, he will be my new hero, really :)
Jan 02 13:46:16 <zajec> :)
Jan 02 13:49:04 <Devastatr> to make myself clear, I'm not against hacks, but only for testing an idea, a concept, not in mainline
Jan 02 13:50:44 <Devastatr> I wish netgear started using openwrt, their mtd layouts are crazy
Jan 02 13:51:16 <Devastatr> "let's put our cfe in the middle of root partition"
Jan 02 13:51:31 <Devastatr> "why?" "because it's fun!"
Jan 02 13:51:38 <jow_laptop> :D
Jan 02 13:51:45 <builder> build #402 of kirkwood is complete: Failure [failed shell_14]  Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/402
Jan 02 14:31:54 <Pteridium> There is any way to reconfigure the rgmii port in rt3052 to RevMII?
Jan 02 14:32:08 <Pteridium> the board is the Alpha ASL26555
Jan 02 14:33:24 <Pteridium> i want to communicate with the Trendchip to test a couple of things
Jan 02 14:34:21 <blogic> let me have a look
Jan 02 14:34:25 <blogic> ah
Jan 02 14:34:32 <Pteridium> thanks
Jan 02 14:34:34 <blogic> rt305x has no mdio or gmii support
Jan 02 14:34:39 <blogic> well the chip does
Jan 02 14:34:51 <blogic> but the driver will need wuite a bit of work to make that happen i think
Jan 02 14:35:25 <Pteridium> can it be done with swconfig?
Jan 02 14:36:21 <Pteridium> or any other util
Jan 02 14:40:48 <Pteridium> blogic: this is the u-boot line: ASIC 3052_MP2 (Port5<->RvMII)
Jan 02 14:41:37 <Pteridium> but not sure if port5 is attached to the Trendchip
Jan 02 14:45:22 <blogic> yes
Jan 02 14:45:44 <blogic> but gmac1 nees to be configured
Jan 02 14:45:45 <Pteridium> good
Jan 02 14:46:41 <Pteridium> gmac1=port5, no?
Jan 02 14:48:19 <blogic> i think so
Jan 02 14:48:40 <Pteridium> can be passed to the dts file something like this?
Jan 02 14:48:41 <Pteridium> 		port@5 {
Jan 02 14:48:41 <Pteridium> 			compatible = "swconfig,port";
Jan 02 14:48:41 <Pteridium> 			phy-mode = "rmii";
Jan 02 15:17:52 <builder_> build #392 of au1000 is complete: Failure [failed shell_14]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/392
Jan 02 15:20:15 <Pteridium> blogic: another thing; i've tried to load openwrt from BRN-Boot with an arv4518 but had problems with jffs2
Jan 02 15:20:50 <Pteridium> but with a ram image there are no problems
Jan 02 15:21:30 <blogic> can you mount root from the ram imae manulaly ?
Jan 02 15:21:42 <Pteridium> so, for newbies that want to burn the 2010.03 uboot, it is enough
Jan 02 15:21:49 <Pteridium> didn't tried
Jan 02 15:23:14 <Pteridium> and i think that the old uboot is enough for the old danube routers with 4MB flash
Jan 02 15:26:21 <Pteridium> i'll made some more tests with brnboot. i'll give you the feedback i something changes
Jan 02 15:26:55 <Pteridium> but, as i said, u-boot is the best and safest optionn i think
Jan 02 15:27:13 <Pteridium> thanks for your time
Jan 02 15:27:23 <Pteridium> happy new year!
Jan 02 15:51:35 <Devastator> I love power outages..
Jan 02 16:23:06 <DonkeyHotei> blogic: is there an ETA on the wifi eeprom patch?
Jan 02 16:26:49 * Devastator hides
Jan 02 16:26:57 <Devastator> incoming!
Jan 02 20:49:37 <builder_> build #472 of lantiq is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/472
Jan 02 21:35:09 <builder_> build #349 of gemini is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/349
Jan 02 22:33:56 <builder_> build #480 of atheros is complete: Failure [failed shell_19]  Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/480
Jan 02 22:58:32 <builder_> build #356 of adm5120 is complete: Failure [failed shell_14]  Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/356
Jan 02 23:36:16 <builder_> build #446 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/446
Jan 02 23:39:27 <builder_> build #446 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/446
Jan 03 00:35:33 <builder_> build #489 of brcm47xx is complete: Failure [failed shell_14]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/489
Jan 03 01:40:05 <builder_> build #416 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/416
**** ENDING LOGGING AT Fri Jan 03 02:59:58 2014