From owner-freebsd-isdn Wed Sep 30 11:07:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16146 for freebsd-isdn-outgoing; Wed, 30 Sep 1998 11:07:58 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16138 for ; Wed, 30 Sep 1998 11:07:54 -0700 (PDT) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (frankenputer.aussie.org [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id EAA25933 for ; Thu, 1 Oct 1998 04:07:37 +1000 (EST) Message-Id: <199809301807.EAA25933@mail.aussie.org> From: "Hallam Oaks P/L list account" To: "freebsd-isdn@FreeBSD.ORG" Date: Thu, 01 Oct 1998 04:04:02 +1000 Reply-To: "Hallam Oaks P/L list account" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: HSCX query Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is primarily directed to Hellmuth, but anyone else familiar with the internals of i4b please feel free to respond :) I'm working on a new device support for i4b. This device (a PCI ISDN card) does _not_ have a HSCX in the normal manner of speaking. Most of the HSCX functions are handled by the PCI ISAC, the rest (HDLC decoding) has to be done in software. At the moment, I just want to get the 'D' channel signalling working [as a first step], but firstly I need to know how much of the HSCX code has to be implemented to allow this. Since the ISAC doesn't at all resemble a 82525 et al, I'm probably going to have to emulate it at the register level, and that (may?) be a lot of work. I think I may only have to do the HSCX interrupt control and version stuff for 'D' but I may be very wrong. Can anyone tell me ? regards, -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message