**** BEGIN LOGGING AT Thu May 15 02:59:59 2014 May 15 03:44:38 <5EXAA8SU8> build #163 of mxs is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/163 May 15 05:01:57 <5EXAA8SU8> build #574 of uml is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/574 May 15 05:58:56 <5EXAA8SU8> build #567 of x86 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/567 May 15 08:48:38 <5EXAA8SU8> build #60 of x86_64 is complete: Failure [failed compile_1] Build details are at http://buildbot.openwrt.org:8010/builders/x86_64/builds/60 May 15 09:29:09 two things, I yesterday got stuck at May 15 09:29:34 I have noticed that v3.13 and the kernel xz downloaded are different May 15 09:29:49 I have the diff between v3.13 tag and the xilinx kernel May 15 09:30:15 how may I convert that diff to apply over the downloaded sources? May 15 09:41:53 If xilinx supports, not only it's arm chipsets, but also it's vhdl chipsets, such as the microblaze, should I create a platform for each type of processor? May 15 09:42:25 I am in theory just integrating the Zynq (arm), but the kernel diff does also contain work for microblaze... May 15 09:42:33 and powerpc May 15 10:02:22 txomon|home: you want to add support for a xilinx arm SoC to OpenWrt? May 15 10:16:30 Hauke, yes May 15 10:16:40 zynq7000 chipsets May 15 10:19:54 txomon|home: is there basic support for this SoC in the linux mainline kernel? May 15 10:21:17 Hauke, yes May 15 10:21:28 but their work hasn't been fully merged yet May 15 10:21:39 and I don't know how to define basic support... May 15 10:22:09 you should add a target like target/linux/zynq7000/ and add the patches needed for this SoC May 15 10:22:28 I do not know if zynq7000 is a good name May 15 10:22:50 you should not add the stuff needed for the powerPC or some very different SoCs May 15 10:23:29 I have thought about zynq May 15 10:23:34 not zynq700* May 15 10:23:44 well, I am at the moment some very dirty things May 15 10:23:45 yes thats probably better May 15 10:24:02 if all the SoCs from this series are similar May 15 10:24:07 like having a big patch that applies over 3.13.tar.xz May 15 10:24:11 they are May 15 10:24:34 I do not like one big patch ;-) May 15 10:24:48 I have the problem I said about the mainline tag and the stable release May 15 10:24:52 how may I solve it? May 15 10:24:59 may I do the integration work? May 15 10:25:20 the git tag in linus tree should be the same as the tar you can download from kernel.org May 15 10:25:34 not my case :( May 15 10:25:41 in OpenWrt we add the patches from target/linux/generic/patches-3.13 on top of that patch May 15 10:25:50 hummm May 15 10:25:54 maybe that's my problem May 15 10:25:55 s/top of that patch/on top of the mainline kenrel/ May 15 10:26:23 ohhh ok May 15 10:26:27 then that's the problem May 15 10:26:41 is there any way to avoid those patches being applied? May 15 10:26:57 or any recommendation on them? May 15 10:28:03 you should try to resolve the conflict May 15 10:28:26 maybe mainline -> apply xilinx patches -> then try to reapply openwrt patches ? May 15 10:28:51 I do not think it will be very hard, as most of the generic patches are just adding drivers or touching stuff you should probably not touch when you want to add a new SoC May 15 10:29:27 <5EXAA8SU8> build #457 of gemini is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/457 May 15 10:29:56 here is a description on how to work with patches in OpenWrt: http://wiki.openwrt.org/doc/devel/patches May 15 10:30:04 Hauke, take into account that they also add controllers for their devices etc. May 15 10:30:45 plntyk, how may I change that order? May 15 10:30:49 yes if you are lucky you just have some conflicts in the Makefiles where the generic patches and your patch want to add a entry at the smae place May 15 10:31:19 nope, not lucky, getting collisions on usb driver May 15 10:31:34 I am going to split up the giant xilinx patch May 15 10:31:39 and see If I can bisect it May 15 10:31:48 yes splitting it up is a good idea May 15 10:35:31 btw, in buildroot is already integrated May 15 11:24:52 Hauke, just found that it's not my fault the patch failure May 15 11:24:57 it's openwrt's May 15 11:25:04 generic/102-ehci_hcd_ignore_oc.patch May 15 11:31:10 and found the reason May 15 11:31:17 comments have been changed May 15 11:33:59 the problem is that the patch for 3.13 are prepared to apply under 3.13.11 May 15 11:34:23 at least this oe May 15 11:34:25 one* May 15 11:34:34 any proposition? how should I proceed? May 15 11:34:42 correct the generic patch to apply over 3.13 May 15 11:35:21 the generic patches does not apply on 3.13.11? May 15 11:35:31 no, it does not apply on 3.13 May 15 11:35:54 should I use a 3.13.11 kernel? May 15 11:36:32 OpenWrt currently uses 3.13.7 May 15 11:36:53 the currently used kernel minor versions are in include/kernel-version.mk May 15 11:37:36 oh ok May 15 11:38:08 good to know May 15 11:38:44 so I will update the LINUX_VERSION on the make file, rather than using my one, 3.13 May 15 11:40:28 yes May 15 12:05:31 can someone explain how this patch https://dev.openwrt.org/changeset/40682/trunk works ? It wrongly detects ht_capabs on my wndr4300, and it wonly seems to work on 5ghz networks to begin with May 15 12:07:14 <5EXAA8SU8> build #459 of mcs814x is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/459 May 15 14:30:59 I have a patch to submit and review for mac80211 May 15 14:31:15 but I have no idea how to do that, and frankly I do not have the time May 15 14:31:38 anyone wants to review this and possibly correct it and submit ? May 15 14:32:23 I am not sure about the locking mechanism I am using and most certainly the code format / details will have to be corrected May 15 14:32:34 it fixes a big mem leak in mac802.11 May 15 14:34:15 that mem leak has been around at the very least since backfire May 15 14:34:42 adri: ^ May 15 14:34:48 just ping me if anyone is to the task May 15 14:35:11 afaik at least you have to send your part with a Signed off by , agreeing to the developers certificate of origin https://dev.openwrt.org/wiki/SubmittingPatches May 15 14:35:52 and mac80211 probably only interests nbd ; or people on linux-wireless mailing list May 15 14:37:22 also, if you want someone to review/correct, you should maybe provide a link to it? May 15 14:38:11 http://pastebin.com/PvD2Ym5B May 15 14:42:50 hm... is this patch against mac80211 in AA ? May 15 14:43:20 any version since backfire I believe May 15 14:43:24 including trunk May 15 14:43:45 did you have a look at http://git.kernel.org/cgit/linux/kernel/git/linville/wireless-testing.git/tree/net/mac80211/rate.h ? May 15 14:43:53 no May 15 14:44:10 oh May 15 14:44:15 interesting May 15 14:46:42 plntyk, what do you see changed ? May 15 14:46:49 plntyk, i see no change May 15 14:46:56 regarding this problem May 15 14:47:15 can you point out what you are referring to exactly in that file ? May 15 14:47:28 maybe I missed something May 15 14:47:32 ? May 15 14:47:54 so, send it to the maliing list with a signed-off-by line, and then it's at least in the record, and someone may take it or not. May 15 14:48:24 Yeah maybe I'll do that May 15 14:48:27 thanks May 15 14:50:06 nighty-_: i wasnt sure which function the patch belonged to since that was missing and I don't know any code there May 15 14:51:33 static inline void rate_control_free_sta(struct sta_info *sta) May 15 17:22:48 Is anyone here with a Comcast feed able to connect to OpenWRT SVN as well as forum? When I did a traceroute to openwrt.org, it broke in hop #6 as seen here (http://pastebin.com/Vgs9nG5x). May 15 17:24:59 I'm not on comcast, can connect from here, and from my servers in a data center without any trouble May 15 17:27:05 I sure would like to know if any Comcast users can access any OpenWRT SVN and/or Forum servers. May 15 17:27:08 mazilo: but your posts show server after the alleged breakage that reply to ping May 15 17:27:46 it is only one server that does not want to answer your ping on the route as i see it May 15 17:28:05 Exactly. But, my effort to access the OpenWRT SVN and/or Forum servers fails. May 15 17:28:29 This has happened for the past three days. May 15 17:29:59 Perhaps, I should reboot my modem to see if that will fix the issue. May 15 17:30:02 http://pastebin.com/vudBetN1 May 15 17:30:11 from my place, with local network removed May 15 17:30:39 Mazilo: if I use a looking glass and ping from a comcast location it has 100% success rate May 15 17:30:52 http://lg.eastlink.ca/ May 15 17:34:13 I tried the looking glass and hop #2 was dead. Here (http://pastebin.com/1wCSMP6W) you can see. May 15 17:35:35 again that sort of thing does not matter - it is some server that is either overloaded or configured to ignore icmp/ping requests May 15 17:37:16 mentioned for example at http://customer.comcast.com/help-and-support/internet/run-traceroute-command/ May 15 17:37:32 OK. But, I still can't connect to either OpenWRT SVN or Forum server. May 15 17:38:33 <5EXAA8SU8> build #60 of mpc83xx is complete: Failure [failed shell compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/60 May 15 17:39:37 either its modem or some flood protection from comcast spambots ? May 15 17:39:44 But, I have no problem to access the above OpenWRT buildbot May 15 17:40:06 I will try to reboot my modem to see if that will resolve the issue. May 15 17:40:14 <5EXAA8SU8> build #565 of rb532 is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/565 May 15 17:40:34 <5EXAA8SU8> build #565 of ppc44x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/565 May 15 17:41:34 <5EXAA8SU8> build #534 of sibyte is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/534 May 15 17:42:42 <5EXAA8SU8> build #59 of adm8668 is complete: Failure [failed shell] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/59 May 15 17:44:56 Still the same problem after rebooting my cablemodem. :( May 15 17:52:12 hm... check http://atw.hu/ - that seems to be the provider of the openwrt server May 15 17:52:48 I think there is a problem within the Comcast network that serves my community. May 15 19:05:25 <5EXAA8SU8> build #60 of bcm53xx is complete: Failure [failed shell_15] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/60 May 15 19:08:00 <5EXAA8SU8> build #472 of iop32x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/472 May 15 19:27:10 do you have any guide on what stuff is needed for getting a kernel booted? May 15 19:27:39 I am trying to do the base config for the xilinx kernel, trying to remove all unneeded stuff May 15 19:29:08 <[florian]> txomon|home: you need a few things: a timer driver, an UART driver, proper CPU configuration (e.g: selecting the right CPU), enabling low-level debug, an interrupt controller driver, and that's about it May 15 19:38:18 puf May 15 19:38:20 ok May 15 20:04:19 nbd r40770 trunk/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh * mac80211: fix VHT80 channel allocation (thx, SeG) May 15 20:04:23 nbd r40771 trunk/package/network/config/netifd/Makefile * netifd: update to the latest version, fixes wireless setup cancellation May 15 20:13:12 nbd r40772 trunk/toolchain/gcc/common.mk * toolchain/gcc: fix build on arm with clang as host gcc replacement May 15 21:49:25 ok, I think I have configured correctly the kernel, but will need tons of help once a board gets on my hands... May 15 21:49:32 now I have the uboot thing :( May 15 22:09:24 I will be asking tomorrow, but if someone pings me at txomon|fon I will be glad. How may I use the xilinx uboot branch? I have seen many uboot packages at packages/boot/uboot* and I don't understand how they are linked May 15 22:22:27 so the question is, how may I link my board to use its uboot? May 15 22:22:40 I will continue tomorrow trying to figure out something on that May 15 22:58:20 txomon|home: you probably shouldn't have to deal with the bootloader at all, as long as the bootloader already in flash works, just leave it be, do one thing at a time May 16 01:22:20 <5EXAA8SU8> build #545 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/545 May 16 02:23:02 <5EXAA8SU8> build #154 of mvebu is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/154 May 16 02:54:20 <5EXAA8SU8> build #611 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/611 **** ENDING LOGGING AT Fri May 16 02:59:58 2014