From owner-freebsd-isdn  Mon Sep  2  5:37: 5 2002
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 3A39F37B400
	for <freebsd-isdn@FreeBSD.ORG>; Mon,  2 Sep 2002 05:37:04 -0700 (PDT)
Received: from guinness.syncrontech.com (guinness.syncrontech.com [62.71.8.19])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CF2FA43E6E
	for <freebsd-isdn@FreeBSD.ORG>; Mon,  2 Sep 2002 05:37:02 -0700 (PDT)
	(envelope-from ari.suutari@syncrontech.com)
Received: from linux (coffee.syncrontech.com [62.71.8.37])
	by guinness.syncrontech.com (8.12.3/8.12.3) with ESMTP id g82CaxeA033999;
	Mon, 2 Sep 2002 15:36:59 +0300 (EEST)
	(envelope-from ari.suutari@syncrontech.com)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Ari Suutari <ari.suutari@syncrontech.com>
Organization: Syncron Tech Oy
To: hselasky@c2i.net
Subject: Re: New ihfc driver
Date: Mon, 2 Sep 2002 15:37:20 +0300
User-Agent: KMail/1.4.2
Cc: freebsd-isdn@FreeBSD.ORG
References: <200208301111.g7UBBUQI005381@peedub.jennejohn.org> <200209020943.29552.ari.suutari@syncrontech.com>
In-Reply-To: <200209020943.29552.ari.suutari@syncrontech.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200209021537.20517.ari.suutari@syncrontech.com>
Sender: owner-freebsd-isdn@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isdn.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-isdn>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-isdn>
X-Loop: FreeBSD.org

Hi,


I have done some more reading of ihfc2 driver source now.
Do I understand it wrong or is this driver trying to support
multiple chip architectures ? There seems to be at least hfc-1,
hfc-s and some others. Maybe there is a good idea behind this,
but didn't isdb4bsd have this kind of monolithic single driver
in the beginning (which supported only Siemens chips).
I understood that it was difficult to add new chip sets to
this architecture, thus the lowest layer was
split into separate drivers.

So is this driver moving back to that initial approach ?
Is it wise ?

=09Ari S.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message