**** BEGIN LOGGING AT Tue Aug 26 02:59:58 2014 Aug 26 03:14:21 build #713 of orion is complete: Failure [failed compile_7] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/713 Aug 26 03:19:33 build #167 of x86_64 is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/x86_64/builds/167 Aug 26 03:22:38 build #572 of iop32x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/572 Aug 26 03:32:35 build #667 of ar7 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/667 Aug 26 04:03:00 build #715 of atheros is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/715 Aug 26 04:32:58 build #619 of kirkwood is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/619 Aug 26 04:53:11 build #67 of brcm47xx.mips74k is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.mips74k/builds/67 Aug 26 05:54:08 build #254 of mvebu is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/254 Aug 26 05:59:14 KanjiMonster: did you have a moment to grab E2000 boot log? Aug 26 06:52:20 build #520 of octeon is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/520 Aug 26 07:02:44 hi guys :) Aug 26 07:03:07 someone has familiar with platform at91? Aug 26 07:28:55 Swalker: whoops. Thanks for letting me know. Aug 26 08:26:55 zajec: http://pastebin.com/uakLtFPS Aug 26 08:40:10 blogic r42298 trunk/package/ utils/usbmode/Makefile utils/usbmode/data utils/usbmode/data/12d1:1f16 * usbmode: update to latest git Aug 26 08:42:54 cyrusff, ping Aug 26 08:43:41 cyrusff, there is pull request for fixing CVE for pulseaudio. I did not know that the open CVE is also for barrier-breaker. Could you merge that pull request for trunk and for release branch? Aug 26 09:15:33 KanjiMonster: thx Aug 26 09:17:43 slachta: done Aug 26 09:17:51 swalker: fixed Aug 26 09:37:12 blogic r42299 trunk/package/network/utils/umbim/Makefile * umbim: update to latest git Aug 26 09:47:19 cyrusff, thank you so much for merging. You're the best. ;-) Aug 26 09:47:31 slachta: haha you're welcome Aug 26 10:58:23 when i add support for sth.. - should the patches be contributed for trunk in the first place? i've made a patchset based on BB - guess thats not the way it has to be done...? Aug 26 11:05:13 N3ph: rebase onto trunk and git-send-email to the devel-ml please Aug 26 11:05:38 If its non-core packages please do a pull request on github Aug 26 11:07:40 nope - its a new model for ar71xx - okay - will do it that way again.. thx Aug 26 12:16:07 nbd r42300 trunk/rules.mk * build: override hardcoded paths to bison and m4 to make the SDK more relocatable Aug 26 12:16:32 nbd r42301 branches/barrier_breaker/rules.mk * build: override hardcoded paths to bison and m4 to make the SDK more relocatable Aug 26 12:33:05 nbd r42302 trunk/target/toolchain/Makefile * target/toolchain: strip files, leave out the initial gcc Aug 26 12:33:29 nbd r42303 branches/barrier_breaker/target/toolchain/Makefile * target/toolchain: strip files, leave out the initial gcc Aug 26 13:12:16 blogic r42304 trunk/package/kernel/linux/modules/usb.mk * kernel: add package for huawei ncm modems Aug 26 13:12:26 blogic r42305 trunk/target/linux/ramips/Makefile * ralink: set 3.14 as default Aug 26 14:20:03 Hi all. Quick question: What's the proper subject line to use when re-submitting a patch to the mailing list? I see a couple of "[PATCH RESEND]" Aug 26 16:20:55 :-/ meh - brainfart - the first one supplied via git send-email is still for BB - sry Aug 26 16:22:41 second one is for trunk Aug 26 16:48:16 is 3.14.11 the latest kernel which builds successfully? Aug 26 16:52:27 hm - also this version doesn't build.. Aug 26 16:52:28 fs/yaffs2/yaffs_mtdif.c: In function 'yaffs_get_mtd_device': Aug 26 16:52:28 fs/yaffs2/yaffs_mtdif.c:256:21: error: 'MTD_BLOCK_MAJOR' undeclared (first use in this function) Aug 26 17:43:18 build #668 of ppc44x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/668 Aug 26 18:42:59 build #274 of imx6 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/274 Aug 26 18:49:11 build #699 of ramips is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/699 Aug 26 18:51:10 build #52 of ramips.rt3883 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/52 Aug 26 18:52:04 build #637 of sibyte is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/637 Aug 26 19:17:44 build #679 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/679 Aug 26 19:40:37 hERRO Aug 26 19:48:14 build #649 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/649 Aug 26 19:52:10 Is there anyone here?? Aug 26 19:52:31 nope Aug 26 19:52:36 I'm new to this, but I want to get a working boot for BCM63xx Aug 26 19:52:38 sorry Aug 26 19:52:51 as far as I know, there is missing MTD drivers Aug 26 19:52:56 see https://dev.openwrt.org/wiki/brcm63xx Aug 26 19:53:14 But I came accross this: https://github.com/linux-pmfs/pmfs/blob/master/drivers/mtd/bcm63xxpart.c - would this driver even work? Aug 26 19:53:45 Edit, use this URL instead, newer (3.16) http://lxr.free-electrons.com/source/drivers/mtd/bcm63xxpart.c Aug 26 19:53:54 sorry i have no experience with bcm63xx Aug 26 19:54:17 heffer, you know how drivers work in general then? Aug 26 19:54:57 a little bit, yes Aug 26 19:57:32 ColdIce: this is only a partition/image tag parser, but not a mtd flash driver Aug 26 19:59:19 Thx KanjiMonster! Aug 26 20:01:25 ColdIce: for nor flash, bcm63xx uses "generic" drivers; that is physmap for parallel flash, and m25p80 on top of spi for spi-nor flash Aug 26 20:03:09 ColdIce: you should probably start by making a kernel boot over network; if you have serial attached, you can tell cfe to boot an elf kernel from network Aug 26 20:04:04 I got serial cached yes, it supports multiboot. It's a looked bootloader, but I've opened it (thx ZynPass). So I could boot from network? Oo Aug 26 20:04:22 So I build bootloader then boot from network? :S Aug 26 20:04:40 ColdIce: assuming it is CFE based Aug 26 20:05:03 then you can 'c' change boot parameters and change it to boot from 'h' host instead of 'f' flash Aug 26 20:05:25 It is Aug 26 20:07:10 it will then try to load the "default host run file name" from the "host ip address" using tftp, and boot that Aug 26 20:07:52 you need to select "initramfs" as the image type in openwrt to make it create a suitable elf kernel Aug 26 20:15:36 KanjiMonster, I don't see anything about boot paramters? Aug 26 20:15:42 I see xmodem thing... Aug 26 20:16:06 ah, found it! ATIP (run from flash / host) Aug 26 20:34:41 Oh I see KanjiMonster, you are responsible for BCM63xx, rigtht? Aug 26 20:38:50 ColdIce: partially. Aug 26 20:43:11 KanjiMonster, I have no idea of what I'm doing, but somehow I want to build an booting image :S Aug 26 20:44:48 ColdIce: you are chosing the hardest device to start with; a) unsupported flash type, and b) heavily modified bootloader ;) Aug 26 20:47:22 Hehe, gotta start somewhere. this is what I have.... Aug 26 20:50:30 I started my OpenWRT career about the same way Aug 26 20:51:13 first project was with unsupported flash and encrypted firmware upater, second project broke the switch in modified u-boot Aug 26 20:51:31 but both devices are now supported in BB :D Aug 26 20:54:49 KanjiMonster, I have the source code, I found my board-ID in boardparms.c Aug 26 20:54:55 am I good to go yet? :D Aug 26 21:00:56 ColdIce: not really, you still have a lot of hurdles to jump over ;) Aug 26 21:01:18 ColdIce: first you should get the bootloader to load a kernel through tftp Aug 26 21:01:57 (it won't boot, but before you get that far hacking on the code is meaningless) Aug 26 21:08:17 and where to I get the kernel? Oo I have no idea Aug 26 21:13:25 ColdIce: you need to build it yourself **** BEGIN LOGGING AT Tue Aug 26 22:33:52 2014 Aug 27 00:11:46 build #714 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/714 Aug 27 01:46:44 build #620 of kirkwood is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/620 Aug 27 02:58:42 build #573 of iop32x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/573 **** ENDING LOGGING AT Wed Aug 27 02:59:58 2014