**** BEGIN LOGGING AT Tue Dec 25 02:59:58 2012
Dec 25 14:02:50 <builder_> build #97 of iop32x is complete: Failure [failed shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/97
Dec 25 14:05:23 <builder_> build #94 of gemini is complete: Failure [failed shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/94
Dec 25 15:21:24 <builder_> build #131 of orion is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/131
Dec 25 15:25:37 <builder_> build #89 of octeon is complete: Failure [failed shell shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/89
Dec 25 16:06:34 <dkostousov> I have posted a photo of DIR-615 k2 entry. https://kst-d.net/wiki/dir-615-k2
Dec 25 18:46:23 <OpenWrt-Commits> juhosg r34880 trunk/target/linux/ar71xx/files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c * ar71xx: ag71xx: show PHY interface mode in dmesg
Dec 25 18:46:24 <OpenWrt-Commits> juhosg r34881 trunk/target/linux/ generic/files/drivers/net/phy/ar8216.c generic/files/include/linux/ar8216_platform.h generic/files/drivers/net/phy/ar8216.h * generic: ar8216: add sgmii_delay_en field to ar8327_platform_data
Dec 25 18:46:25 <OpenWrt-Commits> juhosg r34882 trunk/target/linux/ar71xx/patches-3.6/609-MIPS-ath79-ap136-fixes.patch * ar71xx: dynamically set AR8327's PAD configuration on AP136
Dec 26 02:03:24 <isuldor> is network routing (nat) always done in software? or is there an openwrt device profile that includes hardware nat acceleration?
**** ENDING LOGGING AT Wed Dec 26 02:59:59 2012