From owner-freebsd-mobile  Tue Sep 17 21:13:20 1996
Return-Path: owner-mobile
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA29542
          for mobile-outgoing; Tue, 17 Sep 1996 21:13:20 -0700 (PDT)
Received: from lserver.infoworld.com (root@lserver.infoworld.com [192.216.48.4])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA29530
          for <mobile@freebsd.org>; Tue, 17 Sep 1996 21:13:17 -0700 (PDT)
Received: from ccgate.infoworld.com (ccgate.infoworld.com [192.216.49.101]) by lserver.infoworld.com (8.7.5/8.7.3) with SMTP id VAA02975; Tue, 17 Sep 1996 21:13:06 -0700 (PDT)
From: BRETT_GLASS@infoworld.com
Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11)
	id AA843019805; Tue, 17 Sep 96 23:08:20 PST
Date: Tue, 17 Sep 96 23:08:20 PST
Message-Id: <9608178430.AA843019805@ccgate.infoworld.com>
To: Nate Williams <nate@mt.sri.com>
Cc: nate@mt.sri.com, mobile@freebsd.org, msmith@atrad.adelaide.edu.au
Subject: Re: PCMCIA, APM, 3C562
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> The PCIC support code currently doesn't shared interrupts.  But,
> *anything* is possible given enough time and effort, and if you choose
> not to use the PCIC support code (/sys/pccard), then you might be able
> to pull it off.

I think you misunderstand. What I would do is write ONE DRIVER that handled
interrupts from the card by passing them through to existing serial and
Ethernet code. As far as the PCMCIA code was concerned, the interrupt
wouldn't look as if it was shared, since the interrupts would all be
dispatched by that driver.

--Brett