On Sun, Sep 13, 2009 at 08:45:08AM +0200, Raoul Bönisch wrote:
> Hallo!
>
> Now I have to differentiate. There is the option "dchan" as
> opposed to "hardhdlc" in /etc/dahdi/system.conf. This is my
> current system.conf:
Hmmm... hfc_zap_chanconfig looks fishy . Try the following patch:
The attached patch looks like the fix to me. Though I'm not sure if
there isn't any actual use in the code of the fact that sigchan is
reset.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.co...@xorcom.com
+972-50-7952406 mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir
Index: zaphfc/base.c
===================================================================
--- a/drivers/dahdi/zaphfc/base.c (revision 4)
+++ b/drivers/dahdi/zaphfc/base.c (working copy)
@@ -626,10 +626,7 @@ static int hfc_zap_chanconfig(struct dahdi_chan *d
struct hfc_card *card = chan->card;
struct dahdi_hfc *hfccard = card->ztdev;
- if ((sigtype == DAHDI_SIG_HARDHDLC) || (hfccard->sigchan == d_chan)) {
- hfccard->sigchan = (sigtype == DAHDI_SIG_HARDHDLC)
- ? d_chan : NULL;
-
+ if ((sigtype == DAHDI_SIG_HARDHDLC) && (hfccard->sigchan == d_chan)) {
hfccard->sigactive = 0;
atomic_set(&hfccard->hdlc_pending, 0);
}
