Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-11 Thread Eddi De Pieri
Hi again, asterisk: set debug output on console console = notice,warning,error,debug so, all software recognize correctly the correct port [Nov 11 15:08:06] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 0 detected event off hook [Nov 11 15:08:10] DEBUG[894]: chan_lantiq.c:835

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-11 Thread Luka Perkov
Hi Eddi, On Tue, Nov 11, 2014 at 04:10:30PM +0100, Eddi De Pieri wrote: asterisk: set debug output on console console = notice,warning,error,debug so, all software recognize correctly the correct port [Nov 11 15:08:06] DEBUG[894]: chan_lantiq.c:835 lantiq_dev_event_hook: on port 0

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-11 Thread Eddi De Pieri
On Tue, Nov 11, 2014 at 4:24 PM, Luka Perkov l...@openwrt.org wrote: Hi Eddi, I don't remember if that worked on owsip. But asterisk should support both channels. What about TAPI/0? I am unsure if we started naming the channels from 0 or 1... /* on asterisk user's side, we're using port

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-11 Thread Eddi De Pieri
it seems it work better in this way... chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%d, (c + 1)); I don't know so well asterisk programming... please let me know if it seems correct to you! Eddi On Tue, Nov 11, 2014 at 6:11 PM, Eddi De Pieri e...@depieri.net wrote:

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-11 Thread Luka Perkov
Hi Eddi, On Tue, Nov 11, 2014 at 07:11:13PM +0100, Eddi De Pieri wrote: it seems it work better in this way... chan = ast_channel_alloc(1, state, NULL, NULL, , ext, ctx, 0, c, TAPI/%d, (c + 1)); I don't know so well asterisk programming... please let me know if it seems correct to you!

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-11 Thread Eddi De Pieri
Hi Luka, For me is the same... just to compliant comment inside source code: /* on asterisk user's side, we're using port 1-2. * Here in non normal human's world, we begin * counting at 0. */ So you confirm that TAPI/%s,1 map both port0 and port1 to TAPI/1 and you can't use asterisk

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-11-10 Thread Eddi De Pieri
- tapidemo -d 1: (tapidemo-5.1.0.53) phone1 connected: [...] EASY80910: Detected event on channel 0: ID: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) [...] phone2 connected: EASY80910: Detected event on channel 1: ID: 0x2005 (IFX_TAPI_EVENT_FXS_OFFHOOK) Phone No 2: Event

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-21 Thread Eddi De Pieri
I've managed to get FXS working on my vgv7519 vr9 router using asterisk-chan-lantiq. busy/free tone ok chan-lantiq to sip ok sip to chan-lantiq to test. I need to do some other tests before start to release code for BB... Eddi ___ openwrt-devel

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-18 Thread Eddi De Pieri
Hi to all, about gpio... before starting tapidemo (or asterisk): gpio8: dir/in alt0/0 alt1/0 gpio34: dir/in alt0/0 alt1/0 gpio35: dir/in alt0/0 alt1/0 gpio36: dir/in alt0/0 alt1/0 after starting tapidemo (or asterisk): gpio8: dir/out alt0/1 alt1/0 gpio34: dir/out alt0/0 alt1/1 gpio35: dir/in

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-16 Thread Eddi De Pieri
Hi to all, by manually setting correcly gpio like on original board with devmem: root@OpenWrt:/# /etc/init.d/tapidemo start eth1 ITM version 0.0.0.27. Compiled for EASY80910 with FXO (Slic121). Filesystem firmware binary used (/lib/firmware/voice_ar9_firmware.bin). VMMC [version 0x 0, type

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-15 Thread Eddi De Pieri
Hi Mikko, I've pushed my changes on https://github.com/openwrt-vgv7519/openwrt (branch vgv7519-20141007-begin_vmmc) If you want to try it on different router remember to adjust profiles and dts like VGV7519. bootargs = console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M mem=62M

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-15 Thread thomas.langer
Hello Eddi, Eddi De Pieri wrote onĀ 2014-10-14: Hi to all, I've applied to kernel patch for vpe committed for falcon, fixed for vr9 ltq-vmmc, modified VGV7519 dts for passing new parameters console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M mem=62M panic=1

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-15 Thread John Crispin
On 15/10/2014 12:10, thomas.lan...@lantiq.com wrote: Hello Eddi, Eddi De Pieri wrote on 2014-10-14: Hi to all, I've applied to kernel patch for vpe committed for falcon, fixed for vr9 ltq-vmmc, modified VGV7519 dts for passing new parameters console=ttyLTQ0,115200 init=/etc/preinit

Re: [OpenWrt-Devel] lantiq vr9 and fxs

2014-10-14 Thread Eddi De Pieri
Hi to all, I've applied to kernel patch for vpe committed for falcon, fixed for vr9 ltq-vmmc, modified VGV7519 dts for passing new parameters console=ttyLTQ0,115200 init=/etc/preinit maxvpes=1 maxtcs=1 phym=64M mem=62M panic=1 vpe1_load_addr=0x83e0 vpe1_mem=2M vpe1_wired_tlb_entries=1 Now I

[OpenWrt-Devel] lantiq vr9 and fxs

2014-10-11 Thread Eddi De Pieri
Hi to all, I've started to figure out how much work is needed to support fxs on vr9 board like mine. On latest trunk : - owsip is missing (i know is bugged with 32mbram) - ltq-tapidemo is m issing - lantiq falcon fxs support seems broken It seems to me that by rebasing some patch for falcon