From owner-freebsd-hackers Wed Sep 16 05:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02496 for freebsd-hackers-outgoing; Wed, 16 Sep 1998 05:25:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@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 FAA02475 for ; Wed, 16 Sep 1998 05:25:02 -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 WAA22191 for ; Wed, 16 Sep 1998 22:24:40 +1000 (EST) Message-Id: <199809161224.WAA22191@mail.aussie.org> From: "Hallam Oaks P/L list account" To: "freebsd-hackers@FreeBSD.ORG" Date: Wed, 16 Sep 1998 22:24:39 +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: 'struct isa_device' advice sought Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello; I'm implementing a PCI device interface for an ISDN card. The interface has the normal pci/ dir support code (this is already done so is not an issue). The main driver, however, is the i4b ISDN code, and this is where I'm running into trouble (despite appearances, this is not an ISDN-specific posting). The particular i4b code that I need to deal with assumes that the card it's working with is ISA, and as such makes liberal use of isa_device structs as parameters to functions, etc. To make this work with the PCI card, I'd have to either extensively modify this code (possible but not desirable), or init an isa_device structure and pretend that the PCI card is an ISA device (at least insofar as the i4b code is concerned). The changes necessary to the i4b code to make this work would not be so major - it would be aware of the PCI-ness of the card where it mattered, but otherwise not. My question is this : is the concept of a PCI card masquerading (in a limited sense) as an ISA one a legitimate approach ? Is it likely to cause problems ? I know it's a kludge but the alternative is also not particularly desirable. Any advice appreciated. -- Chris Hallam Oaks P/L To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message