**** BEGIN LOGGING AT Thu Aug 21 02:59:59 2014 Aug 21 03:45:04 build #62 of brcm47xx.mips74k is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.mips74k/builds/62 Aug 21 03:47:21 build #567 of iop32x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/567 Aug 21 03:52:50 build #720 of brcm47xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/720 Aug 21 03:54:44 build #740 of brcm63xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/740 Aug 21 04:13:34 build #264 of mxs is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/264 Aug 21 04:13:57 build #161 of bcm53xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/161 Aug 21 04:17:57 build #159 of realview is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/realview/builds/159 Aug 21 04:22:53 build #688 of ppc40x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/688 Aug 21 05:10:14 build #698 of lantiq is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/698 Aug 21 05:14:46 build #42 of x86.kvm_guest is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.kvm_guest/builds/42 Aug 21 05:44:22 build #249 of mvebu is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/249 Aug 21 06:41:38 blogic r42232 trunk/target/linux/ramips/dts/OMNI-PLUG.dts * ramips: fix OMNI-PLUG.dts Aug 21 06:58:38 How can I change the permission of the files folder to executable when I build the source code of openwrt? Aug 21 07:01:03 chmod +x Aug 21 07:06:03 or there are INSTALL_BIN / _DIR / _DATA / _CONF that are used in Makefiles of packages that should set permissions (see rules.mk file) Aug 21 07:26:28 build #162 of cns21xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/162 Aug 21 07:55:54 build #703 of cobalt is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/703 Aug 21 08:10:15 build #47 of brcm63xx.smp is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx.smp/builds/47 Aug 21 08:10:56 build #46 of ramips.rt3883 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/46 Aug 21 08:10:58 build #710 of atheros is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/710 Aug 21 08:11:18 build #70 of brcm47xx.legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/70 Aug 21 08:11:22 build #620 of ixp4xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/620 Aug 21 08:42:29 cyrusff: afaik, Luka should be on a vacation with limited access to the Internet. When I get some time I will fix the open CVE issue for nspr package. Aug 21 08:42:37 slachta: thanks Aug 21 08:43:34 shouldn't be too hard just bumping the revision and possibly refreshing patches Aug 21 08:43:39 i hope Aug 21 08:44:28 cyrusff: is it possible to test current BB for the "compilability" on release builders? I would love to know if the telephony repository is compilable on release builders. Aug 21 08:44:57 well you can build it from the bb-branch Aug 21 08:45:45 the only real breakage in the release-builder was with curl Aug 21 08:48:59 one more thing to resolve - I just found out that there is one lantiq target without TAPI subsystem. It causes the breakage of asterisk package on that target, because drv-tapi.h is missing. http://git.openwrt.org/?p=feed/telephony.git;a=blob;f=net/asterisk-1.8.x/Makefile#l264 Aug 21 08:49:33 Should I add ifneq for that target to not to copy the custom lantiq src? Aug 21 08:49:58 (lantiq xrx200) Aug 21 08:51:08 is there a way to invert leds (on ramips) in a configuration? gpio-leds seem to be backwards 1 is off, 0 is on. Aug 21 09:08:25 build #515 of octeon is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/515 Aug 21 09:16:33 build #47 of ar71xx.nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.nand/builds/47 Aug 21 09:26:42 russell--: if the gpio controller allows passing flags; <&gpioX 1> instead of <&gpio 0> (the bit controls active low) Aug 21 09:27:07 err <&gpioX 0> the second example Aug 21 09:53:41 blogic r42233 trunk/package/network/config/firewall/files/firewall.init * firewall: the firewall did not start properly on boot Aug 21 10:03:27 build #635 of xburst is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/635 Aug 21 11:11:45 build #157 of brcm2708 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/157 Aug 21 11:20:41 build #565 of ep93xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/565 Aug 21 11:22:59 build #47 of ar71xx.mikrotik is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.mikrotik/builds/47 Aug 21 11:27:57 jogo r42234 trunk/target/linux/brcm63xx/dts/dsl-274xb-c.dts * brcm63xx: dsl-274xb-c: linux partition should not be read-only Aug 21 11:28:06 jogo r42235 trunk/target/linux/brcm63xx/dts/ bcm6348.dtsi bcm6338.dtsi bcm6345.dtsi * brcm63xx: dts: fix spelling of "bank-width" Aug 21 11:28:11 jogo r42236 trunk/target/linux/brcm63xx/dts/spw500v.dts * brcm63xx: use DT for partitions on SPW500V Aug 21 11:28:19 jogo r42237 trunk/target/linux/ (40 files in 4 dirs) * brcm63xx: Add DT support for CT-5365 Aug 21 11:28:24 jogo r42238 trunk/target/linux/ (28 files in 4 dirs) * brcm63xx: Add DT support for CT-6373 Aug 21 11:28:28 jogo r42239 trunk/target/linux/ (27 files in 4 dirs) * brcm63xx: Add DT support for AR-5381u Aug 21 11:28:38 jogo r42240 trunk/target/linux/ (28 files in 4 dirs) * brcm63xx: Add DT support for AR-5387un Aug 21 11:28:41 jogo r42241 trunk/target/linux/ (9 files in 4 dirs) * brcm63xx: Add DT support for VR-3025u Aug 21 11:28:44 jogo r42242 trunk/target/linux/ (8 files in 4 dirs) * brcm63xx: Add DT support for VR-3025un Aug 21 11:28:47 jogo r42243 trunk/target/linux/ (10 files in 4 dirs) * brcm63xx: Add DT support for WAP-5813n Aug 21 11:28:49 jogo r42244 trunk/target/linux/ (29 files in 4 dirs) * brcm63xx: Add DT support for A4001N1 Aug 21 11:28:53 jogo r42245 trunk/target/linux/ (5 files in 4 dirs) * brcm63xx: Add DT support for A4001N Aug 21 11:28:55 jogo r42246 trunk/target/linux/ (6 files in 4 dirs) * brcm63xx: Add DT support for HG520v Aug 21 11:29:04 jogo r42247 trunk/target/linux/ (41 files in 4 dirs) * brcm63xx: Add DT support for HG553 Aug 21 11:29:09 jogo r42248 trunk/target/linux/ (7 files in 4 dirs) * brcm63xx: Add DT support for P870HW-51a Aug 21 11:29:11 jogo r42249 trunk/package/network/services/dropbear/patches/002-match_keepalive_to_OpenSSH.patch * dropbear: fix keepalive more Aug 21 11:29:14 jogo r42250 trunk/package/network/services/dropbear/Makefile * dropbear: restore performance by disabling mips16 Aug 21 11:33:10 build #734 of at91 is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/734 Aug 21 11:38:43 build #595 of au1000 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/595 Aug 21 11:48:34 wiki back Aug 21 11:55:02 phaidros: thanks! Aug 21 12:03:22 build #156 of mpc83xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/156 Aug 21 12:04:07 KanjiMonster: thank you! Aug 21 12:12:39 build #614 of ar71xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/614 Aug 21 12:23:51 build #48 of lantiq.xrx200 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq.xrx200/builds/48 Aug 21 12:28:11 build #41 of x86.xen_domu is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.xen_domu/builds/41 Aug 21 12:41:37 build #369 of mpc85xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/369 Aug 21 12:43:41 KanjiMonster: your suggestion worked, btw. /me does happy dance. Aug 21 12:57:38 build #155 of cns3xxx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/155 Aug 21 13:10:20 hi - I've done some changes to support RB2011UiAS-2HnD and would like to supply the patches - i already subscribed on openwrt-devel, but am still waiting for the acknowledgement.. Who is maintaining the list and willing to help? Aug 21 14:08:20 build #554 of mcs814x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/554 Aug 21 14:51:38 To anyone who maintains the target/linux/generic/patches-3.14/259-regmap_dynamic.patch, please fix line #17 (http://paste.debian.net/116698) that has a missing '"' at the end. Aug 21 15:14:42 build #537 of mpc52xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/537 Aug 21 15:54:24 ping slachta. I have sent you some PMs. Go check them out. Aug 21 16:09:36 build #559 of adm5120 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/559 Aug 21 16:33:12 build #155 of adm8668 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/155 Aug 21 16:43:47 build #553 of gemini is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/553 Aug 21 16:43:50 build #151 of omap is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/151 Aug 21 16:46:27 build #171 of sunxi is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/171 Aug 21 16:56:22 * dottedmag wonders why a lot of old closed bugs were moved to BB 14.07 milestone, like https://dev.openwrt.org/ticket/132 Aug 21 16:58:46 nico r42251 packages/libs/freetype/Makefile * freetype: moved to github Aug 21 16:58:47 nico r42252 packages/libs/liblo/Makefile * liblo: moved to github Aug 21 16:58:49 nico r42253 packages/utils/gnupg/Makefile * gnupg: moved to github Aug 21 17:06:43 nico r42254 packages/multimedia/fswebcam/Makefile * fswebcam: moved to github Aug 21 17:10:21 because they're closed with it now. they were all bugs fixed in trunk, so they're rolled up into bb? Aug 21 17:26:17 karlp: dottedmag: more likely a mass update done a bit too broad Aug 21 17:42:16 build #663 of ppc44x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/663 Aug 21 17:56:15 cyrusff: ping Aug 21 17:56:17 :) Aug 21 17:56:31 Hauke: if this SPI driver seems to be working for soem devices at least, could you push it? Aug 21 17:56:40 Hauke: i'm not sure what else to try on R6250 so far :( Aug 21 18:28:19 jogo r42255 branches/barrier_breaker/package/network/services/dropbear/Makefile * BB: dropbear: restore performance by disabling mips16 Aug 21 18:31:20 build #269 of imx6 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/269 Aug 21 18:44:54 <_trine> Kaloz, I have still not been able to get HW crypto engine working on the dockstar is there any chance you could take a look at it? Aug 21 18:45:25 zajec: yes I will merge them Aug 21 18:46:45 <_trine> Kaloz, http://paste.debian.net/116789/ Aug 21 18:48:54 <_trine> Kaloz, this is how it should look when its working http://paste.debian.net/116791/ Aug 21 19:12:45 nbd r42256 trunk/package/network/ (7 files in 2 dirs) * xtables-addons: update to version 2.5 Aug 21 19:12:48 nbd r42257 trunk/package/libs/uclient/Makefile * uclient: update to latest version, fixes HTTP keepalive issues Aug 21 19:13:20 nbd r42258 branches/barrier_breaker/package/libs/uclient/Makefile * uclient: update to latest version, fixes HTTP keepalive issues Aug 21 19:19:03 build #674 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/674 Aug 21 19:22:51 build #632 of sibyte is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/632 Aug 21 19:31:47 Hauke: any ideas what else may be wrong with R6250? Aug 21 20:10:11 Does anyone know if udhcp supports a failover address? Aug 21 20:20:30 build #644 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/644 Aug 21 20:29:53 zajec: no I have no idea what could be wrong on R6250 Aug 21 20:30:41 the boot loader log looks like it starts a small cfe version from serial flash which then loads a normal cfe from nand flash Aug 21 20:34:16 I never paid attention to this log Aug 21 20:34:35 Hauke: did reading chip ID work for you? Aug 21 20:34:50 yes Aug 21 20:34:54 Weird Aug 21 20:45:01 zajec: is "mtd: bcm53xxspiflash: new driver for SPI flahes on Broadcom ARM SoCs" the same as your v2 got OpenWrt? Aug 21 20:49:03 right Aug 21 20:49:53 btw. you may test it with SmartRG if you wish to Aug 21 20:55:40 _trine: I won't have time for it for some time. make sure you have both mv_cesa loaded as well as cryptodev-linux for it Aug 21 20:56:09 zajec: what device(s) do you have with that b0rkedcom arm? Aug 21 20:56:30 <_trine> Kaloz, I have done all that,, the code generally does not compile or work Aug 21 20:56:52 Netgear R6250 Aug 21 20:57:35 zajec: ah, so you are pretty much stuck at netbooting until you have a nanddriver Aug 21 20:58:04 _trine: well, thing is you are trying quite some stuff at the same time :) Aug 21 20:58:07 Kaloz: or initramfs Aug 21 20:58:42 <_trine> Kaloz, the thing is the code does not work Aug 21 20:58:47 but yeah, we need nand driver Aug 21 20:58:49 zajec: that's netbooting in my pov :) I rather avoid nfsroot because of the pain it causes Aug 21 20:59:17 _trine: I'm pretty sure it does. just you have to figure out which one with which way Aug 21 20:59:29 _trine: ocf is a mess, but that';s what most people used Aug 21 20:59:29 <_trine> and it is not compiling I have applied some patches which makes the code compile but even then it does not make HW crypto work Aug 21 20:59:52 _trine: if you want to use the in-kernel mv_cesa and openssl (because of some kinf od perversion) you need cryptodev-linux Aug 21 21:00:36 Kaloz: AFAICT, the mv_cesa compiles OK but doesn't work. Aug 21 21:01:04 Mazilo: how did you test it? Aug 21 21:01:05 <_trine> Kaloz, I just want any way to have HW crypto working even if I have to commit some kind of perversion Aug 21 21:01:07 <_trine> :P Aug 21 21:01:32 Mazilo: because openssl itself won't use cryptodev with it Aug 21 21:01:48 Kaloz: http://paste.debian.net/116787/ Aug 21 21:02:04 <_trine> Kaloz, your help to get this working would be appreciated Aug 21 21:02:06 Mazilo: that means nothing Aug 21 21:02:16 Kaloz: While openssl is doing the above, it used about 90% CPU resources. Aug 21 21:02:25 Mazilo: you are testing a userland software and claim in-kernel crypto doesn;t work Aug 21 21:02:48 Mazilo: if you want to use the in-kernel accelerator, try ipsec/dmcrypt Aug 21 21:03:05 Kaloz: So we can't test using openssl? Aug 21 21:03:09 Mazilo: if you want userland to use it, that means you need cryptodev-linux and openssl patching Aug 21 21:03:45 Kaloz: The cryptodev is broken when tried to compile. Aug 21 21:04:16 Mazilo: cryptodev is an interface - if you've tried ocf's cryptodev, that needs ocf Aug 21 21:04:34 Mazilo: and that doesn't use mv_cesa, but it's own MvCesa driver Aug 21 21:04:52 Mazilo: if you want to use the in-kernel mv_cesa, you have to use cryptodev-linux Aug 21 21:05:03 <_trine> Kaloz, come on give us a hand here Aug 21 21:05:04 Kaloz: That's even better. But, OCF doesn't even compile. Aug 21 21:05:08 I know the names could be confusing, I wasn't the one who came up with them Aug 21 21:05:31 _trine: look up, I've did pretty much that :) Aug 21 21:06:08 <_trine> Kaloz, yes but for me I need you to do it for me Aug 21 21:06:30 Kaloz: If you do a 'make kernel_menuconfig', go into OCF and enable Kirkwood HW option. This will cause kernel compilation fail with error messages, i.e. can Aug 21 21:06:38 <_trine> I have been trying none stop for more than a week Aug 21 21:06:43 not find linux/autogen.h file. Aug 21 21:09:32 Kaloz: When I posted this issue long time ago on OpenWRT forum (https://forum.openwrt.org/viewtopic.php?pid=137835#p137835), I got this response (https://forum.openwrt.org/viewtopic.php?pid=219221#p219221 that explained pretty wall, AFAICT. Aug 21 21:10:39 hauke r42259 trunk/target/linux/ (6 files in 2 dirs) * bcm53xx: backport more spi-nor patches Aug 21 21:10:42 Mazilo: this is what I've said. you have to pick a driver for your purposes Aug 21 21:11:14 hauke r42260 trunk/target/linux/ bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch bcm53xx/patches-3.14/405-mtd-bcm53xxspiflash-try-using-JEDEC-as-one-of-method.patch bcm53xx/config-3.14 * bcm53xx: add bcm53xxspiflash driver for SPI flashes Aug 21 21:11:22 Mazilo: and actually noone likes ocf here imho.. hence you have to fix it up if you want to :) Aug 21 21:11:36 Kaloz: Isn't the OCF Kirkwood HW driver? Aug 21 21:11:49 Mazilo: I will try to get cryptodev-linux working with mv_cesa, but only when I'll have time Aug 21 21:12:06 Kaloz: That's fair. Aug 21 21:12:17 Mazilo: ocf is a framework. if you want to you that with openssl, you need ocf's driver for the crypto engine Aug 21 21:12:44 Mazilo: if you want to use the in-kernel mv_vesa driver, you have to use cryptodev-linux to get it working with openssl Aug 21 21:13:05 Mazilo: it's either OCF or the other way, you can't mix both and await success :) Aug 21 21:13:29 Kaloz: I am hoping you will get a chance to fix the mv_cesa driver. Aug 21 21:14:06 <_trine> Kaloz, in Cryptographic API there is Hardware crypto devices/ Aug 21 21:14:19 <_trine> Marvell's Cryptographic Engine Aug 21 21:14:22 <_trine> and Aug 21 21:14:59 <_trine> OCF (Open Cryptograhic Framework) Aug 21 21:15:08 <_trine> kirkwood (HW crypto engine) Aug 21 21:15:21 <_trine> I have been trying those Aug 21 21:15:30 <_trine> is that wrong Aug 21 21:16:05 _trine: you have tried to pour diesel in your gasoline car and the other way around Aug 21 21:16:06 <_trine> I was also including cryptodev Aug 21 21:16:38 <_trine> Kaloz, I would try water if i didnt know any better thats why I am asking you Aug 21 21:16:56 _trine: you either want ocf or cryptodev-linux, not both, they basically do the same Aug 21 21:17:29 <_trine> Kaloz, where does kirkwood (HW crypto engine) fit into this Aug 21 21:17:46 difference is that ocf includes some drivers on it's own, whereas cryptodev-linux uses linux kernel included drivers Aug 21 21:18:01 and ocf is outdated in general Aug 21 21:18:09 <_trine> is one way better than the other? Aug 21 21:18:16 _trine: you want to have hw crypto with openssl. for that, you need the cryptodev _framework_ Aug 21 21:18:45 _trine: ocf has its own driver for the marvell crypto engine as well it's own "driver" for cryptodev support for openssl Aug 21 21:19:27 _trine: the in-kernel cryptoapi has it's own driver called mv_cesa and it needs cryptodev-linux to have a "driver" for cryptodev for openssl Aug 21 21:19:48 (tried to simplify it, as relations and dependencies are pretty much the other way around, but still) Aug 21 21:20:10 Kaloz: the problem is that one piece of software is called cryptodev-linux and the generic interface is called cryptodev :) Aug 21 21:20:33 <_trine> well I am grateful for any simplification Aug 21 21:20:34 gustavoz: and the kernel driver is mv_cesa the ocf driver is MvCesa Aug 21 21:20:34 :) Aug 21 21:20:51 Kaloz: that too, but in my experience (powerpc mostly) the ocf included drivers are pretty bad Aug 21 21:21:00 gustavoz: it's BSD Aug 21 21:21:01 :P Aug 21 21:21:12 Kaloz: i'm trying not to confuse the guy/gal here ;) Aug 21 21:21:31 neither drivers is compilable ATM. Aug 21 21:21:52 Mazilo: that's more than likely completely wrong Aug 21 21:22:05 Mazilo: you just can't use mv_cesa for what you want it for Aug 21 21:22:25 ocf can use the kernel drivers with the cryptosoft module IIRC Aug 21 21:22:25 Mazilo: it would still provide hw crypto for dmcrypt/ipsec/etc Aug 21 21:23:08 Kaloz: I meant cryptodev-linux package is broken (at least that happened to me when the kirkwood kernel got updated to v3.14.16). Aug 21 21:23:23 gustavoz: that's like driving a car when you're drunk and making sure you are covering your eyes, too ;) Aug 21 21:23:51 <_trine> Kaloz, you have some funny analogies Aug 21 21:23:59 Mazilo: that's not the hw crypto driver ;) and well, try the snapshots/mail the auther Aug 21 21:24:07 Mazilo: there's a patch for that, let me dig it up -> https://github.com/cryptodev-linux/cryptodev-linux/commit/57b5544de80db85c8955499831fdaa30829db77a Aug 21 21:24:16 Mazilo: this isn't a device specific issue than but general issue with new kernels Aug 21 21:24:22 1.7 should be out soon though Aug 21 21:24:40 Kaloz: well it's another slow-things-up layer ;) Aug 21 21:25:34 Kaloz: Regardless, can we have it fixed once and for all so that we can take the advantage of what kirkwood HW crypto chip can offer? Aug 21 21:26:36 Mazilo: you'll want patch 01 from Nikos for openssl from http://rt.openssl.org/Ticket/Display.html?id=2770&user=guest&pass=guest to make it behave well Aug 21 21:26:48 Mazilo: sure. but as long as I'm doing something else for a living, this will happen when I have free time for it :) Aug 21 21:27:01 Mazilo: there is no "once and for all", things tend to break sometimes (due to API changes etc), especially if they are maintained out of tree Aug 21 21:27:06 Kaloz: That is perfectly fine with me. Aug 21 21:27:14 Mazilo: and once and for all won't happen in the FOSS world, as another kenrel change cna break it again in the future ;) Aug 21 21:27:23 * Kaloz pokes KanjiMonster Aug 21 21:27:25 :) Aug 21 21:27:54 * _trine also pokes KanjiMonster Aug 21 21:27:58 Kaloz: That's true. What I meant on once-and-for-all is for this v3.14.16 kernel. Aug 21 21:27:59 <_trine> :) Aug 21 21:28:29 Mazilo: btw, the patch gustavoz linked you worked for me with 3.13 for omap Aug 21 21:28:37 there already is a pull request pending with the fix on github waiting for the package maintainer to pick it up Aug 21 21:28:48 works for me up to 3.16.1 which last i've checked was latest ;) Aug 21 21:28:52 Mazilo: just never got around of updating cryptodev Aug 21 21:29:12 Mazilo: when I'll do, I'll simply nuke ocf from the openwrt worls Aug 21 21:29:15 I have no problem to wait. Aug 21 21:29:15 world* Aug 21 21:29:42 i've got talitos & caam accels around, and ocf talitos never worked right for me, caam... well... there's no support for that Aug 21 21:29:56 KanjiMonster: I'm pretty sure I'll end up taking that package over if that doesn't happen soon enough Aug 21 21:30:01 * _trine reminds Kaloz he is nearly 70 now so time is of the essence in my case :P Aug 21 21:30:30 _trine: LOL. Aug 21 21:30:43 <_trine> hehe I might not have long to go Aug 21 21:30:47 <_trine> who knows Aug 21 21:31:45 _trine: Just as a reminder, a cascade is for a dead (i.e. young, old, or whatever) person. Aug 21 21:32:08 <_trine> gee I feel bad now Aug 21 21:32:13 <_trine> :) Aug 21 21:32:36 _trine: No, what I meant regardless your age, anyone can pass on without any sign. Aug 21 21:33:16 it's better to pass out, after many drinks Aug 21 21:33:28 <_trine> well I guess so but I will continue to haunt this channel when I am gone Aug 21 21:34:47 _trine: you will be welcomed to do so Aug 21 21:34:55 <_trine> ta Aug 21 21:35:22 _trine: mind it you might have to wait a long time sometimes to find someone to be haunted here ;) Aug 21 21:36:01 <_trine> Kaloz, I have you in my sights if you dont get this working :P hehe Aug 21 21:39:46 Kaloz: (/me half paying attention) wgt634u depends on ocf at the moment too, fwiw Aug 21 21:42:21 for its hw crypto accelerator or something Aug 21 21:45:39 <_trine> russell--, this is the difference it makes when its working http://paste.debian.net/116789/ Aug 21 21:45:40 <_trine> http://paste.debian.net/116791/ Aug 21 21:46:53 <_trine> and instead of the cpu being at 100% it idles at about 5% Aug 21 21:50:02 russell--: well, let me quote the wiki "end-of-lifed by Netgear on October 1, 2005" Aug 21 21:52:09 russell--: clearly noone cared enough to make it working with the upstream kernel for about a decade Aug 21 21:52:21 russell--: it's quite surprising you still have a working unit :P Aug 21 22:43:13 Kaloz: I have a stack of about 50 of them Aug 21 22:43:39 they are more useful than the wrt54g Aug 21 22:46:00 if someone were to reimplement the hw crypto support for wgt634u using modern APIs, what would those be? Aug 21 22:48:50 wgt634u was pretty well supported until maybe a year or two ago Aug 21 22:54:02 <_trine> Kaloz, http://paste.debian.net/116818/ Aug 22 00:06:25 _trine: that's ocf :) Aug 22 02:15:59 build #158 of pxa is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/158 Aug 22 02:30:55 build #709 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/709 Aug 22 02:33:56 build #670 of x86 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/670 Aug 22 02:55:53 build #568 of iop32x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/568 **** ENDING LOGGING AT Fri Aug 22 02:59:58 2014