Olivier
2010-May-08 20:04 UTC
[asterisk-users] Conflict between jumper settings and dmesg with OctoBRI
Hello, In my system, dmesg outputs : [ 13.039788] wcb4xxp 0000:01:0a.0: probe called for b4xx... [ 13.039788] ACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21 [ 13.039788] wcb4xxp 0000:01:0a.0: Identified HFC-8S Junghanns.NET octoBRI PCI (controller rev 1) at 0001dfe0, IRQ 21 [ 13.041202] wcb4xxp 0000:01:0a.0: NOTE: hardware echo cancellation has been disabled [ 13.041477] wcb4xxp 0000:01:0a.0: Port 1: TE mode [ 13.041591] wcb4xxp 0000:01:0a.0: Port 2: NT mode [ 13.044952] wcb4xxp 0000:01:0a.0: Port 3: TE mode [ 13.045116] wcb4xxp 0000:01:0a.0: Port 4: TE mode [ 13.045116] wcb4xxp 0000:01:0a.0: Port 5: TE mode [ 13.045116] wcb4xxp 0000:01:0a.0: Port 6: TE mode [ 13.045116] wcb4xxp 0000:01:0a.0: Port 7: TE mode [ 13.045116] wcb4xxp 0000:01:0a.0: Port 8: TE mode [ 13.045116] wcb4xxp 0000:01:0a.0: Did not do the highestorder stuff [ 13.139884] wcb4xxp 0000:01:0a.0: new card sync source: port 3 [ 13.630304] wcb4xxp 0000:01:0a.0: Span 5 has invalid sync priority (5), removing from sync source list [ 13.630304] wcb4xxp 0000:01:0a.0: Span 6 has invalid sync priority (6), removing from sync source list [ 13.630304] wcb4xxp 0000:01:0a.0: Span 7 has invalid sync priority (7), removing from sync source list [ 13.630304] wcb4xxp 0000:01:0a.0: Span 8 has invalid sync priority (8), removing from sync source list [ 13.666827] dahdi_echocan_oslec: Registered echo canceler 'OSLEC' [ 13.671632] dahdi: Registered tone zone 2 (France) [ 13.730925] wcb4xxp 0000:01:0a.0: new card sync source: port 1 The strange thing is I'm quite certain the jumper for port 2 is set to TE mode (I checked twice). Could this come for a bug in wcb4xxp ? The card is an old Junghanns OctoBRI. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100508/11dc16a7/attachment.htm
Andre
2010-May-28 23:53 UTC
[asterisk-users] Conflict between jumper settings and dmesg with OctoBRI
Hi! Try this patch. IF you apply it you can tell dahdi the port mode to use like this modprobe wcb4xxp port_mode=0,0,1,1 means TE,TE,NT,NT Tell me if it works! ---------------------------- --- drivers-old/dahdi/wcb4xxp/base.c 2009-11-09 20:32:45.000000000 +0100 +++ drivers/dahdi/wcb4xxp/base.c 2010-05-29 01:46:03.000000000 +0200 @@ -95,6 +95,8 @@ static int alarmdebounce = 500; static int vpmsupport = 1; static int timer_1_ms = 2000; static int timer_3_ms = 30000; +static int port_mode[MAX_SPANS_PER_CARD] = {}; +static int port_mode_count = 0; #if !defined(mmiowb) #define mmiowb() barrier() @@ -1472,8 +1474,13 @@ static void hfc_init_all_st(struct b4xxp */ if (b4->card_type == B410P) nt = ((gpio & (1 << (i + 4))) == 0); - else - nt = ((gpio & (1 << (i + 4))) != 0); + else { + if (i<port_mode_count) { + nt = (port_mode[i] > 0); + } else { + nt = ((gpio & (1 << (i + 4))) != 0); + } + } s->te_mode = !nt; @@ -2938,6 +2945,7 @@ module_param(alarmdebounce, int, S_IRUGO module_param(vpmsupport, int, S_IRUGO); module_param(timer_1_ms, int, S_IRUGO | S_IWUSR); module_param(timer_3_ms, int, S_IRUGO | S_IWUSR); +module_param_array(port_mode, int, &port_mode_count, S_IRUGO | S_IWUSR); MODULE_PARM_DESC(debug, "bitmap: 1=general 2=dtmf 4=regops 8=fops 16=ec 32=st state 64=hdlc 128=alarm"); MODULE_PARM_DESC(spanfilter, "debug filter for spans. bitmap: 1=port 1, 2=port 2, 4=port 3, 8=port 4"); @@ -2951,6 +2959,7 @@ MODULE_PARM_DESC(alarmdebounce, "msec to MODULE_PARM_DESC(vpmsupport, "1=enable hardware EC, 0=disable hardware EC"); MODULE_PARM_DESC(timer_1_ms, "NT: msec to wait for link activation, TE: unused."); MODULE_PARM_DESC(timer_3_ms, "TE: msec to wait for link activation, NT: unused."); +MODULE_PARM_DESC(port_mode, "Port Mode 0=TE,1=NT"); MODULE_AUTHOR("Digium Incorporated <support at digium.com>"); MODULE_DESCRIPTION("B410P & Similars multi-port BRI module driver.");