**** BEGIN LOGGING AT Thu Oct 29 02:59:57 2009 Oct 29 10:43:16 florian * r18198 /trunk/target/linux/generic-2.6/patches-2.6.31/082-mtd_info_move_forward_decl.patch: [kernel] move the forward declaration of struct mtd_info, prevents build failures on arm and mips Oct 29 10:55:54 florian * r18199 /trunk/target/linux/generic-2.6/patches-2.6.31/032-mips_vmlinux_lds.patch: [kernel] fix build failure on vmlinux.lds with 2.6.31 (#6052) Oct 29 10:59:48 florian * r18200 /packages/lang/luasocket/Makefile: [package] fix luasocket compilation failures (#6065) Oct 29 12:20:46 florian * r18201 /trunk/ (4 files in 4 dirs): [kernel] remove support for 2.6.27, no target is using it anymore Oct 29 12:22:55 florian * r18202 /trunk/package/ (6 files in 2 dirs): [package] remove references to 2_6_27 Oct 29 12:51:47 blogic * r18203 /trunk/target/linux/ramips/files/drivers/net/ramips.c: [ramips] hopefully fixes dma issues seen on ethernet driver when under high load Oct 29 13:39:30 florian * r18204 /trunk/target/linux/brcm63xx/image/Makefile: [brcm63xx] do not generate trx images, this is useless Oct 29 14:53:19 florian * r18205 /packages/libs/gnutls/Makefile: [package] explicitely disable guile bindings in libgnutls Oct 29 15:48:37 florian * r18206 /trunk/target/linux/at91/image/dfboot/Makefile: [at91] fix dfboot linking failures (#5937) Oct 29 16:00:49 florian * r18207 /trunk/target/linux/at91/image/u-boot/patches/015-eabi_fixes.patch: [at91] fix u-boot linking failure with an EABI toolchain Oct 29 16:03:17 florian * r18208 /trunk/target/linux/at91/ (base-files/sbin/ image/u-boot/Makefile): [at91] fix u-boot installation Oct 29 16:50:47 florian * r18209 /packages/lang/ (luafilesystem/Makefile luaprofiler/Makefile luasec/Makefile): [package] fix lua programs by adding missing std=gnu99 cflag Oct 29 16:54:06 ping florian Oct 29 16:55:26 [florian]: ^ Oct 29 16:55:29 <[florian]> cshore: pong Oct 29 16:56:37 florian: hi. I saw in your email to Marc you wanted to coordinate with me about the GPIO button? Oct 29 16:56:50 <[florian]> cshore: indeed Oct 29 16:57:05 <[florian]> cshore: did you try the current code which registers kmod-input-gpio ? Oct 29 16:57:32 cshore: The last time I tried was before we had the info from Tecom Oct 29 16:58:07 <[florian]> ok, so now that you have the pinout, does it work better? Oct 29 16:58:59 I didn't know how to make it do so....I don't know what code is needed Oct 29 16:59:28 <[florian]> basically you will need to indicate the right gpio in arch/mips/bcm63xx/boards/board_bcm963xx.c Oct 29 16:59:55 <[florian]> then the input-gpio driver will regularly poll this gpio in order to detect a state change Oct 29 16:59:59 <[florian]> and trigger an action accordingly Oct 29 17:03:57 do you know how to access the LED on the GW? Oct 29 17:04:20 <[florian]> unfortunately no, I tried using the standard broadcom led mapping, but this does not work apparently Oct 29 17:07:09 Hmm...Power has not GPIO and WLAN LNK&ACT are from the BRCM4318....does that mean anything to you? Oct 29 17:07:54 <[florian]> yes, that means that we might potentially control the wlan led using the bcm4318 gpios Oct 29 17:08:01 <[florian]> but I remember that these were not directly accessible Oct 29 17:08:17 its 0 and 1 on the bcm4318 according to Tecom Oct 29 17:08:48 the WAN is from the BRCM6438 and they say EPHY_LNK_ACT_LED_B, which means nothing to me Oct 29 17:10:05 <[florian]> I think that means the led is controlled by the PHY chip Oct 29 17:10:23 <[florian]> the PHY between the chip which converts ethernet frames into the right electrical signals on the RJ45 cable Oct 29 17:10:51 ok...is that enough information or do we need more from them? Oct 29 17:11:55 <[florian]> cshore: they should give you the gpio number they connected the button to Oct 29 17:12:21 the button is on 36 Oct 29 17:12:52 <[florian]> oh ok Oct 29 17:13:39 and lan are controlled by the switch and are LED[1-4]A on it, if that helps Oct 29 17:13:59 <[florian]> well yes that's not something we can easily interact with Oct 29 17:14:21 <[florian]> by the way, I noticed that kmod-switch can now drive the switch on the GW6000 Oct 29 17:14:26 ok, so ATM we really on have the WAN we can use Oct 29 17:14:40 cool....you mean vlan on the GW6000? Oct 29 17:14:47 <[florian]> maybe Oct 29 17:14:58 <[florian]> but I found it little buggy since it attached to eth0 and not eth1 Oct 29 17:15:43 hmmm...since it's a new kernel I should see if the vlan on the 6200 has been solved Oct 29 17:16:04 <[florian]> yes that would be interesting to test Oct 29 17:17:50 what's needed to access the LED on the PHY for the WAN? Oct 29 17:18:28 <[florian]> without much experience on it, I do not know Oct 29 17:18:56 <[florian]> I suppose that it can be accessed using some PHY registers, but I have not the doc of theses Oct 29 17:19:42 ok, I'll let Marc know we need more info from Tecom...otherwise we have no controllable LEDs Oct 29 17:20:04 <[florian]> excactly Oct 29 17:21:11 What the FXO / FXS, there on the VP101 chip, AGPO[3,4,5]=FXO[1,2,3], AGPIO[6] = FXS Oct 29 17:22:18 <[florian]> I do not understand your sentence sorry Oct 29 17:23:38 the FXO and FXS LEDs are controlled by the VP101 chip, and the GPIO mapping is AGPIO[3,4,5]=FXO[1,2,3] and AGPIO[6]=FXS. Does that help us any? Oct 29 17:24:08 <[florian]> this is the gpio mapping vp101-side I think Oct 29 17:24:59 they do say that those LEDs are controlled by the Tecom software Oct 29 17:25:41 <[florian]> they can be controlled by asking the vp101 to do it ;) Oct 29 17:25:50 the WLAN and WAN are marked as controlled by their respective chipsets, so I'm not sure if there is software control available Oct 29 17:25:58 ah? does that help us? Oct 29 17:26:13 <[florian]> I have no idea how to drive them easily Oct 29 17:26:49 sorry I mean the VP101 stuff...or is that a case of needing VP101 register info? Oct 29 17:27:00 <[florian]> it does yes Oct 29 17:28:05 so you could drive the VP101 LEDs? Oct 29 17:30:22 <[florian]> knowing the register layout, certainly Oct 29 18:03:42 root@OpenWrt:/# swconfig dev eth0 get ports Oct 29 18:03:42 swlib_priv_init(542): Switch API not present Oct 29 18:03:42 Failed to connect to the switch Oct 29 18:04:23 nbd: any clue why that happens? Oct 29 18:06:28 sn9: the phy driver does not szupport swconfig Oct 29 18:06:50 as in, libphy? Oct 29 18:08:54 what device? Oct 29 18:11:23 nbd: i got the switch-robo.ko to activate on the wrt350n; it just can't be configured Oct 29 18:11:36 switch-robo.ko does not use swconfig Oct 29 18:11:37 previously, it refused to load Oct 29 18:11:40 it's based on the old /proc stuff Oct 29 18:11:45 oh Oct 29 18:11:52 what configures that? Oct 29 18:12:02 a script in /lib/switch/ Oct 29 18:12:09 or you can configure it manually Oct 29 18:12:30 i don't have a /lib/switch Oct 29 18:12:50 it should be included with the switch-core package Oct 29 18:12:57 nope Oct 29 18:13:05 oh, wait Oct 29 18:13:10 it's /lib/network/switch.sh Oct 29 18:13:10 sorry Oct 29 18:13:18 i have a tendency to forget details about legacy crap ;) Oct 29 18:13:27 which is healthy, i guess Oct 29 18:14:27 ok Oct 29 18:17:53 florian * r18210 /packages/utils/screen/ (Makefile files/ files/etc/ files/etc/screenrc): [package] provide a screenrc (#5958) Oct 29 18:19:08 florian * r18211 /packages/ (mail/imapfilter/Makefile net/prosody/Makefile): [package] fix more std=gnu99 lua related packages Oct 29 18:22:05 nbd: did switch-robo.ko ever work in the least? Oct 29 18:22:14 sure Oct 29 18:22:30 dunno if it worked on the wrt350n, though Oct 29 18:22:47 what did it work on? Oct 29 18:23:06 basically all of the standard 11g broadcom hw with broadcom switches Oct 29 18:24:42 was that a 5325? Oct 29 18:24:52 yes Oct 29 18:25:00 it reports a 5397 for the wrt350n Oct 29 18:25:06 yeah, i know Oct 29 20:51:15 can someone please review this patch for commit? http://openwrt.pastebin.com/f39719a96 Oct 29 20:51:44 it finally makes the ethernet work oob on the wrt350n Oct 29 20:52:28 and it fixes an incorrect package dep Oct 29 20:57:18 nbd: ? Oct 29 20:59:37 sn9: i woul dcheck for existence of tg3 before the insmod Oct 29 20:59:47 ?! Oct 29 21:00:43 blogic: what would be the harm if it's not there? just an extra line in dmesg Oct 29 21:01:07 yes Oct 29 21:01:13 tg3 must load before switch-robo, loaded below, and after diag Oct 29 21:01:20 that means we get a bug report saying bogus error Oct 29 21:01:43 well, ok Oct 29 21:08:13 blogic * r18212 /trunk/target/linux/ramips/files/drivers/net/ramips.c: [ramips] fixes rx path for eth, spinlock it, increases buffer size, board now survives ping -f Oct 29 21:09:40 blogic: revised patch: http://openwrt.pastebin.com/f6920baa6 Oct 29 21:12:03 nbd needs to ack the switch patch Oct 29 21:12:07 soz Oct 29 21:13:34 the patch is still missing some of the code for 5398 switches, because i can't test that Oct 29 21:15:11 also, i don't have a reference to fix the vlan state reading, so that's still broken; however, it's relatively unimportant, since it doesn't work under 2.4, either Oct 29 21:18:49 ack for the patch, though it should be split up into the switch/failsafe part and the dependency fix Oct 29 21:19:06 sn9: split it up and i can commit it Oct 29 21:19:46 you can apply it, then split the commits Oct 29 21:19:57 svn allows that Oct 29 21:21:00 :) Oct 29 21:21:03 of course :) Oct 29 21:22:41 what commit messaegs ? Oct 29 21:23:24 up to you Oct 29 21:23:31 package/kernel/modules/other.mk seems a third patch ?! Oct 29 21:23:41 no, that's the dep fix Oct 29 21:23:50 ah k Oct 29 21:23:54 the other two files go together Oct 29 21:24:14 ? Oct 29 21:24:48 how does bluetooth relate i dont get it Oct 29 21:25:03 it doesn't; that's the second patch Oct 29 21:25:23 ahhh Oct 29 21:25:57 blogic * r18213 /trunk/package/kernel/modules/other.mk: fixes bluetooth dependency, thx sn9 Oct 29 21:26:38 blogic * r18214 /trunk/ (2 files in 2 dirs): make etehrent work on wrt350n, thx sn9 Oct 29 21:26:46 done Oct 29 23:34:41 florian * r18215 /trunk/target/linux/olpc/image/Makefile: [olpc] ext2 images need to wait for /dev/sda2 to appear before attempting to mount it, fixes olpc boot on ext2 images Oct 29 23:35:55 florian * r18216 /trunk/target/linux/olpc/image/olpc.fth: [olpc] make the kernel also output on ttyS0 and ask openfirmware to unfreeze the screen Oct 29 23:42:14 florian * r18217 /trunk/toolchain/insight/Makefile: [toolchain] update insight to 6.8-1 (#6007) Oct 30 00:29:54 ready for commit: http://openwrt.pastebin.com/f72bfd46f Oct 30 00:31:54 [florian]: since you seem to be around, ^ Oct 30 00:39:11 i guess he's not around... Oct 30 00:45:48 Bartman007: time zones being what they are, you're likely to the only committer awake for some hours Oct 30 00:47:22 *to be Oct 30 01:05:08 ejka: do you still have commit access? Oct 30 01:05:39 thepeople * r18218 /trunk/target/linux/brcm47xx/profiles/WRT350Nv1.mk: add WRT350Nv1 target, thanks sn9 Oct 30 01:05:49 thepeople: thx Oct 30 01:05:55 sn9: np Oct 30 01:07:04 thepeople: you cut off a ) Oct 30 01:07:18 at the end Oct 30 01:07:23 doh Oct 30 01:07:46 pastebin has "download this" links, ya know Oct 30 01:08:13 thepeople * r18219 /trunk/target/linux/brcm47xx/profiles/WRT350Nv1.mk: fix my typo Oct 30 01:08:14 I know Oct 30 01:08:23 for whatever reason patch didn' Oct 30 01:08:28 t like your patch Oct 30 01:09:24 i generated with "svn diff" Oct 30 01:09:49 eitherway it is committed and fixed now Oct 30 02:33:37 russell_: you around? **** ENDING LOGGING AT Fri Oct 30 02:59:58 2009