From owner-freebsd-current Tue Jan 18 23:29:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 58DC314F15 for ; Tue, 18 Jan 2000 23:29:23 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA79128; Wed, 19 Jan 2000 02:29:19 -0500 (EST) Date: Wed, 19 Jan 2000 02:29:19 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Problems with PCMCIA Cards In-Reply-To: <200001190716.AAA23745@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Jan 2000, Warner Losh wrote: > Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC > part. If they are, then it works great. If they aren't, then we lose > bigtime. It seems to me that any IRQ that the PCIC can see will be usable for assignment to a card no? Is there no way to hit the PCIC and tell it to issue an interrupt? Keep in mind I'm coming from a network device background here where a number of chips can be told to do this. Otherwise your timeout solution seems good. Are the valid IRQs dependent on the board integrator or on the chip used? Since we can identify the chips (well, it looks like we can) couldn't we maintain a 'quirk' table? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message