**** BEGIN LOGGING AT Sat Jan 24 02:59:57 2009 Jan 24 03:02:23 On current trunk, can someone confirm that " make CONFIG_ATH9K_DEBUG=y V=99" fails? Am i doing something wrong? Jan 24 11:19:13 nbd * r14166 /tags/8.09_rc2/: tag 8.09 rc2 Jan 24 11:41:09 nbd * r14167 /branches/8.09/package/opkg/files/opkg.conf: adjust opkg url for final release Jan 24 15:47:09 lars * r14168 /trunk/rules.mk: Use multi libc naming scheme for PACKAGE_DIR Jan 24 16:15:32 lars * r14169 /packages/ (4 files in 3 dirs): Update alsa-lib and alsa-utils to 1.0.19 Jan 24 17:05:27 hi Jan 24 17:05:33 hey Jan 24 17:05:57 does someone know how the modify the patch statement for some files inside the makefile? i need -p2 instead of -p1 ... Jan 24 17:06:30 files=patches Jan 24 17:07:50 why do you need p2? can't you convert the patches? Jan 24 17:09:59 nbd okay thought maybe there is a way to use them direct ... this are bash patches ... and the offical patches are released as -p2 patches Jan 24 17:11:46 puchu: i'm sure you can prepare the patches with a simple sed command Jan 24 17:12:10 im also sure ;) Jan 24 19:13:58 hi Jan 24 19:14:08 Anyone around that can tell me how to get access to close or otherwise change the state of bugs? Jan 24 19:14:09 welcome to #openwrt-devel! Jan 24 19:15:28 A lot of the bugs are irrelevant or have a patch attached that needs to be reviewed and applied or dropped. Jan 24 19:15:48 wt: i read what you wrote in #openwrt Jan 24 19:15:54 ah Jan 24 19:16:01 personally i'm not responsible but will redirect that to the others Jan 24 19:16:12 *not responsible for the trac-stuff Jan 24 19:16:14 I was told to come here. Jan 24 19:16:37 no you were not ;) It was a suggestion. Jan 24 19:17:22 wt: the admin is not around right now Jan 24 19:17:40 s/.*/it was suggested I come here/ Jan 24 19:17:48 anyone using dlink dsl-2640b? Jan 24 19:18:11 I know that I have a documentation bug in there somewhere that hasn't been applied yet, also. Jan 24 19:18:24 Seems like those things would be pretty low hanging fruit. Jan 24 19:20:08 wt: date of the email? Jan 24 19:20:48 I filed a bug Jan 24 19:20:52 I am looking for it now Jan 24 19:21:11 I sent an email about it on 11/20/08 Jan 24 19:21:51 Subject: [PATCH] Add documentation for passphrase option. Jan 24 19:22:18 I sent the mail to openwrt-devel Jan 24 19:23:08 ok, saw it Jan 24 19:23:33 wt: I think it isn't entirely clear how many people have x hours to spare on patch integration and such ;) It seems to me developers aren't sleeping, just don't have the extra time. Jan 24 19:24:14 yep - it's a situation which we don't know to handle yet Jan 24 19:24:22 I'd like to help triage and find the more important bugs. Jan 24 19:24:40 bug triage parties are good Jan 24 19:24:57 the trac has so many open bugs that it isn't useful Jan 24 19:25:28 Some were reported against Whiterussian and may not be useful anymore. Jan 24 19:26:18 sweet Jan 24 19:26:56 RoundSparrow1: I don't think they're sleeping. Jan 24 19:27:01 That's why I wanna help. Jan 24 19:27:28 I think that some processes could certainly be improved; like checking in code more frequently. Jan 24 19:27:44 pushing more patches upstream Jan 24 19:27:48 things like that Jan 24 19:28:21 One huge thing I saw was that someone ported the brcm43xx patches to 2.6.27 and it just got dropped. Jan 24 19:28:31 The patch was never incorporated Jan 24 19:29:03 and I think that's a shame because it will be much harder to port patches from 2.6.25 to the current Jan 24 19:29:06 oh, I could have used that Jan 24 19:29:46 I gave up trying to use a 2.6 kernel with brcm43xx hardware Jan 24 19:29:52 there are also things like the nvram not working in brcm43xx Jan 24 19:30:13 jb42: the 8.09RC release works fine in client mode. Jan 24 19:30:20 wt: you cannot simply apply patches as they fly in especially not critical ones like kernel updates, they most likely fix 3 devices and break 10 others Jan 24 19:30:23 yeah, need ap mode Jan 24 19:30:37 CyrusFF: I agree, but you can stage them Jan 24 19:30:43 something else didn't work too I think, maybe problems with asterisk, can't remember Jan 24 19:30:54 also for what reason do you need nvram? Jan 24 19:31:09 in other words add the files-(ver) and patches-(ver) to the repository, but don't change the LINUX_VERSION in the Makefile Jan 24 19:31:47 jb42: master mode in the new 80211 stack isn't in the 2.6 kernel from what I understand Jan 24 19:31:57 oh Jan 24 19:32:00 jb42: I've been told that it will likely make it into 2.6.29 Jan 24 19:32:17 cool Jan 24 19:32:31 CyrusFF: need nvram to turn boot_wait on Jan 24 19:32:43 guess I can take my time getting this new router to work Jan 24 19:32:44 wt: nvram on 2.6 is a "wontfix" Jan 24 19:32:52 missing kernel-side support Jan 24 19:33:18 it's not just a forgotten binary Jan 24 19:33:26 xMff: oh, was the 2.4 patch never ported? I saw nvram.c in the 2.6.25 files directory Jan 24 19:33:35 no it was never ported Jan 24 19:34:55 xMff: what is the nvram.c file in target/linux/brcm47xx/files-2.6.25/arch/mips/bcm47xx? I guess it's not being compiled :) Jan 24 19:35:56 Afaik it has only read support. Unfortunately you need to rely on some nvram info to configure various devices like the ethernet switch on the bcm47xx platform Jan 24 19:36:32 * jb42 wonders how and what to load on to his new dsl2640b Jan 24 19:36:46 btw. 2.6.28 is in preparation for brcm47xx as you can see in the repository Jan 24 19:37:05 CyrusFF: I saw Jan 24 19:37:16 CyrusFF: thanks for that! Jan 24 19:37:37 don't thank me I've nothing to do with the brcm stuff ;-) Jan 24 19:37:38 I really do appreciate what you all do...I just would like to help out a bit. Jan 24 19:38:42 BTW, here's a simple bug. https://dev.openwrt.org/ticket/2449 Jan 24 19:39:43 This bug has had a patch attached for 8 months. Jan 24 21:52:49 hello Jan 24 21:52:55 hi Jan 24 21:53:14 is md5 sum of compat-wireless source not updated?? Jan 24 21:54:04 which svn? Jan 24 21:54:45 latest Jan 24 21:54:50 oops wait Jan 24 21:54:53 maybe not Jan 24 21:55:06 14169 Jan 24 21:58:15 I ran into that too Jan 24 21:59:20 that's wierd Jan 24 21:59:24 I went back to 14153 with svn update -r 14153 Jan 24 21:59:24 ... Jan 24 21:59:47 is md5 or source changed? Jan 24 21:59:53 source Jan 24 22:00:12 I changed the makefile to have the new md5 but then the patches failed to apply Jan 24 22:00:24 so something's changed with the source distribution Jan 24 22:00:43 the distributions are often, almost everyday, I wonder if they did 2 in 1 day Jan 24 22:01:11 maybe Jan 24 22:01:19 but so many changes that the patches dont apply? Jan 24 22:01:24 yeah Jan 24 22:01:25 dunno Jan 24 22:01:56 there's a jan 24 distfile on the second mirror site Jan 24 22:02:00 wireless.kernel.org Jan 24 22:02:03 for the same filename/download md5sum should be same. question is did one of the downloads change? Jan 24 22:02:36 ..or md5 was not calculated corectly? Jan 24 22:03:08 maintainer would probably know what happened Jan 24 22:03:13 yup Jan 24 22:03:22 but nothing listed in the makefile, don't know much about this project Jan 24 22:07:18 anyway, 14153 compiles, dunno if it works Jan 24 22:10:54 I use kamikaze 7.09 on a wrt54g as router and pbx for sip phones with asterisk Jan 24 22:11:28 thinking of changing my internet connection to dsl and so get a dlink dsl-2640b, trying to get that working Jan 24 22:19:11 is juhosg here? anyone knows who that is? Jan 24 22:23:30 * jb42 wonders what the pinout of the console port is and if he needs level shifters Jan 25 00:24:49 lars * r14170 /feeds/efl/ecore/patches/ (. 010-fix-ecore-evas-linking.patch): Link ecore_evas against libX11. Jan 25 00:37:45 nbd * r14171 /trunk/package/madwifi/patches/ (6 files): madwifi: fix the long standing bug that is triggered by nodes getting a timeout on one vap, then moving to another **** ENDING LOGGING AT Sun Jan 25 02:59:58 2009