[11:26] florian: any ideas on this https://dev.openwrt.org/ticket/1690 maybe? [11:28] <[florian]> jb24: some yes [11:29] <[florian]> jb24: I have to check something [11:29] please [11:30] [florian], kamikazi needs compiled, or are there 'snapshot' builds available? [11:31] florian: i think it's some sort of compiler code optimization ... which let the kernel hang there... [11:31] <[florian]> jb24: I wonder if there is not clock-specific settings when you have a different SoC revision [11:32] the -2.4 means 2.4 kernel? [11:33] I can flash the .bin file from the linksys web config? Or is there a better way of doing it? [11:34] you can, Cisien, but you should now how to recover from a failure [11:34] that's why other methods are recommended, just so you know you can do them [11:34] florian: i have tnetd 7200 cpu [11:34] # cat /proc/cpuinfo [11:34] system type : MIPS OHIO [11:34] processor : 0 [11:34] cpu model : MIPS 4KEc V4.8 [11:34] BogoMIPS : 211.35 [11:34] wait instruction : yes [11:34] microsecond timers : yes [11:34] tlb_entries : 16 [11:34] extra interrupt vector : yes [11:34] hardware watchpoint : yes [11:34] VCED exceptions : not available [11:34] VCEI exceptions : not available [11:34] * You were kicked by wrt (flood) Session Close: Fri May 18 11:34:28 2007 Session Start: Fri May 18 11:34:43 2007 Session Ident: #openwrt [11:35] <[florian]> jb24: use a pastebin instead, the bot has some channel flooding protection [11:36] florian: as far as i heard so while many users have this problem with the tnetd 7200 and 7300 cpu [11:37] florian: sorry, ok will use pastebin next time .... [11:37] <[florian]> jb24: no problem, it's for you ;) [11:37] <[florian]> jb24: I think that using volatile for hardware programming is pretty difficult to manage, and this changeset has changed that [11:37] i really don't understand why MS isn't releasing DX10 for XP [11:38] florian: do you have a suggestion to fix this? [11:39] <[florian]> jb24: try to revert the changeset that make it broken [11:39] <[florian]> I will try to tell you which one [11:43] florian: r7118 will not work, hydra tested it [11:44] <[florian]> jb24: you mean 7119 ? [11:46] <[florian]> jb24: ok, I see what you mean, well, this means that tned7200/7300 needs specific initialisations [11:46] <[florian]> jb24: you can see that with ejka [11:52] florian: http://pastebin.ca/494561 [11:53] florian: i am trying to contact ejka but without luck :( [11:54] <[florian]> ok, I will give him a word then [11:55] <[florian]> volatile is considered bad by the kernel developpers themselves ;-) [11:55] florian: can you give him a wink on https://dev.openwrt.org/ticket/1690? [11:55] <[florian]> yep [11:55] ok thanks [11:57] florian: i think fixing this bug, will pushing the ar7 port the right and openwrt could be used on ar7 based (tnetd7200,7300) devices [11:58] *could be used more [11:58] *the right way [11:58] <[florian]> sure, this the DSL platform we are recommending [11:58] damn typos [11:58] <[florian]> bcm963xx is too crappy and close source [11:58] sorry [12:02] florian: about closed source... the t-com speedport 900v is a avm oem product has dect support and avm only delivers a compiled binary module without sources... :( [12:03] thats bad, it would be great if i could use all the features: voip, dect with openwrt [12:03] <[florian]> yes this would be great, reverse engineering those kind of drivers will be hard [12:05] any experience with it [12:05] ? [12:06] and i think we could not load the module on the new kernel right? [12:06] they have used 2.6.13.1 [12:07] <[florian]> well with CONFIG_MODVERSIONS disabled we might be able to load it anyway, but not sure it will work [12:07] <[florian]> have to go, see you later [12:08] what do you think? asking avm/t-com for the sources ... [12:09] jb24, you won't get sources from AVM. Secondly, even if you get the kernel module loaded, you still need an application to make use of it. [12:09] ...but i think the don't will publish them for the binary modules [12:11] they published the sources for the firmware and the kernel ... but not for the dect, isdn and voip bin modules [12:12] * bullet has joined #openwrt [12:12] Maybe they cannot publish the code because they don't own it? At least this has been the case with the early versions of the VLYNQ code, which they used from TI back then. [12:14] its published under the gpl... am i wrong? they must publish the code from the modules also..? [12:15] No, they don't have to publish the code of the module if it's not based on someone else's GPL code. I doubt that the DECT or ISDN code is based on GPL code because - after all - ISDN and DECT are AVM's core field of activity ;-) [12:16] pogo123: the dect just sits on the internal S0 [12:17] jb24: know if anyone has got a shell on the 900 without openning it / reflashing it? [12:18] murb, that fits into the scheme. ISDN is what AVM knows best. The number of DECT chipsets on the market with an open hardware interface is very limited. [12:19] I think Thomson has a USB DECT chip, but they don't sell it to OEMs. [12:20] i await devices that have UMTS cells. [12:20] (they are being developed) [12:20] UMTS cells? [12:20] well base stations. [12:20] so you can use your hand [12:20] y [12:21] Cisien_: as in gsm++ [12:22] pogo123: oh are they using it in their homebase whatever they are called things? (thomson)