**** BEGIN LOGGING AT Thu Jan 24 02:59:58 2013 Jan 24 03:02:54 build #139 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/139 Jan 24 03:03:31 build #162 of atheros is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/162 Jan 24 03:10:48 build #144 of ar7 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/144 Jan 24 05:21:59 build #161 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/161 Jan 24 06:41:42 build #167 of brcm63xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/167 Jan 24 06:59:53 build #155 of cobalt is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/155 Jan 24 07:49:42 build #154 of lantiq is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/154 Jan 24 07:54:55 build #124 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/124 Jan 24 09:12:02 build #151 of x86 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/151 Jan 24 09:17:26 build #121 of gemini is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/121 Jan 24 09:58:36 Ralf: wb Jan 24 09:59:09 blogic: inv Jan 24 10:00:16 <[florian]> ah ah Jan 24 10:13:56 build #145 of ar7 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/145 Jan 24 10:31:08 <__trine> on phone Jan 24 11:03:50 <__trine> http://dpaste.com/889902/ Jan 24 11:31:27 build #141 of xburst is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/141 Jan 24 11:37:13 jow r35312 packages/net/ (5 files in 2 dirs) * ipsec-tools: fix compilation against Linux 3.7, refresh patches Jan 24 11:42:52 cyrus r35313 packages/ipv6/6scripts * Kill obsoleted 6scripts Jan 24 12:14:38 have there really been no devices with working voip hardware in owrt that have more than 8M flash?? Jan 24 12:22:38 DonkeyHotei: there is but i doubt you can get it... Jan 24 12:23:01 lantiq demo boards have more then 8mb flash iirc Jan 24 12:23:54 luka: what do you know of such? Jan 24 12:24:47 i know that they exist Jan 24 12:25:24 there seems to be no mention of them in the owrt source tree Jan 24 12:26:12 are they danube? Jan 24 12:29:35 luka: are they sample dev boards from lantiq? Jan 24 12:33:56 DonkeyHotei: yes, but they cost a fortune Jan 24 12:34:14 i see Jan 24 12:34:34 i'm curious what they have on them Jan 24 12:34:49 quite a big nand chip Jan 24 12:34:59 wifi? Jan 24 12:35:03 there are some unsupported devices that have more than 8 MB RAM (e.g. the fritzbox 7360 has 16 MB) Jan 24 12:35:22 flash, not ram Jan 24 12:35:29 I mean falsh Jan 24 12:35:30 *flash Jan 24 12:36:17 the bt homehub v2b is supported and has more flash, but i don't think voip works on it AFAICT Jan 24 12:41:12 KanjiMonster: any that are moddable to have additional internal storage? Jan 24 12:41:23 no idea Jan 24 12:42:38 because i'm wondering what i could get besides yet another sx762 or if i could give it more storage somehow Jan 24 12:43:19 the sane-libs pkg alone is 3MB so it can't really be used in 8MB Jan 24 12:45:49 luka, KanjiMonster: ^ Jan 24 13:38:34 DonkeyHoyei: I once setup saned and p910d on a TL-WR1043ND to share a USB OfficeJet. clients would use cups and xsane net plugin to use it Jan 24 13:39:22 hotplug- or input-triggered saneimage and safe via samba would need more flash or extroot though, i guess. Jan 24 13:46:38 dangole: exactly my point Jan 24 13:47:07 but the device has to have fxs in this case Jan 24 13:48:09 also, are there any network scanner clients for windows? Jan 24 13:48:53 there is an xsane client for windows afaik, there even at least was a TWAIN-SANE wrapper... Jan 24 13:49:09 awesome Jan 24 13:49:48 i'm assuming this is what you did: http://zagrodzki.net/~sebek/openwrt/ Jan 24 13:50:58 similar to this, yes Jan 24 13:51:10 by the end of the day, it's often more useful to have the scanner's button trigger a safe-to-samba-share or attached samba-accessible storage Jan 24 13:51:36 most scanner have hid buttons Jan 24 13:54:24 i think twain-sane or at least an xsane client makes more sense, but either way, sane-libs is a 3MB pkg Jan 24 14:00:53 yeah, probably it would make sense to split it up, so one could install only the plugins "dlls" actually needed Jan 24 14:02:06 not gonna happen in AA Jan 24 14:27:49 <__trine> DonkeyHotei, you were up early this morning Jan 24 14:28:27 yes Jan 24 14:29:13 <__trine> I see you have no further joy with your project Jan 24 14:29:48 <__trine> the dockstar + SPA 3102 is not a bad alternative Jan 24 14:31:33 <__trine> and if anything went wrong with freeswitch or openwrt you could have a copy on a replacement pendrive which could be easily swapped Jan 24 14:32:11 <__trine> and you could have a nice gui for FS fusionpbx Jan 24 14:32:26 that would mean the wifi would need to be on a usb stick Jan 24 14:32:39 usb sucks as an ap Jan 24 14:32:44 <__trine> yes it would Jan 24 14:32:53 so, no go Jan 24 14:33:12 <__trine> or Jan 24 14:33:33 <__trine> you could connect the dockstar to a small tplink router Jan 24 14:33:41 <__trine> and have the best of all worlds Jan 24 14:34:07 <__trine> or even a very nice wndr3800 Jan 24 14:34:09 <__trine> :) Jan 24 14:34:26 that's four devices altogether, if you add the docsis modem Jan 24 14:34:40 there are space and power constraints Jan 24 14:34:49 <__trine> my dockstar works very well with FS running in a pendrive connected to my wndr3700 Jan 24 14:35:05 <__trine> its not the space shuttle is it Jan 24 14:35:16 <__trine> these things are small Jan 24 14:35:54 and as i said, the sx762 is $23.75 while i'd have to buy three separate devices otherwise, each individually exceeding that Jan 24 14:36:07 <__trine> a tp-link 3034 and a dockstar will fit in the palm of your hand Jan 24 14:36:41 <__trine> well now you are bringing in another part of the equation if it has to be cheap as well Jan 24 14:36:50 can they all be powered off the dockstar's usb? Jan 24 14:37:03 <__trine> you often just get what you pay for Jan 24 14:37:29 <__trine> I would think the tp3034 could be Jan 24 14:37:43 <__trine> you would have to check Jan 24 14:37:57 the wndr costs an insane amount of money Jan 24 14:38:12 <__trine> that was tongue in cheek Jan 24 14:38:24 <__trine> I knew you would not buy one of those Jan 24 14:38:40 not for this i wouldn't Jan 24 14:39:04 <__trine> a secondhand spa3102 is normally less than $20 Jan 24 14:39:25 hauke r35314 trunk/target/linux/ (17 files) * brcm47xx: change generic profiles Jan 24 14:39:42 if it were for a large network without built-in fxs needs, wndr would be my pick, but not for this Jan 24 14:39:46 <__trine> a dockstar can be any price from $20 to $60 Jan 24 14:40:19 <__trine> a new SPA 3102 is about $35 Jan 24 14:40:50 sipura dial plans are a pain in the butt; i'd rather deal with * directly Jan 24 14:41:38 it would be nice if freeswitch could use lantiq voip, but atm it can't Jan 24 14:41:44 <__trine> they are not bad once you understand them Jan 24 14:42:01 i understand them pretty well Jan 24 14:42:10 they are poorly designed Jan 24 14:45:07 <__trine> thats like a verbal trap "sipura dial plans are a pain in the butt" + "i understand them pretty well" Jan 24 14:45:13 <__trine> :) Jan 24 14:45:55 <__trine> anyway I need to go and do something else see you later Jan 24 14:47:58 "i'd rather deal with * directly" Jan 24 14:49:27 hauke r35315 trunk/target/linux/generic/config-3.8 * kernel: add missing config options for 3.8 Jan 24 16:27:01 build #112 of octeon is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/112 Jan 24 17:04:41 build #123 of mcs814x is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/123 Jan 24 17:06:01 florian r35316 trunk/target/linux/ mvebu/patches-3.8/035-arm_mvebu_the_core_pcie_driver.patch mvebu/Makefile * mvebu: update to 3.8-rc4 Jan 24 17:06:04 florian r35317 trunk/target/linux/ (6 files) * kernel: refresh 3.8 patches Jan 24 17:09:49 juhosg r35318 trunk/ (13 files in 13 dirs) * kernel: update linux 3.7 to 3.7.4 Jan 24 18:08:14 RT3883-based router: out for devilery \o/ Jan 24 18:09:12 what time zone are you in? Jan 24 18:09:23 zinx: which one ? Jan 24 18:09:41 blogic: Edimax BR-6475nD Jan 24 18:10:00 blogic: i do plan on adding support if it's not in git (i checked out the 12.xx branch) Jan 24 18:10:05 erh, svn Jan 24 18:10:28 if you want to add support, it should go in trunk, not 12.xx Jan 24 18:10:29 btw, how frequently are those sync'd? i would rather use git, but if they aren't sync'd on commit it would be a pain Jan 24 18:10:35 DonkeyHotei: i know Jan 24 18:11:00 nbd maintains the git mirror Jan 24 18:11:23 zinx: they're synced every 5 minutes or so Jan 24 18:11:29 i'd imagine he has a cron job of it Jan 24 18:11:32 jow_laptop: i can deal w/ that Jan 24 18:11:58 git-svn works well for me too, but the initial checkout takes a lot of time Jan 24 18:12:05 hehe Jan 24 18:12:46 i stopped using svn a while ago, should probably look at the interoperability tools available Jan 24 18:13:30 hmm yeah, i'll use git-svn Jan 24 18:13:56 I mean in the end you have to send patches to the list using git-send-email Jan 24 18:14:08 whether your commits are based on a git-svn clone or nbd's mirror doesn't really matter Jan 24 18:14:24 s/have to/should/ Jan 24 18:21:54 i use svn because i'm more familiar with it Jan 24 18:23:19 once you switch to git you never go back ;D Jan 24 18:27:05 build #127 of adm5120 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/127 Jan 24 18:27:18 git sucks Jan 24 18:27:25 Jan 24 18:28:16 zinx: it's too different for me to acclimate so far Jan 24 18:29:21 i can understand that Jan 24 18:29:45 if you have the time though, i'd recommend learning it - even if you decide not to use it, it's good to know how in the open source community :) Jan 24 18:30:19 i'm well aware of that Jan 24 18:30:48 i wanted to use github's svn frontend but it's really not up to par Jan 24 18:31:47 certain features of their site are accessible only through a git client Jan 24 18:31:54 not even over the web Jan 24 18:33:03 if owrt ever dumps svn, i'd recommend github for it Jan 24 18:56:09 hi guys, a doubt: some packages were touched since the AA was branched, but didn't had their PKG_RELEASE field bumped Jan 24 18:56:14 example: mac80211 Jan 24 18:56:46 so, it has plenty of updates (backports) that are never available as an upgrade to an user running an old AA Jan 24 18:57:04 is that a mistake? Jan 24 18:57:23 they are available if you rebuild from source Jan 24 18:57:57 I'm talking about via opkg (web update) Jan 24 19:02:44 pkg release is usually only touched if the binary outcome changes Jan 24 19:02:57 a compilation foix against a newer kernel for example does not require a pkg release change Jan 24 19:04:22 i'd recommend against using opkg to bring in AA fixes Jan 24 19:04:50 Hi, https://forum.openwrt.org/viewtopic.php?id=41860 Jan 24 19:05:31 jow_laptop, but patches were touched Jan 24 19:05:58 jwendell: got a specific example? Jan 24 19:06:08 mac80211 Jan 24 19:06:45 you cannot update kernel modules through opkg anyway Jan 24 19:07:07 why not? Jan 24 19:08:46 I mean, what's the problem in having this newer ath9k updated in the current kernel version? Jan 24 19:08:47 they have to match the kernel, which is inaccessible to opkg Jan 24 19:09:07 opkg force-depends Jan 24 19:22:01 opkg is limited to the filesystem, which the kernel is not in Jan 24 19:25:20 I'm talking about a kernel module (*.ko), which are packages, not the kernel itself Jan 24 19:25:43 they have to match the kernel, which is inaccessible to opkg Jan 24 19:58:15 jow_laptop: i think the PKG_RELEASE bumping is mostly useless Jan 24 19:58:27 argh, tab completion Jan 24 19:58:32 meant jwendell, but he's already gone ;) Jan 24 20:40:14 nbd: imho it has informational value Jan 24 21:05:15 any feedback on my alix2 (update to 3.7) patches? http://patchwork.openwrt.org/patch/3212/ and http://patchwork.openwrt.org/patch/3213/ (the latter needs updating to 3.7.4 now) Jan 24 22:09:39 build #143 of avr32 is complete: Failure [failed compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/143 Jan 25 01:19:11 build #158 of ppc40x is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/158 Jan 25 01:47:55 build #168 of brcm63xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/168 Jan 25 01:51:10 build #159 of ramips is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/159 Jan 25 01:52:29 build #150 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/150 Jan 25 02:02:32 build #150 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/150 Jan 25 02:29:21 build #155 of uml is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/155 Jan 25 02:37:17 build #166 of brcm47xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/166 Jan 25 02:40:45 build #140 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/140 **** ENDING LOGGING AT Fri Jan 25 02:59:58 2013