From owner-freebsd-isdn@FreeBSD.ORG Wed Aug 17 00:00:33 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBA6416A41F for ; Wed, 17 Aug 2005 00:00:33 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5333043D45 for ; Wed, 17 Aug 2005 00:00:32 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-198-105.daxnet.no ([193.217.198.105] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 433903102 for freebsd-isdn@freebsd.org; Wed, 17 Aug 2005 02:00:30 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Wed, 17 Aug 2005 02:01:27 +0200 User-Agent: KMail/1.7 References: <200508161814.j7GIESTv010770@peedub.jennejohn.org> In-Reply-To: <200508161814.j7GIESTv010770@peedub.jennejohn.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200508170201.28540.hselasky@c2i.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: New ISDN driver X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 00:00:34 -0000 On Tuesday 16 August 2005 20:14, Gary Jennejohn wrote: > Michael Reifenberger writes: > > On Tue, 16 Aug 2005, Hans Petter Selasky wrote: > > ... > > > > >> Well, doesn't "i4l_" indicate that this came from "ISDN4LINUX" ? > > > > > > If you "cat" all the files in "/sys/i4b" and search for the word > > > "linux" or "Linux" you will get some hits. > > > > > > So I suspect that some parts of the drivers in "/sys/i4b/layer1" are > > > derivatives of Linux. And I have got some hints about that too. So > > > maybe we should just drop support for some hardware, and stick with the > > > chip-drivers > > > > I > > > > > have written from scratch ? Else we might end up getting a bad rumor > > > about stealing code from Linux. > > > > The occurance of [Ll]inux or l_* doesnt imply that these files are from > > linux . > > /sys/compat/linux/* files are stuffed with these letters. > > Usually they are for compatibility reasons. > > So its not reasonable to suspect any I4B files to be linux tainted. > > Several drivers were developed after examining the Linux code, which > in these cases was the only form of documentation available. AVM in > particular is very bad about providing documentation to any developer > outside the Linux world! Been there, done that. They might be afraid that someone will find problems about their products. For example their B-channel FIFO interface ill fits my system, hence you have to pre-write data lengths, which is a bad idea. Because then one has to pre-walk mbuf chains. But it might be interesting to dissassemble that AVM firmware, and see if it is really solid. I think that we won't have much use for those active AVM controllers in the future. Modern passive E1 chips have many useful features. For example DTMF detection, support for telephony conferences, interconnection of channels, and very large buffers. The only thing these chips haven't got, is a modem emulator, which I think is not very difficult to have in software. Detecting sine waves is not very difficult. One simply puts the waves one wants to detect, into a linear equation set, solves it, and finds the unknown amplitudes. This is something like Fast Fourier Transform, though we cannot use FFT, hence these modem frequencies doesn't fit exactly into "n" samples. So it is not very difficult. There also exist other algorithms to demodulate sine waves, but I think one will get best results with linear equation sets? --HPS