**** BEGIN LOGGING AT Thu Jun 05 02:59:58 2014 Jun 05 03:00:40 <5EXAA8SU8> build #97 of sunxi is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/97 Jun 05 03:03:31 <5EXAA8SU8> build #641 of brcm47xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/641 Jun 05 03:22:51 <5EXAA8SU8> build #543 of ixp4xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/543 Jun 05 05:40:35 anyone still run on WRT54GSv1? I got a hard freeze when doing 'swconfig dev switch0 show' Jun 05 05:42:29 eigma: i have one with stock firmware directly under this laptop, not plugged into power Jun 05 05:43:35 v1s did have discrete ADM6996 switches, right? that's the driver that I have built in Jun 05 05:44:57 i could open it and look but i'm tired and upset Jun 05 05:45:32 I'll open mine, thanks Jun 05 05:45:42 was only asking in case you knew off-hand Jun 05 05:58:22 <5EXAA8SU8> build #532 of ar71xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/532 Jun 05 06:17:32 <5EXAA8SU8> build #653 of at91 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/653 Jun 05 06:41:27 <5EXAA8SU8> build #630 of atheros is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/630 Jun 05 07:12:31 ~.~. Jun 05 07:15:10 hehe Jun 05 07:16:28 eigma: do you by any chance have any experience with jtag on these devices? Jun 05 07:28:04 very scarce Jun 05 07:28:36 DonkeyHotei: I've used openocd and urjtag on some other similar devices Jun 05 07:29:03 what are you trying to do? Jun 05 07:29:10 I'll try to help but no profises Jun 05 07:29:11 promises Jun 05 07:30:06 [Sat 2014-05-24 12:27:23 PM PDT] i grabbed a wrt54gs v2 with a sticker on it saying "bricked" and got a jtag header onto it, but urjtag reports "TDO seems to be stuck at 1" after the LEDs come on and settle to a blinking power. anyone ever seen similar? Jun 05 07:30:48 heh, that sounds pretty bad Jun 05 07:31:08 have you checked some power supplies, 5v, 3v3, whatever the RAM might be on? Jun 05 07:31:33 do you have a scope, to check if the device gets the clock going? Jun 05 07:31:35 the 3.3v pins provide 3.3v Jun 05 07:31:44 i do not Jun 05 07:32:23 with an ohmmeter, check TDO to ground, to some supply rails, is it shorted to a rail, or being *driven* from the chip Jun 05 07:32:24 but i might get access to one Jun 05 07:32:35 (obviously unpowered when checking with ohmmeter) Jun 05 07:34:06 you've checked your jtag rig against some other device? Jun 05 07:34:34 worked on a wrt54g v2 Jun 05 07:39:43 3.3v rail is 3.38v, infinite resistance to tdo with power off Jun 05 07:48:20 you checked voltage on TDO, it's really 3.3v? Jun 05 07:51:44 eigma: voltage on tdo is zero Jun 05 08:11:12 I don't think TDO is typically inverted.. Jun 05 08:11:26 strange that urjtag says it's stuck at 1 Jun 05 08:21:31 blogic r41005 trunk/target/linux/lantiq/patches-3.10/0010-MIPS-lantiq-wifi-and-ethernet-eeprom-handling.patch * lantiq: fix eep handling patch Jun 05 08:21:35 blogic r41006 trunk/package/system/procd/files/procd.sh * procd: rename local variable in uci_validate_section Jun 05 08:29:28 h Jun 05 08:31:38 weird, looks like I have a device model WRT54GS, FCC ID containing "WRT54GV2", nvram points to an WRT54G, but its LED GPIO layout most closely matches the "WRTSL54GS" board Jun 05 10:38:02 cyrusff: is there any "good" way of improving this situation? http://pastebay.net/1446428 Jun 05 10:38:23 I know it matters when one package Makefile offers more than one package, but is there a better way? Jun 05 10:48:08 not really Jun 05 10:48:26 i mean probably not going to get any better than that Jun 05 10:49:28 Could the feeds script be adjusted to allow only one package of the same name to be installed at a time? Jun 05 10:49:45 it only does, except you have to be damn careful where it will pull from first Jun 05 10:50:07 that's the problem I run into having packages in my own "upstream" feed as well as the owrt-packages feed Jun 05 10:50:19 particularly where dependent packages get pulled from Jun 05 10:57:39 blogic r41007 trunk/package/system/procd/Makefile * procd: update to latest git head Jun 05 10:57:43 blogic r41008 trunk/package/system/procd/files/procd.sh * procd: add wrapper calls for interface triggers Jun 05 10:57:46 blogic r41009 trunk/package/network/config/netifd/Makefile * netifd: update to latest git HEAD Jun 05 10:57:50 blogic r41010 trunk/package/network/config/netifd/files/etc/init.d/network * netfid: make procd watch the network.interface object for events Jun 05 10:57:54 blogic r41011 trunk/package/ network/services/igmpproxy/files/igmpproxy.init network/services/igmpproxy/Makefile network/services/igmpproxy/files/igmpproxy.hotplug * igmpproxy: register interface change triggers Jun 05 11:01:43 karlp: you know you can commit without doing pull requests? ;) Jun 05 11:01:50 yeah, I know :) Jun 05 11:02:18 I'm just leaving a little breathing room, before arbitrarily taking over libraries that I didn't own/look after before :) Jun 05 11:02:42 this is actually something I missed with mosquitto, libcares had always just existed in the past Jun 05 11:03:10 also, it lets other people have a look at it, even if I merge it myself in a couple of days? Jun 05 11:03:32 But I'm all ears if you'd rather I did this differently? Jun 05 11:05:12 no its fine Jun 05 11:07:25 cyrusff: karlp: doing pull requests even if you have commit access isn't a bad idea, allows for code review by others Jun 05 11:07:41 sure. i was just wondering Jun 05 11:07:45 KanjiMonster: that was my thinking, especially as I've never had it before Jun 05 11:08:06 do all this however you like ;) Jun 05 11:08:25 the result is what counts Jun 05 11:11:33 nbd: ;) Jun 05 11:29:31 pie in the sky, any chance "scripts/feeds remove" coud be added as an alias for uninstall? opkg only has install/remove, but scripts/feeds uses install/uninstall. Maybe it's just me, but I always use the wrong one first Jun 05 11:57:12 nbd r41012 trunk/package/network/services/hostapd/files/netifd.sh * hostapd: move reading of rsn_preauth out of auth_type=eap context Jun 05 12:21:18 doh, worked out how to write procd init script, found a bug in monit where the "stay in the foreground" feature got broken. Jun 05 13:14:04 cyrusff: I'm using avahi-daemon at present, just for advertising services, I see you're maintaining mdnsresponder, can Iuse that for the same purpose? one less package to migrate, I dont need any of the avahi addressing portions Jun 05 13:15:54 You can. Colleague has put countless hours in it to make it stable. Jun 05 13:16:47 We also have a proxy based upon that to make it work across links Jun 05 13:17:30 Still i guess someone will pick up avahi at somepoint Jun 05 13:17:34 so the files/mDNSResponder.conf right now, that does the same thing as the /etc/avahi/services/ssh.service I guess? Jun 05 13:17:55 I'm trying to be proactive, without having to put my name down on an unrealistic amount of packages Jun 05 13:18:03 Sure Jun 05 13:18:15 I mean mdnsresponder can do tge same Jun 05 13:18:27 Just config is differ ent Jun 05 13:19:01 procd runs it with -debug? was that intentional? Jun 05 13:19:35 Yeah we should probably patch in a -foreground Jun 05 13:19:49 ahh, that's why debug :) Jun 05 13:19:56 Yeah Jun 05 13:20:22 Have that on my todo somewhere Jun 05 13:20:45 procd question, I see there's procd_set_param command, respawn and env, which are obvious enough Jun 05 13:20:54 what does "set_param file" do? Jun 05 13:23:59 if procd and respawn are awesome enough, with these triggers and everything, I should be able to drop "monit" et al right? Jun 05 13:34:51 well, if you want process to keep running, procd's your process indeed Jun 05 13:35:53 it would be useful to at some point harmonize the service definitions across avahi/mdnsd(=mDNSResponder) Jun 05 13:36:04 yet another thing on the 'one day'.. Jun 05 13:37:47 nah, we'll simply replace avahi and mDNSResponder Jun 05 13:37:48 very soon Jun 05 13:38:06 chuckle, looking forward to 100% implementation of the set of RFCs mDNSResponder implements Jun 05 13:38:23 work in progress is here: http://git.openwrt.org/?p=project/mdnsd.git;a=summary Jun 05 13:38:28 Nbd: please add v6 support beforehand Jun 05 13:38:30 ;) Jun 05 13:38:32 6762 6763 draft-sekar-*llq* and some other things at least.. Jun 05 13:38:40 if I remember right, just 6762 has 100ish MUSTs Jun 05 13:38:49 ok, so I was just about to start dropping my basic avahi config to mDNSResponder, as cyrus is maintaining that, should i Just ignore this then until mdnsd is "finished" ? Jun 05 13:39:21 I (obviously incorrectly) assumed that mDNSResponder was the "blessed" way forward if that was the one being maintained by cyrusff Jun 05 13:39:43 well, I think they'll wind up answering different needs Jun 05 13:39:56 mdnsd if you want to advertise services on your device, and mDNSResponder for 'rest' Jun 05 13:40:08 because unless nbd has year+ of motivation, mdnsd won't match mDNSResponder on feature front Jun 05 13:40:14 cyrusff: sure, when i get around to it Jun 05 13:40:23 idli: so what kind of features are you interested in? Jun 05 13:40:33 btw. we want to cover more than just advertising services, browsing is useful as well Jun 05 13:40:38 start with full implementation of those RFCs, add the dns_sd.h API Jun 05 13:40:41 nbd: can yours not be called "mdnsd" at the same time as the mDNSResponder has "mdnsd" ? Jun 05 13:40:49 karlp: don't worry, we'll rename it Jun 05 13:41:04 basically, my own motivation is just to be able to do hybrid proxy on top of that Jun 05 13:41:12 and that requires 'full' implementation of those RFCs mentioned, more or less Jun 05 13:41:17 hybrid proxy? Jun 05 13:41:32 https://github.com/sbyx/ohybridproxy Jun 05 13:41:36 Making mdns wirk across link Jun 05 13:41:43 specified in http://tools.ietf.org/html/draft-cheshire-dnssd-hybrid-01 Jun 05 13:41:50 Mdns is link-local mc Jun 05 13:42:08 oddly enough cero guys and us who play with homenet WG stuff find more than one link useful ;) Jun 05 13:42:29 ah, right Jun 05 13:42:40 Basically we need an api to do arbitrary queries. Jun 05 13:42:47 Via ubus or so Jun 05 13:42:57 sure, we can implement that Jun 05 13:43:13 i want the mdns rewrite to be able to handle such stuff as well Jun 05 13:43:28 so we don't have to rely on ugly bloatware code Jun 05 13:43:48 I guess once we have ability to query by arbitrary dnstype and domain Jun 05 13:44:02 We could do initial port of the proxy to that Jun 05 13:44:32 And as mdnsd gains more and more features it will just work better Jun 05 13:44:50 i still have to learn a bit more about how mdns works - at the moment i'm still busy with minor cleanups to blogic's code and finishing the openwrt integration part wrt. service announcements Jun 05 13:45:07 nbd: hello, i've one more request to you Jun 05 13:45:17 nbd: could you take care of my mac80211/b43 patches, please? Jun 05 13:45:20 there are 2 more Jun 05 13:45:34 zajec: will look into it Jun 05 13:45:37 thanks Jun 05 13:45:43 Well important facts are its lin-local multicast and some clients expect ttl of 255 Jun 05 13:45:57 Which means regular mc routing will not do Jun 05 13:46:03 yeah, i know Jun 05 13:46:18 i got some sense of how the low level protocol works by looking at the code Jun 05 13:46:23 Ok Jun 05 13:46:25 i'm just not familiar with most of the protocol interactions yet Jun 05 13:46:31 can nbd's mdnsd or mDNSResponder help with advertising to windows? Jun 05 13:46:40 we've started using: https://gitorious.digitalstrom.org/dss-misc/upnpbeacon whcih works well, Jun 05 13:46:40 No windows uses ssdp Jun 05 13:46:50 Which is upnp based Jun 05 13:47:06 that's what I thought, just knew I couldn't do it with avahi-daemon at least Jun 05 13:47:31 one could add a daemon that implements ssdp and talks to mdnsd on the backend side via ubus Jun 05 13:47:39 there's some mini* stuff that deals with some parts of upnp Jun 05 13:47:48 not sure how useful that would be as SSDP isn't DNS-based for most part Jun 05 13:47:52 I've packaged upnpbeacon with UCI support, but I can't see all teh overlapping parts Jun 05 13:47:52 service defintions would look different Jun 05 13:48:03 most of the minixxx stuff I saw was only interested in media playing or port opening Jun 05 13:48:09 or well, suppose you could provide _all_ of that crap in there and have it pick something useful Jun 05 13:48:16 miniupnp git repo has minissdpsomething too Jun 05 13:48:18 never played with it Jun 05 13:48:49 Yeah miniupnp itself is more for the various firewall hole punching protocols Jun 05 13:49:00 Again there are 3 Jun 05 13:49:01 ;) Jun 05 13:50:01 most of that upnp stuff is so full of xml I feel dirty just looking at it Jun 05 13:50:01 well, the upnpbeacon thing works nicely for showing up our devices in windows explorer -> network -> other devices Jun 05 13:50:29 which was nice, previously it was safari only for bonjour bookmarks, and the really not very pretty "avahi-discover" for linux Jun 05 13:52:44 nbd r41013 trunk/package/libs/libubox/Makefile * libubox: update to the latest version, adds static vlist initializer macros Jun 05 13:52:47 that sounds useful to have Jun 05 13:52:47 nbd r41014 trunk/package/kernel/mac80211/patches/830-b43-workaround-pcie-bcm4716.patch * mac80211: b43: update BCM4716 patch to compile without SSB Jun 05 13:52:51 nbd r41015 trunk/package/kernel/mac80211/Makefile * mac80211: b43: make support for SSB optional Jun 05 13:52:56 zajec: there you go Jun 05 13:53:00 we're looking at multi-link upnp and it's _not_ pretty Jun 05 13:53:15 but perhaps router advertising itself would be a first step Jun 05 13:54:28 Basically same problem there. Windows only does link-local mc for upnp Jun 05 13:54:49 somewhat sadder, because the spec exists for site-local and even global Jun 05 13:54:55 but windows doesn't even try it, without registry hacks Jun 05 13:59:38 nbd: thanks again! Jun 05 14:00:04 i start liking brcm47xx state ;) Jun 05 14:03:13 zajec: btw, saw your post (in february) on the linksys e900 Jun 05 14:03:15 what's up with that one? Jun 05 14:04:00 works except for wireless ofc Jun 05 14:04:19 right now I work on 5 GHz support in b43 Jun 05 14:04:23 wireless because it's a 53572 ? Jun 05 14:04:27 yeah Jun 05 14:04:35 (not that familiar with brcm47xx, so just asking) Jun 05 14:04:35 okay Jun 05 14:04:42 you may want to see http://wireless.kernel.org/en/users/Drivers/b43/soc Jun 05 14:05:08 53572 means 0x2057 radio and high PHY revision Jun 05 14:05:12 b43 doesn't support them Jun 05 14:06:39 gotcha, thanks Jun 05 14:10:50 nbd r41016 trunk/package/kernel/mac80211/patches/ (37 files) * rt2x00: merge beacon setup fixes, disable unused hw beacon slots Jun 05 14:14:14 idli: the upnpbeacon is packaged here: https://github.com/remakeelectric/owrt_pub_feeds/tree/master/upnpbeacon with uci support if you want to try it out, Jun 05 14:15:33 karlp: ah, cool, I'll keep it in mind next time I start to play with upnp stuff Jun 05 14:15:54 (I'm running Windows-free production network at home, but for demo purposes and whatever it's useful to cater to 'that crowd' too) Jun 05 14:18:28 yeah, we are normally a DHCP client, so it's nice to have for the "where's my device" situation Jun 05 14:56:39 nbd r41017 trunk/package/kernel/mac80211/patches/300-pending_work.patch * ath9k: merge a p2p powersave handling fix Jun 05 14:56:43 nbd r41018 trunk/package/kernel/mac80211/patches/ 522-mac80211_configure_antenna_gain.patch 310-ap_scan.patch 300-pending_work.patch 520-mac80211_cur_txpower.patch * mac80211: merge a series of cleanups/fixes Jun 05 14:56:47 nbd r41019 trunk/package/network/services/hostapd/patches/370-ap_sta_support.patch * wpa_supplicant: fix locking hostapd to 20MHz (#12720) Jun 05 14:56:50 nbd r41020 trunk/package/system/procd/Makefile * procd: update to the latest version, fixes a crash on early boot Jun 05 15:15:05 nbd r41021 trunk/package/kernel/mac80211/patches/560-ath9k_pcoem_optional.patch * ath9k: fix enabling PC-OEM card support (#16624) Jun 05 15:59:37 nbd r41022 trunk/package/ (16 files in 2 dirs) * hostapd: update to 2014-06-03 Jun 05 16:12:51 with procd, is ther ea way of grabbing the pid of the service it started? Jun 05 16:13:25 I've been getting the pid and adjusting the oom_adj score in /proc to make some of my processes more likely to be killed, (so that the process monitor it more likely to survive and restart them) Jun 05 16:14:22 hi guys, is luci-app-sqm already added in trunk? -> http://patchwork.openwrt.org/patch/5079/ Jun 05 16:25:08 eigma: i checked with a working unit, zero volts is normal for TDO Jun 05 17:40:33 <5EXAA8SU8> build #586 of rb532 is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/586 Jun 05 17:40:43 <5EXAA8SU8> build #586 of ppc44x is complete: Failure [failed shell shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/586 Jun 05 17:41:07 <5EXAA8SU8> build #631 of atheros is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/631 Jun 05 17:41:15 <5EXAA8SU8> build #632 of orion is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/632 Jun 05 17:41:57 <5EXAA8SU8> build #555 of sibyte is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/555 Jun 05 17:42:11 <5EXAA8SU8> build #492 of ep93xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/492 Jun 05 17:42:20 <5EXAA8SU8> build #175 of mvebu is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/175 Jun 05 17:42:49 <5EXAA8SU8> build #493 of iop32x is complete: Failure [failed shell shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/493 Jun 05 17:43:16 <5EXAA8SU8> build #296 of mpc85xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/296 Jun 05 17:43:25 <5EXAA8SU8> build #481 of mcs814x is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/481 Jun 05 17:44:20 <5EXAA8SU8> build #464 of mpc52xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/464 Jun 05 17:44:29 <5EXAA8SU8> build #98 of sunxi is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/98 Jun 05 17:45:24 <5EXAA8SU8> build #443 of octeon is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/443 Jun 05 17:45:33 <5EXAA8SU8> build #81 of pxa is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/81 Jun 05 17:46:29 <5EXAA8SU8> build #84 of cns21xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/84 Jun 05 17:46:37 <5EXAA8SU8> build #82 of mpc83xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/82 Jun 05 17:47:34 <5EXAA8SU8> build #83 of bcm53xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/83 Jun 05 17:47:41 <5EXAA8SU8> build #81 of brcm2708 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/81 Jun 05 17:48:38 <5EXAA8SU8> build #83 of realview is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/realview/builds/83 Jun 05 17:48:47 <5EXAA8SU8> build #80 of omap is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/80 Jun 05 17:49:43 <5EXAA8SU8> build #81 of adm8668 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/81 Jun 05 17:49:51 <5EXAA8SU8> build #81 of malta is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/malta/builds/81 Jun 05 17:50:47 <5EXAA8SU8> build #81 of cns3xxx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/81 Jun 05 17:50:56 <5EXAA8SU8> build #82 of x86_64 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/x86_64/builds/82 Jun 05 18:24:01 Hi Hauke Jun 05 18:24:10 Hauke: have some free time? Jun 05 18:24:29 Hauke: i already asked nbd to handle b43 patches which he did :) Jun 05 18:24:40 Hauke: so I wonder if you could try my subtarget(s) patches Jun 05 18:25:25 Hauke: i've tested "generic" and "mips74k" subtargets on my devices (i've devices based on BCMA only) and they work :) Jun 05 18:44:06 <5EXAA8SU8> build #521 of au1000 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/521 Jun 05 18:52:23 <5EXAA8SU8> build #662 of brcm63xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/662 Jun 05 18:59:28 <5EXAA8SU8> build #192 of imx6 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/192 Jun 05 19:02:13 <5EXAA8SU8> build #626 of cobalt is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/626 Jun 05 19:11:15 zajec_: I will try it today Jun 05 19:12:28 after having generic and mips74k, it would be good to have a 'legacy' subtarget as well Jun 05 19:12:31 or something similar Jun 05 19:12:40 without tg3, bgmac, bcma, etc. Jun 05 19:13:34 <5EXAA8SU8> build #597 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/597 Jun 05 19:28:56 Hauke: thanks, that's great Jun 05 19:29:07 nbd: i already started that, give me a sec Jun 05 19:29:38 nbd: http://patchwork.openwrt.org/patch/5437/ Jun 05 19:29:52 nbd: i didn't plan to have separated builds for tg3 and b44 Jun 05 19:30:02 nbd: i planned one firmware for both: tg3 and b44 Jun 05 19:30:29 nbd: i'll continue work on this subtarget ofc Jun 05 19:30:39 tg3 is big Jun 05 19:30:43 nbd: i just prefered to do mips74k first, as I can test it Jun 05 19:30:47 nbd: oh, i didn't know tha Jun 05 19:30:49 and it pulls in ptp, pps and hwmon Jun 05 19:31:06 ouch Jun 05 19:31:14 so getting rid of that will be good for devices with 16M RAM Jun 05 19:31:28 which are quite close to the RAM usage limit with current builds Jun 05 19:31:48 ok, i'll think about even more 2 separated subtargets then Jun 05 19:31:52 i wanted to avoid too many Jun 05 19:31:58 but I'll see in this situation Jun 05 19:32:14 i mean it could be bmips3300, generic and mips74k Jun 05 19:32:45 nbd: but sine you don't want tg3 in bmips3300 Jun 05 19:32:49 if i remember correctly, devices that use tg3 are typically big enough that a bit of extra bloat shouldn't matter that much Jun 05 19:32:58 so they can run the generic subtarget Jun 05 19:32:58 nbd: it'd be nice to have something with tg3 too Jun 05 19:33:04 oh Jun 05 19:33:08 another thing i didn't know Jun 05 19:33:14 i'll look for tg3 devices Jun 05 19:33:15 thanks for info Jun 05 19:33:19 well, i'm not that sure about it Jun 05 19:33:24 it's just an assumption Jun 05 19:33:25 ok, i'll check that first Jun 05 19:35:07 i'm really happy with recent drop of SSB dependncy in b43 :) Jun 05 19:37:50 zajec: tg3 was only used in bcm4705/4785 Jun 05 19:38:04 I know only of linksys devices with this chip: https://en.wikipedia.org/wiki/Linksys_routers Jun 05 19:38:14 all have 32 or 64 MB ram Jun 05 19:39:40 yeah, it matches wikidevi database Jun 05 19:40:53 ok... tg3.c si HUGE Jun 05 19:42:14 i guess i know why I saved 128 KB in mips74k now ;) Jun 05 19:42:19 by disabling tg3 Jun 05 19:42:21 (mostly) Jun 05 19:43:06 i'm now damn happy I never had to touch tg3 ;) Jun 05 19:56:58 <5EXAA8SU8> build #557 of xburst is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/557 Jun 05 20:14:14 zajec: you send these two patches right? http://patchwork.openwrt.org/patch/5597/ http://patchwork.openwrt.org/patch/5577/ Jun 05 20:14:36 right Jun 05 20:14:44 older ones are deprecated Jun 05 20:15:14 Hauke: you can drop http://patchwork.openwrt.org/patch/5437/ and http://patchwork.openwrt.org/patch/5438/ , they were just RFC Jun 05 20:36:38 <5EXAA8SU8> build #566 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/566 Jun 05 20:43:18 Hauke: any idea how to name different sets of WRT54G*? Jun 05 20:43:51 WRT54G V2 and WRT54GS V1 share the same IDs Jun 05 20:43:56 0x0101/42/0x10 Jun 05 20:44:12 I do not know Jun 05 20:44:20 BCM47XX_BOARD_LINKSYS_WRT54GV2_WRT54GSV1 looks hacky Jun 05 20:44:35 even worse for other IDs Jun 05 20:45:25 BCM47XX_BOARD_LINKSYS_WRT54GV22_WRT54GV3_WRT54GV31_WRT54GSV11_WRT54GSV21 ... Jun 05 20:45:27 nooo :p Jun 05 20:45:39 maybe we should try using type? Jun 05 20:46:08 BCM47XX_BOARD_LINKSYS_WRT54G_0101 / BCM47XX_BOARD_LINKSYS_WRT54G_0708 / BCM47XX_BOARD_LINKSYS_WRT54G_0467 Jun 05 20:51:19 nbd: I am running into this problem: https://dev.openwrt.org/ticket/16700 Jun 05 20:52:30 http://pastebin.com/2iXjc2J5 Jun 05 20:53:11 "struct wpa_ssid *ssid = wpa_s->current_ssid;" is declared inside an ifdef and user later outside that ifdef on "wpa_supplicant_initiate_eapol" Jun 05 20:58:37 this problem is also in hostap upstream Jun 05 21:00:29 will take care of it Jun 05 21:15:39 nbd r41023 trunk/package/ (6 files) * hostapd: fix wpad-mini compile error (#16700) Jun 05 21:17:30 Hauke: night, in case of problem, mail me please Jun 05 21:25:35 hauke r41024 trunk/target/linux/ (6 files in 3 dirs) * brcm47xx: move current target to "generic" subtarget Jun 05 21:26:39 hauke r41025 trunk/target/linux/ (8 files in 3 dirs) * brcm47xx: add mips74k subtarget for newer devices Jun 05 21:34:13 hauke r41026 trunk/package/libs/openssl/Makefile * openssl: version bump to 1.0.1h Jun 05 21:47:21 hauke r41027 branches/attitude_adjustment/package/openssl/Makefile * AA: openssl: version bump to 1.0.1h Jun 05 23:08:31 <5EXAA8SU8> build #185 of mxs is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/185 Jun 05 23:34:54 <5EXAA8SU8> build #485 of adm5120 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/485 Jun 05 23:35:30 nbd r41028 trunk/package/kernel/mac80211/patches/562-ath9k_ani_ws_detect.patch * ath9k: add a fix for ANI related stability issues Jun 05 23:35:34 nbd r41029 trunk/package/kernel/mac80211/patches/563-ath9k_rxorn_intr_fix.patch * ath9k: add a fix for rx overrun processing Jun 05 23:43:30 <5EXAA8SU8> build #621 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/621 Jun 06 00:31:46 <5EXAA8SU8> build #544 of ixp4xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/544 Jun 06 00:46:38 <5EXAA8SU8> build #533 of ar71xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/533 Jun 06 01:03:29 <5EXAA8SU8> build #642 of brcm47xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/642 Jun 06 02:48:57 <5EXAA8SU8> build #585 of ar7 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/585 **** ENDING LOGGING AT Fri Jun 06 03:00:00 2014