From owner-freebsd-hackers Mon Sep 25 01:21:06 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA05405 for hackers-outgoing; Mon, 25 Sep 1995 01:21:06 -0700 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id BAA05400 for ; Mon, 25 Sep 1995 01:21:03 -0700 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0sx8m1-0003voC; Mon, 25 Sep 95 01:20 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id JAA00231; Mon, 25 Sep 1995 09:20:20 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: Bruce Evans cc: dennis@etinc.com, hm@altona.hamburg.com, hackers@freebsd.org Subject: Re: LKM: how to fiddle in interrupt routine ptrs ? In-reply-to: Your message of "Mon, 25 Sep 1995 17:20:04 +1000." <199509250720.RAA02192@godzilla.zeta.org.au> Date: Mon, 25 Sep 1995 09:20:19 +0100 Message-ID: <229.812017219@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org Precedence: bulk I guess, that you have noticed that pccard is doing this kind of stuff today, and isn't doing it particular well, since nobody knows what to do :-( It seems to me that we have several kinds of devices: 1. things which say: give me 0x200-0x21f, (similar for iomem, irq & dma). 2. things which say: give me one of {0x200-0x21f,0x300-0x31f,0x320-0x33f} (similar for iomem, irq & dma). 3. things which say: give me 0x20 ioaddresses. (similar for iomem, irq & dma) Now, we need to cater for all of these one way or another, and it doesn't get any easier when some pieces of HW use method 2 for port, 1 for irq and 3 for iomem. Anybody thought about this from scratch ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. It will be some time yet before progress goes to far... (Poul Henningsen)