From owner-freebsd-hackers  Thu Oct 10  2:28:20 2002
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7AA0A37B401
	for <freebsd-hackers@freebsd.org>; Thu, 10 Oct 2002 02:28:19 -0700 (PDT)
Received: from valu.uninet.ee (valu.uninet.ee [194.204.34.51])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CDB4843EAA
	for <freebsd-hackers@freebsd.org>; Thu, 10 Oct 2002 02:28:18 -0700 (PDT)
	(envelope-from taavi@uninet.ee)
Received: by valu.uninet.ee (Postfix, from userid 1002)
	id CAB6836420; Thu, 10 Oct 2002 12:28:13 +0300 (EEST)
Received: from localhost (localhost [127.0.0.1])
	by valu.uninet.ee (Postfix) with ESMTP
	id C93C83261A; Thu, 10 Oct 2002 12:28:13 +0300 (EEST)
Date: Thu, 10 Oct 2002 12:28:13 +0300 (EEST)
From: Taavi Talvik <taavi@uninet.ee>
To: Bruce M Simpson <bms@spc.org>
Cc: float@firedrake.org, David Gilbert <dgilbert@velocet.ca>,
	Neal Nelson <neal@nelson.name>, <freebsd-hackers@freebsd.org>
Subject: Re: [hackers] Writing a PCI ADSL Driver
In-Reply-To: <20021010084237.GC25634@spc.org>
Message-ID: <20021010121046.Q58931-100000@valu.uninet.ee>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.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-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG

On Thu, 10 Oct 2002, Bruce M Simpson wrote:

> I'm sure that if we drive the 3060 as a NATM interface, we can write generic
> netgraph code to attach to a link layer ATM interface and examine inbound
> ATM UNI cells for their VPI*VCI and act accordingly.
>
> This will certainly require ngatm and is a good testing ground for that code.

eni3060 can be configured to receive all unknown VC's on
separately handled receive descriptor.

Another issue is how to cleanly separate xDSL chipset handling
from ATM SAR handling.

For example both eni3060/3061 and 3com HomeConnect have alcatel chipset
but different ATM sar's (eni - lanai, 3com - idt). xDSL handling could be
common to both as code dealing with alcatel chipset is same.

Same thing about configuring modem for different linecodes (G.dmt, G.lite,
ANSI, etc). I looked at miibus, but that is not generic enough to be used
here.

best regards,
taavi


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