From owner-freebsd-isdn Thu Mar 7 9: 0:26 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [62.49.12.213]) by hub.freebsd.org (Postfix) with ESMTP id D584937B405 for ; Thu, 7 Mar 2002 09:00:03 -0800 (PST) Received: by arg1.demon.co.uk (Postfix, from userid 1002) id 6B1459B1A; Thu, 7 Mar 2002 15:02:54 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id 61DEE5D0C; Thu, 7 Mar 2002 15:02:54 +0000 (GMT) Date: Thu, 7 Mar 2002 15:02:54 +0000 (GMT) From: Andrew Gordon X-X-Sender: To: Harald Schmalzbauer Cc: Subject: Re: ifpi2 [WAS: Re: Elsa QuickStep/Microlink PCI] In-Reply-To: <1015498950.13546.2.camel@hry.muc.wearix.com> Message-ID: <20020307144953.X18069-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 7 Mar 2002, Harald Schmalzbauer wrote: > Am Mi , 2002-03-06 um 22.43 schrieb Andrew Gordon: > *SNIP* > > One is the AVM Fritz!Card PCI version 2 (version 1 is 5V-only), now > > supported by the ifpi2 driver. > > Hmm, I missed that. Great!!! > But I saw that it's only in -current, although it's 2 months old and has > mfc after 4 weeks. > Any chance that it gets MFCd in the near future? > Any experiences? I have a Fritz!Card PCI V2 installed in a Net4501 (http://www.soekris.com/) which also has limited +5V current available; I haven't measured the current drawn, but it's probably less than the 100mA you say is available in your system. This machine is running -stable. I can't now remember whether Gary Jennejohn provided a patch set (check the mailing list archives from around November 2001 when he announced the driver) or if I simply used the version from -current. Running I4B from -current on -stable is normally fairly straightforward anyhow. As to the reliability of the driver, there was one major problem, for which there is now a patch (which doesn't appear to have been committed, probably because Gary is waiting for me to test it as I promised to do weeks ago...). With that patch, it is mostly reliable, and probably would be 100% reliable on faster hardware: I believe that the remaining problem is a generic I4B bug, tickled by high interrupt latency causing occasional packet loss. I need to do more work on this, but the failure occurs about once a month in normal use, or almost immediately with high levels of debugging turned on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message