**** BEGIN LOGGING AT Sat Sep 07 02:59:59 2013
Sep 07 05:09:44 <builder> build #248 of octeon is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/248
Sep 07 08:36:53 <quackquack> how to enable both the cores in broadcom 6358?
Sep 07 08:41:58 <quackquack> has anyone here enabled both the cores of bcm6358?
Sep 07 08:42:08 <quackquack> if so can i get some help?
Sep 07 09:10:27 <KanjiMonster> quackquack: enabling both cores will crash the system as it has certain quirks that require additional code to work around
Sep 07 09:11:12 <quackquack> oh
Sep 07 09:11:50 <quackquack> wiki.openwrt.org/doc/hardware/soc/soc.broadcom.bcm63xx/smp
Sep 07 09:12:12 <quackquack> i was hopeful seeing this wiki entry i will have both the cores.
Sep 07 09:12:27 <quackquack> no profit, KanjiMonster ;-)
Sep 07 09:13:01 <KanjiMonster> quackquack: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/mips/bcm63xx/prom.c#n66
Sep 07 09:14:06 <quackquack> aah
Sep 07 09:14:09 <quackquack> i see
Sep 07 09:14:35 <quackquack> so in future we will have both the cores enabled. i hope.
Sep 07 11:10:02 <russell--> hmm. /me seeing openvpn problems on r37911, but only on wgt634u, not alix2 or wzr600dhp
Sep 07 11:16:28 <russell--> trying polarssl instead of openssl
Sep 07 11:25:35 <russell--> hmm, with polarssl it works
Sep 07 11:25:50 <russell--> didn't have this problem on ar71xx or x86
Sep 07 11:34:47 <OpenWrt-Commits> juhosg r37912 trunk/target/linux/ppc40x/ (9 files in 2 dirs) * ppc40x: add support for 3.10
Sep 07 11:34:49 <OpenWrt-Commits> juhosg r37913 trunk/target/linux/ppc40x/Makefile * ppc40x: switch to 3.10
Sep 07 11:34:51 <OpenWrt-Commits> juhosg r37914 trunk/target/linux/ppc40x/ patches-3.8 config-3.8 * ppc40x: remove 3.8 support
Sep 07 11:37:53 <Hauke> russell--: are you using the ssb security module?
Sep 07 11:41:28 <OpenWrt-Commits> juhosg r37915 trunk/target/linux/ar71xx/image/Makefile * ar71xx: use the lzma loader for the WRT160NL
Sep 07 12:23:17 <builder> build #342 of rb532 is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/342
Sep 07 12:25:35 <builder> build #342 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/342
Sep 07 13:15:43 <builder> build #355 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/355
Sep 07 13:26:01 <builder> build #323 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/323
Sep 07 14:13:31 <Devastator> can anyone tell the steps after refreshing a patch? would be something like this? "git commit", then "git format-patch -s --stdout master > ~/mypatch.patch" and "git send-email mypatch.patch"
Sep 07 14:15:43 <strasidlo> yes, byt all user git variables should be correctly set (to send an email and correctly sign the patch)
Sep 07 14:17:46 <Devastator> ok, I guess .gitconfig is properly setup
Sep 07 14:17:55 <Devastator> I was unsure about the steps
Sep 07 14:22:51 <Devastator> now I wonder, should I wait for luka's blessing on doing it, who helped me together with jogo, since the beginning or should I do it already?
Sep 07 14:31:17 <strasidlo> Devastator: I would send the patch to mailing list with CC to luka and jogo
Sep 07 14:31:43 <strasidlo> you can send a newer revision whenever you want
Sep 07 14:31:54 <Devastator> that's true
Sep 07 14:37:25 <KanjiMonster> Devastator: git format-patch --subject="PATCH V2" ... (or V<something>); also edit mypatch.patch and put your changes from the previous version(s) under the tear-off line ("---"), so they don't appear in the actual commit log
Sep 07 14:37:57 <Devastator> will do, already editing :)
Sep 07 14:38:21 <Devastator> thanks guys
Sep 07 15:07:45 <Devastator> is this considered a refreshed patch? http://codepad.org/ZJz7TKZk
Sep 07 15:09:20 <strasidlo> Devastator: I think so, but there is no need to be repetitive - I would delete the 6th line
Sep 07 15:10:03 <Devastator> alright!
Sep 07 15:18:00 <strasidlo> nbd: ping
Sep 07 15:20:15 <nbd> strasidlo: pong
Sep 07 15:20:31 <strasidlo> do you still maintain x86 target?
Sep 07 15:22:30 <strasidlo> I think there is something wrong with preinit (which causes sysupgrade issue - #14088 ). I do not know who to contact to solve that problem.
Sep 07 15:23:26 <nbd> i'm not actively working on x86
Sep 07 15:23:56 <Devastator> strasidlo sorry to keep bothering you, but can I send the patch to you to see if it applies before sending to the mailing list? I'm afraid I've made a git mistake and if it doesn't apply I will start over
Sep 07 15:25:06 <strasidlo> Devastator: yes, you can. send it to slachta<at>cesnet<dot>cz
Sep 07 15:25:12 <strasidlo> I
Sep 07 15:25:18 <Devastator> thanks!
Sep 07 15:25:21 <strasidlo> I will try if that works
Sep 07 15:26:07 <strasidlo> nbd: and is there anyone who maintains this target?
Sep 07 15:31:26 <strasidlo> Devastator: I am going off. I will respond to your email as soon as possible.
Sep 07 15:31:44 <Devastator> strasidlo thank you so much
Sep 07 15:31:50 <Devastator> have a nice weekend :)
Sep 07 15:33:03 <strasidlo> nice weekend to you too!
Sep 07 15:33:28 <Devastator> KanjiMonster iirc, you are a broadcom maintainer, correct?
Sep 07 15:41:31 <KanjiMonster> Devastator: yeah; bcm63xx it is
Sep 07 15:42:16 <Devastator> KanjiMonster bcm4875 is bcm47xx, right?
Sep 07 15:42:35 <KanjiMonster> Devastator: 4785, yes.
Sep 07 15:43:08 <Devastator> KanjiMonster and do you know who maintain bcm47xx?
Sep 07 15:43:20 <KanjiMonster> Hauke does
Sep 07 15:43:33 <Devastator> thanks!
Sep 07 15:43:52 <Hauke> Devastator: problems?
Sep 07 15:44:32 <KanjiMonster> Hauke: maybe you should add yourself as maintainer in https://dev.openwrt.org/browser/trunk/target/linux/brcm47xx/Makefile ;)
Sep 07 15:44:57 <Devastator> Hauke not at all, but I've never used openwrt on bcm47xx yet, I'm considering porting Linksys WRT310N, bcm47xx with 32mb of ram and I
Sep 07 15:45:07 <Devastator> and I've modified its flashchip to 8mb
Sep 07 15:45:09 <Hauke> KanjiMonster: good idea
Sep 07 15:45:30 <KanjiMonster> not that I'm in bcm63xx; but that one has at least [florian].
Sep 07 15:45:58 <Devastator> last time I tried, which was a *long* time ago, didn't work well
Sep 07 15:46:21 <Devastator> now I am more familiarized with openwrt I guess and I think it
Sep 07 15:46:34 <Devastator> and I think it is a good unit for testing, no?
Sep 07 15:47:10 <OpenWrt-Commits> hauke r37916 trunk/target/linux/brcm47xx/Makefile * brcm47xx: add me as maintainer
Sep 07 15:48:12 <Hauke> Devastator: wifi will not work very well, with the propertary driver you will get 80211n speeds and with b43 you will get 80211g speeds
Sep 07 15:48:43 <Hauke> it could be that the switch is not working, but if you have a serial connected could help you to fix the problem
Sep 07 15:51:24 <builder> build #333 of avr32 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/333
Sep 07 16:03:46 <Devastator> Hauke yes, I can work with you on that, if it helps solving anything
Sep 07 16:04:23 <Devastator> Hauke I was curious about how porting this router could be helpful for the project itself
Sep 07 16:04:55 <Devastator> because if it can't contribute much, I don't think it worth..
Sep 07 16:05:44 <Hauke> my device with a bcm4785 is currently broken :-(
Sep 07 16:07:18 <Devastator> Hauke can it help testing the ssb thing I've seen in mailing list?
Sep 07 16:07:43 <Hauke> Devastator: everything should be in trunk
Sep 07 16:08:40 <Devastator> I was referring to Rafael Milecki patch about SSB bus support
Sep 07 16:10:23 <Devastator> Rafal
Sep 07 16:12:11 <Hauke> this is for serial flash support, I only know of one device with ssb and serial flash
Sep 07 16:13:57 <Devastator> hum, not my case I guess
Sep 07 16:17:13 <Devastator> let's get to work then, downloading gpl code
Sep 07 17:36:05 <Devastator> Hauke do you think it will take a long to broadcom to dump closed sources drivers?
Sep 07 18:07:13 <Hauke> Devastator: what do you want to do?
Sep 07 18:33:50 <OpenWrt-Commits> nbd r37917 trunk/tools/ cmake/patches/100-disable_qt_tests.patch cmake/patches * tools/cmake: disable qt related checks to fix build issues
Sep 07 18:48:19 <Devastator> Hauke sorry, had to leave for a few minutes.. well, I'm going to try porting this router and help with openwrt development by testing builds on it
Sep 07 18:49:00 <Devastator> wiki seems to have a guide on how to port broadcom routers, iirc
Sep 07 18:49:42 <Hauke> Devastator: OpenWrt should work on the WRT310N
Sep 07 18:51:28 <Devastator> my question about the propertary drivers was because Broadcom seem to have decided to use opensource drivers now, no? iirc, these opensource drivers are for sta only
Sep 07 19:53:47 <russell--> Hauke: i think so
Sep 07 20:57:28 * russell-- assumes NSA-crippled crypto engine is not working properly
Sep 08 01:05:18 <builder> build #283 of ep93xx is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/283
**** ENDING LOGGING AT Sun Sep 08 02:59:59 2013