From owner-freebsd-mobile Tue Sep 17 21:17:12 1996 Return-Path: owner-mobile Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01586 for mobile-outgoing; Tue, 17 Sep 1996 21:17:12 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01540 for ; Tue, 17 Sep 1996 21:17:05 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA05200; Tue, 17 Sep 1996 22:16:43 -0600 (MDT) Date: Tue, 17 Sep 1996 22:16:43 -0600 (MDT) Message-Id: <199609180416.WAA05200@rocky.mt.sri.com> From: Nate Williams To: BRETT_GLASS@infoworld.com Cc: Nate Williams , mobile@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: PCMCIA, APM, 3C562 In-Reply-To: <9608178430.AA843019805@ccgate.infoworld.com> References: <9608178430.AA843019805@ccgate.infoworld.com> 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. Again, like I said anything is possible given enought time and effort. Hooking into the existing drivers from a driver isn't a trivial task since they have 'bottom-end' drivers which expect to run quickly as interrupt handlers and thus must act quickly. I expect the upper drivers might 'MUX' well, it's the lower-end stuff that's a bit more work. But, I'm more than willing to be blown away with ingenuity of software developers. :) :) Nate