**** BEGIN LOGGING AT Fri Dec 05 07:45:08 2008 Dec 05 10:39:55 juhosg * r13523 /trunk/target/linux/ar71xx/files/drivers/net/ag71xx/ (ag71xx.h ag71xx_main.c): [ar71xx] ag71xx driver: don't use dma_cache_wback_inv Dec 05 13:42:24 does anybody know an alternate firmwarew for thecus n1200? Dec 05 13:42:28 help please Dec 05 13:42:54 or is it possible to flash kamikaze on this device? Dec 05 13:43:41 Did you check out the Table of Hardware ? Dec 05 13:44:19 The N2100 is the one you can run anything on Dec 05 13:47:07 http://git.foonas.org/?p=kernel-n1200.git;a=summary if there is a kernel openwrt should be not too hard Dec 05 13:52:53 but there are no flashing instructions Dec 05 13:53:14 because we're not done with the firmware yet perhaps?.... Dec 05 13:53:51 when will it be ready? Dec 05 13:53:57 :( Dec 05 13:54:02 When it's ready... Dec 05 13:55:45 Is /etc/init.d/fstab running before USB drives are recognized a known bug for 8.09? Is it a wontfix? Dec 05 13:57:13 are there any flashing instructions for the foonas-em firmware on thecus n1200? Dec 05 13:59:38 ... Dec 05 13:59:45 14:52 < mib_0dliy3> but there are no flashing instructions Dec 05 14:02:26 mib_xy28xk: Google wasn't your friend on this one, so what makes you think we will be? Dec 05 14:02:59 i read somwere that was flashed Dec 05 14:03:16 i know it can be done but i don't know how Dec 05 14:55:38 any tutorials to modify patches for using with wrt Dec 05 14:59:42 any tutorials to modify patches for using with wrt Dec 05 16:39:03 any VOX users out there? Dec 05 16:47:41 define VOX ? Dec 05 17:01:04 NAS box from http://www.voxtechnologies.com/. http://www.geeks.com/details.asp?invtid=ENPA-35N-V1K&cat=NET Dec 05 17:03:03 probably a horrible chipset with too little ram/flash to run linux Dec 05 17:10:44 it's a 300MHz arm9 from cortinasystems Dec 05 17:11:12 see http://www.cortina-systems.com/products/view/73 Dec 05 17:17:18 the geeks boxes are an older version of http://voxproducts.com/n1.php# Dec 05 17:18:23 I'm looking into doing a port. anyone else interested let me know Dec 05 17:34:22 mhh, can someone help me to find out how much storage this RAM has? Mira P2V64S40ETP-G6 I found the datasheet, 64mb possible? o.0 on a small router.. Dec 05 19:42:19 juhosg * r13524 /trunk/target/linux/ar71xx/files/drivers/net/ag71xx/ag71xx.h: [ar71xx] ag71xx driver: always flush register writes Dec 05 20:08:03 juhosg * r13525 /trunk/target/linux/ar71xx/files/drivers/net/ag71xx/ (ag71xx.h ag71xx_main.c): [ar71xx] ag71xx driver: improve poll routine Dec 05 21:18:59 Okay, just looking in to usb storage for brcm-2.4 Dec 05 21:20:02 /sbin/usb-storage relies on sys to do its' job Dec 05 21:20:22 Which rules out working on 2.4 Dec 05 21:20:28 there's also /etc/config/fstab Dec 05 21:20:56 and /etc/fstab (/etc/config/fstab) won't work, because it's called before kernel modules for usb are inserted Dec 05 21:20:57 but there's the problem that the corresponding init script runs too early for usb media Dec 05 21:21:21 xMff: It is known and reported? Anyone workong in it? Dec 05 21:21:22 you could try to execute it later Dec 05 21:21:26 s/workong/working/ Dec 05 21:21:44 or should I take a stab at a fix Dec 05 21:21:58 kupesoft: that won't hurt Dec 05 21:22:20 ideally /sbin/usb-storage should both support 2.4 and 2.6 and take /etc/config/fstab into account Dec 05 21:22:49 currently its broken on 2.6 AND ignored /etc/config/fstab Dec 05 21:22:52 It'd kind of a crude script ;p Dec 05 21:22:58 (/sbin/usb-storage) Dec 05 21:23:18 xMff: ignore /usb-storage Dec 05 21:23:25 i will merge mountd hopefully this weekend Dec 05 21:23:47 heh okay... Dec 05 21:23:52 but that need autofs4 Dec 05 21:23:58 which means no 2.4 Dec 05 21:24:03 ... Dec 05 21:24:05 whih i am cool with :) Dec 05 21:24:44 Why not fix /etc/config/fstab Dec 05 21:25:13 add something like "option usb 1" Dec 05 21:26:18 so it's backwards compatible -- and if that flag's set, call another small init script after the usb storage kernel mods are inserted AND wait for discovery of a usb device with that name (timing out liberally) Dec 05 21:26:47 good idea for a ticket / patch or not ? Dec 05 21:28:51 hmm, you know what, usb kernel mods are inserted before /etc/init.d/fstab runs Dec 05 21:29:04 There's just some waiting for the disk to show up Dec 05 21:29:09 but devices take some seconds to become ready Dec 05 21:29:13 Yeah Dec 05 21:29:30 So what about a best guess in /etc/init.d/fstab about whether to wait for the device to come up Dec 05 21:29:38 blogic: so absolutely no way fpr 2.4 ? Dec 05 21:29:54 nope Dec 05 21:29:58 k Dec 05 21:30:02 well Dec 05 21:30:10 we could add older autofs support :) Dec 05 21:30:43 blogic: What about waiting an extra few seconds (say, max 5 or 10) in /etc/init.d/fstab if devices aren't up Dec 05 21:31:08 waiting only if it's detached Dec 05 21:31:16 otherwise it will block start up Dec 05 21:31:32 well Dec 05 21:31:32 & Dec 05 21:31:38 yeah Dec 05 21:31:39 Considering the alternatives, disks not being recognized, not such a bad thing tho Dec 05 21:31:49 Which is the way it currently works, Dec 05 21:32:03 i would suggest waiting and using & for it Dec 05 21:32:12 unless you wanna boot of one of the devices Dec 05 21:32:36 If you wanted to boot off the device /etc/fstab wouldn't be your place to set that up Dec 05 21:32:40 can hotplug handle appearing discs? Dec 05 21:32:57 at least on a broadcom device Dec 05 21:33:30 xMff: yes Dec 05 21:33:53 /etc/hotplug.d/block/ Dec 05 21:33:54 kupesoft: then the cleanest way would be to just write /etc/fstab with the init script Dec 05 21:34:11 then implement a hotplug handler that reads fstab and mounts once the disk is ready Dec 05 21:34:29 perfect Dec 05 21:34:59 you could just use auto and noauto Dec 05 21:35:06 or sth. similar Dec 05 21:37:57 Is a /etc/hotplug.d/block/10-fstab-mount look like something that could make its way in to trunk? Dec 05 21:38:07 s/Is/Does/ Dec 05 21:38:23 for brcm-2.4 anyway Dec 05 21:42:20 Anyone, anyone, going one, going twice... ;p Dec 05 21:56:28 blogic: /etc/hotplug.d/block/ don't work Dec 05 22:00:53 rebooted ? Dec 05 22:01:02 fixed up /etc/hotplug2.rules ? Dec 05 22:03:18 hmm Dec 05 22:03:23 blogic: you owe me an email :) Dec 05 22:05:34 blogic: You're the original author of /sbin/usb-storage -- approve of me hacking it up to work on 2.4, remove the /mnt/usbdrive support that only works for one disk, and get /etc/config/fstab (or possibly just /etc/fstab) info mount in relevant places Dec 05 22:06:01 whatever Dec 05 22:06:05 blogic: The hotplug call for usb-storage looks fine, no need to mess with that Dec 05 22:06:11 i will add mountd next week Dec 05 22:06:26 blogic: btw, I have some examples as to how I thought mounting could be done solely by hotplug2 rules... you may like to take a peek at'em Dec 05 22:06:42 blogic: After you do that, will /sbin/usb-storage be removed ? Dec 05 22:06:59 kupesoft: well Dec 05 22:07:04 if 2.4 needs it .... Dec 05 22:08:19 well no point in working on a patch if there's no chance of acceptance :( Dec 05 22:08:58 iSteve: can I see les exemples? Dec 05 22:09:26 https://svn.nomi.cz/svn/isteve/hotplug2/docs/rules/ Dec 05 22:09:46 ok Dec 05 22:10:12 (will only work with current svn / 1.0-alpha) Dec 05 22:10:21 well Dec 05 22:10:26 that is no automount Dec 05 22:10:30 well Dec 05 22:10:43 it moutns automatically yes, but autofs is something different Dec 05 22:11:05 iSteve: yeah that looks spot on, KISS Dec 05 22:11:05 well... I didn't propagate it as autofs:) Dec 05 22:11:31 anyway, it's just a demo, you guys deploy it as you deem fit of course Dec 05 22:11:57 mountd is similar to on Solaris or AIX right ? Dec 05 22:13:32 dunno Dec 05 22:13:45 rpc thing for mounting filesystems Dec 05 22:13:48 mountd mounts on access and after a timeout unmoiunts Dec 05 22:13:56 h3sp4wn: yeah Dec 05 22:14:01 using netlink Dec 05 22:14:02 no Dec 05 22:14:06 pipes Dec 05 22:15:31 [florian]: Any news on bcm63xx? Dec 05 22:39:09 noz: ping **** ENDING LOGGING AT Sat Dec 06 02:59:57 2008