From owner-freebsd-isdn@FreeBSD.ORG Mon Jan 14 15:07:18 2013 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0A4B5C98 for ; Mon, 14 Jan 2013 15:07:18 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id 924A6E60 for ; Mon, 14 Jan 2013 15:07:17 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id CA4985C942; Mon, 14 Jan 2013 16:07:09 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id pMzxSV0OBNWf; Mon, 14 Jan 2013 16:07:08 +0100 (CET) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 07B365C94D; Mon, 14 Jan 2013 16:07:06 +0100 (CET) Received: from bsdlo.incore (bsdlo.incore [192.168.0.84]) by mail.incore (Postfix) with ESMTP id 00E2250875; Mon, 14 Jan 2013 16:07:05 +0100 (CET) Message-ID: <50F41F19.2050205@incore.de> Date: Mon, 14 Jan 2013 16:07:05 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ISDN4BSD (HPS version) is going into ports References: <509E87EF.9070607@incore.de> <201301101756.16289.hselasky@c2i.net> <50EF40E4.7030805@incore.de> <201301111150.47312.hselasky@c2i.net> In-Reply-To: <201301111150.47312.hselasky@c2i.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-isdn@freebsd.org X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2013 15:07:18 -0000 Hans Petter Selasky wrote: > Can you try to add a printf in "src/sys/i4b/driver/i4b_isppp.c": > > static void > i4bisppp_start(struct ifnet *ifp) > { > struct i4bisppp_softc *sc = ifp->if_softc; > > printf("ifp=%p sc=%p\n", sc, ifp); > > is the "sc" NULL ? No, I get ifp=0xc0c1f380 sc=0xc5532800 for every try for an outgoing message. I had to modify my i4b_filter.h hack for eliminating the last byte of every incoming D-channel message (not every incoming frame). Now D-channel works for outgoing and incoming calls (SETUP length > 32 byte) and also for long FACILITY messages of my provider. The patch is against 2.0.6: --- i4b_filter.h.orig 2009-01-09 20:07:38.000000000 +0100 +++ i4b_filter.h 2013-01-14 15:29:56.000000000 +0100 @@ -158,6 +158,12 @@ (f->buf_len) -= (io_len); (f->Z_chip) -= (io_len); + /* Hack for */ + if((FIFO_NO(f) == d1r) && (sc->sc_d1r_fifo_strip_last_byte == 1)) { + (f->buf_ptr) -= 1; + (f->buf_len) += 1; + } + return; } --- i4b_ihfc2.h.orig 2011-05-23 23:42:32.000000000 +0200 +++ i4b_ihfc2.h 2013-01-13 23:13:56.000000000 +0100 @@ -2583,7 +2583,7 @@ struct usb_callout sc_pollout_timr; /* T50 ms */ struct usb_callout sc_pollout_timr_wait; /* T125 us */ - u_int8_t sc_buffer[1024]; + u_int8_t sc_buffer[1024] __aligned(4); struct sc_fifo * sc_fifo_select_last; /* used by * FIFO_SELECT(,) @@ -2600,6 +2600,8 @@ u_int16_t sc_f0_counter_offset; u_int32_t sc_f0_counter_last; + + u_int8_t sc_d1r_fifo_strip_last_byte; }; --- i4b_avm_pci.h.orig 2012-11-26 22:37:23.000000000 +0100 +++ i4b_avm_pci.h 2013-01-14 12:27:31.000000000 +0100 IHFC_MSG("ista_d=0x%02x\n", ista_d); + sc->sc_d1r_fifo_strip_last_byte = 0; if(ista_d & 0x80 /* RME */) { /* read RBCL (ISAC) */ @@ -347,6 +348,7 @@ /* read RSTA (ISAC) */ avm_pci_chip_read(sc, REG_isacsx_rstad, &temp, 1); sc->sc_fifo[d1r].F_chip = temp; + sc->sc_d1r_fifo_strip_last_byte = 1; } /* RME or RPF - D channel receive */ For an incoming call I now see correct data in B-channel. avm_pci_b_status_read: len=32: 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff avm_pci_b_status_read: len=32: 0xf3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3 ... 12 repeats of last frame ... avm_pci_b_status_read: len=18: 0xff03c02101b0000e0506693e5e370304c023 avm_pci_b_status_read: len=18: 0xff03c02101b1000e0506693e5e370304c023 avm_pci_b_status_read: len=18: 0xff03c02101b2000e0506693e5e370304c023 avm_pci_b_status_read: len=18: 0xff03c02101b3000e0506693e5e370304c023 ... The frames of length 18 are exactly the frames I see on the remote side by isdndecode. But my local isdndecode does not see these B-channel messages, I don't know why. --- Andreas Longwitz From owner-freebsd-isdn@FreeBSD.ORG Mon Jan 14 15:27:24 2013 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 881B7450 for ; Mon, 14 Jan 2013 15:27:24 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id 224B4F4B for ; Mon, 14 Jan 2013 15:27:23 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 366382174; Mon, 14 Jan 2013 16:27:14 +0100 From: Hans Petter Selasky To: Andreas Longwitz Subject: Re: ISDN4BSD (HPS version) is going into ports Date: Mon, 14 Jan 2013 16:28:40 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <509E87EF.9070607@incore.de> <201301111150.47312.hselasky@c2i.net> <50F41F19.2050205@incore.de> In-Reply-To: <50F41F19.2050205@incore.de> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: freebsd-isdn@freebsd.org X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2013 15:27:24 -0000 On Monday 14 January 2013 16:07:05 Andreas Longwitz wrote: > For an incoming call I now see correct data in B-channel. > > avm_pci_b_status_read: len=32: > 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff > avm_pci_b_status_read: len=32: > 0xf3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3f3 > ... 12 repeats of last frame ... > avm_pci_b_status_read: len=18: 0xff03c02101b0000e0506693e5e370304c023 > avm_pci_b_status_read: len=18: 0xff03c02101b1000e0506693e5e370304c023 > avm_pci_b_status_read: len=18: 0xff03c02101b2000e0506693e5e370304c023 > avm_pci_b_status_read: len=18: 0xff03c02101b3000e0506693e5e370304c023 > ... > > The frames of length 18 are exactly the frames I see on the remote side > by isdndecode. But my local isdndecode does not see these B-channel > messages, I don't know why. Hi, Do you know what mode the chip is running in for the B-channels? HDLC or so-called transparent mode (no bit-destuffing). By default the AVM PCI driver is setup to use HDLC emulation, and expects that the chip is configured for transparent mode. Valid HDLC flags start like 0x7E, and that is what I would expect. Else something is wrong somewhere. [Incoming data] -> [HDLC table decoder] -> [isdndecode] No data in isdndecode means that the HDLC table decoder is not getting what it expects. --HPS From owner-freebsd-isdn@FreeBSD.ORG Tue Jan 15 11:28:16 2013 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A027180 for ; Tue, 15 Jan 2013 11:28:16 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id 656C8E6F for ; Tue, 15 Jan 2013 11:28:16 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id EA46C5D4C9; Tue, 15 Jan 2013 12:28:14 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id MC4JiUVJRobk; Tue, 15 Jan 2013 12:28:14 +0100 (CET) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id DE2CB5D4C7; Tue, 15 Jan 2013 12:28:03 +0100 (CET) Received: from bsdlo.incore (bsdlo.incore [192.168.0.84]) by mail.incore (Postfix) with ESMTP id D29BF50880; Tue, 15 Jan 2013 12:28:03 +0100 (CET) Message-ID: <50F53D43.2070404@incore.de> Date: Tue, 15 Jan 2013 12:28:03 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ISDN4BSD (HPS version) is going into ports References: <509E87EF.9070607@incore.de> <201301111150.47312.hselasky@c2i.net> <50F41F19.2050205@incore.de> <201301141628.40780.hselasky@c2i.net> In-Reply-To: <201301141628.40780.hselasky@c2i.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-isdn@freebsd.org X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 11:28:16 -0000 Hans Petter Selasky wrote: > > Do you know what mode the chip is running in for the B-channels? Not really. > HDLC or so-called transparent mode (no bit-destuffing). By default the AVM PCI > driver is setup to use HDLC emulation, and expects that the chip is configured > for transparent mode. Valid HDLC flags start like 0x7E, and that is what I > would expect. Else something is wrong somewhere. > > [Incoming data] -> [HDLC table decoder] -> [isdndecode] > > No data in isdndecode means that the HDLC table decoder is not getting what it > expects. Thanks for this clarification. With some more initialization stolen from the BSD source I now have for the first incoming frame: avm_pci_b_status_read: len_rx=32: 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff avm_pci_b_status_read: len_rx=32: 0xffffffffffe7ff7e7edf070087043c003814183cf920021e20001ea9cfe8e7e7 avm_pci_b_status_read: len_rx=32: 0xe7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7e7 and the first outgoing looks like this: avm_pci_b_status_read: len_tx=32: 0xffffff7edf070087040400381418683c51db0d10008f30e0fafdffffffffffff and my local isdndecode sees both of this frames (remote isdndecode sees only his own frame): -- TE->NT - unit:00 frame:000030 - time:14.01 21:28:26.129845 - length:18 ---- B01:000 ff 03 c0 21 01 01 00 0e 05 06 1a 4f d4 76 03 04 B01:010 c0 23 -- NT->TE - unit:00 frame:000031 - time:14.01 21:28:26.203400 - length:18 ---- B01:000 ff 03 c0 21 01 0f 00 0e 05 06 4f 3e 44 c0 03 04 B01:010 c0 23 But no more frames. I have b1control=hdlc in my isdnd.rc and use for the card: isdnconfig -u 0 -p DRVR_DSS1_TE I do not know what to do otherwise from userland to "configure the chip for transparent mode". The kernel driver should do this (he sets HSCX_MODE_TRANS) ? I agree there is a communication problem for B-channel between the driver and the chip. For an outgoing B-channel frame we write the frame to the fifo of the chip but I cannot see, that we tell the chip we are ready and the frame should go out the line. For an incoming B-channel frame we read the frame from the fifo of the chip but I don't see that we tell the chip we have it, so the chip does not get the next frame from the line. For incoming D-channel frames we use RMC command for this in register cmdrd. Probably I am missing something. -- Andreas Longwitz From owner-freebsd-isdn@FreeBSD.ORG Tue Jan 15 20:24:34 2013 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5EC396DE for ; Tue, 15 Jan 2013 20:24:34 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id 1D1DE617 for ; Tue, 15 Jan 2013 20:24:33 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id B6C135D4FF; Tue, 15 Jan 2013 21:24:26 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id s_taQ1Ui5aAx; Tue, 15 Jan 2013 21:24:26 +0100 (CET) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id E9D5E5D4FE; Tue, 15 Jan 2013 21:24:25 +0100 (CET) Received: from bsdmhs.longwitz (unknown [192.168.99.6]) by mail.incore (Postfix) with ESMTP id 89BA750875; Tue, 15 Jan 2013 21:24:25 +0100 (CET) Message-ID: <50F5BAF9.5020509@incore.de> Date: Tue, 15 Jan 2013 21:24:25 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ISDN4BSD (HPS version) is going into ports References: <509E87EF.9070607@incore.de> <201301091015.39124.hselasky@c2i.net> <50EDDDD7.2000006@incore.de> <201301100813.33186.hselasky@c2i.net> In-Reply-To: <201301100813.33186.hselasky@c2i.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-isdn@freebsd.org X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 20:24:34 -0000 Hi, please forget the last passage of my last post. In the meantime I changed some parts according to my former list to make things work like BSD does: >> 2. DELAY times on startup is different: 4 ms in isdn4bsd, 10 ms in BSD >> 3. Initializing the chip is more expansive in BSD, otherwise the >> register cmdrd is only used in isdn4bsd. >> >> 4. In avm_pci_fifo_reset() we write two single bytes, but BSD does one >> (atomic) four byte read. Particularly we do not write the HSCX_LEN >> byte between the both written bytes (must set to 0 ?) >> >> 5. In avm_pci_b_status_read() - analog to 4. - we read two single bytes, >> BSD (atomic) four bytes. With these adaptions isdn4bsd/isdnd now works with my AVM Fritzcard !! Because the driver works with "transparent mode" I observe that we have data exchange of 64kbit/s full duplex between chip and kernel as soon as a B-channel is up. And it makes no difference if I ping something over the line or run a ssh session or do nothing. I see about 500 irq's every second, I think that is the price for the tiny fifo buffer of 32 byte. Using the BSD driver I see for a ping only 12 irqs/sec and no irqs if the ping stops. Obviously thats not "transparent mode", the BSD driver uses HSCX_MODE_ITF_FLAG instead of HSCX_MODE_TRANS, that make probably the difference. If the 500 irqs/sec is what you expected, I will send you a complete patchfile. Thanks again for helping to track down this long standing problem. -- Andreas Longwitz From owner-freebsd-isdn@FreeBSD.ORG Tue Jan 15 20:47:47 2013 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9C88628F for ; Tue, 15 Jan 2013 20:47:47 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.c2i.net [212.247.154.98]) by mx1.freebsd.org (Postfix) with ESMTP id 1980878B for ; Tue, 15 Jan 2013 20:47:46 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 366923585; Tue, 15 Jan 2013 21:47:38 +0100 From: Hans Petter Selasky To: Andreas Longwitz Subject: Re: ISDN4BSD (HPS version) is going into ports Date: Tue, 15 Jan 2013 21:49:02 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <509E87EF.9070607@incore.de> <201301100813.33186.hselasky@c2i.net> <50F5BAF9.5020509@incore.de> In-Reply-To: <50F5BAF9.5020509@incore.de> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: freebsd-isdn@freebsd.org X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 20:47:47 -0000 Hi Andreas, On Tuesday 15 January 2013 21:24:25 Andreas Longwitz wrote: > Hi, > > please forget the last passage of my last post. > > In the meantime I changed some parts according to my former list to make > > things work like BSD does: > >> 2. DELAY times on startup is different: 4 ms in isdn4bsd, 10 ms in BSD > >> 3. Initializing the chip is more expansive in BSD, otherwise the > >> > >> register cmdrd is only used in isdn4bsd. > >> > >> 4. In avm_pci_fifo_reset() we write two single bytes, but BSD does one > >> > >> (atomic) four byte read. Particularly we do not write the HSCX_LEN > >> byte between the both written bytes (must set to 0 ?) > >> > >> 5. In avm_pci_b_status_read() - analog to 4. - we read two single bytes, > >> > >> BSD (atomic) four bytes. > > With these adaptions isdn4bsd/isdnd now works with my AVM Fritzcard !! > > Because the driver works with "transparent mode" I observe that we have > data exchange of 64kbit/s full duplex between chip and kernel as soon as > a B-channel is up. And it makes no difference if I ping something over > the line or run a ssh session or do nothing. I see about 500 irq's every > second, I think that is the price for the tiny fifo buffer of 32 byte. Beware that hardware HDLC can generate an even higher number of IRQ's, if specifically crafted messages are sent. Using transparent mode this rate is at least constant. I know at least one chip, the Winbond USB one, which has a neat feature to filter those flag datas once repeated. I was hoping the HSCX could do something similar. > > Using the BSD driver I see for a ping only 12 irqs/sec and no irqs if > the ping stops. Obviously thats not "transparent mode", the BSD driver > uses HSCX_MODE_ITF_FLAG instead of HSCX_MODE_TRANS, that make probably > the difference. > > If the 500 irqs/sec is what you expected, I will send you a complete > patchfile. I would expect 500 * 32 = 16K. Maybe it is possible to use a timer instead for all cards, because 250 IRQ's second is sufficient. Yes, I expect something like that. > > Thanks again for helping to track down this long standing problem. :-) You're welcome! --HPS From owner-freebsd-isdn@FreeBSD.ORG Fri Jan 18 16:23:07 2013 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DB9E4191 for ; Fri, 18 Jan 2013 16:23:07 +0000 (UTC) (envelope-from longwitz@incore.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id A041835B for ; Fri, 18 Jan 2013 16:23:07 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id BAE8C5D5B1; Fri, 18 Jan 2013 17:22:59 +0100 (CET) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id kvQ8pnU-GI54; Fri, 18 Jan 2013 17:22:59 +0100 (CET) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id 105E75D5A0; Fri, 18 Jan 2013 17:22:59 +0100 (CET) Received: from bsdlo.incore (bsdlo.incore [192.168.0.84]) by mail.incore (Postfix) with ESMTP id 0602B50875; Fri, 18 Jan 2013 17:22:59 +0100 (CET) Message-ID: <50F976E2.6020507@incore.de> Date: Fri, 18 Jan 2013 17:22:58 +0100 From: Andreas Longwitz User-Agent: Thunderbird 2.0.0.19 (X11/20090113) MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ISDN4BSD (HPS version) is going into ports References: <509E87EF.9070607@incore.de> <201301172230.44583.hselasky@c2i.net> <50F87F05.2080203@incore.de> <201301180900.41991.hselasky@c2i.net> In-Reply-To: <201301180900.41991.hselasky@c2i.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-isdn@freebsd.org X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 16:23:07 -0000 Hans Petter Selasky wrote: > Hi, > > I've committed all patches to the I4B SVN now with one more delta, to move the > remove_stat into a separate FIFO map. > > Please test and report back! > > r2549 > > --HPS With revision 2549 from your SVN my AVM Fritz!Card version 2 PCI card works correct. Thanks again ! -- Andreas Longwitz