From owner-freebsd-hackers Thu Oct 5 15:22:03 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA24611 for hackers-outgoing; Thu, 5 Oct 1995 15:22:03 -0700 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA24600 for ; Thu, 5 Oct 1995 15:21:59 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id PAA17861; Thu, 5 Oct 1995 15:20:52 -0700 Message-Id: <199510052220.PAA17861@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Julian Elischer cc: gibbs@freefall.freebsd.org (Justin T. Gibbs), j@uriah.heep.sax.de, mango@communique.net, hackers@freebsd.org Subject: Re: EISA and FreeBSD In-reply-to: Your message of "Thu, 05 Oct 1995 13:51:25 PDT." <199510052051.NAA05616@ref.tfs.com> Date: Thu, 05 Oct 1995 15:20:51 -0700 From: "Justin T. Gibbs" Sender: owner-hackers@freebsd.org Precedence: bulk >> >The eisa code is orphaned and defunct (to the best of my knowledge). >> >Simply declare it as isa. >> >> I'm in the process of bringing it back from the dead and cleaning it up. >> I hope to have it functional again in the comming week. > >can I help? >It worked fine, except that it couldn't setup the interrupts for the devices.. >(it thought it did but they didn't work) > >it should be set up so that EISA devices have TEXT_SET or DATA_SET entries for >their config lines, so that mere inclusion of the driver >makes the EISA code aware of it's existance.. >(i.e the file eisadevs.c should go away) > >julian I agree that eisaconf.c should go away, but I think that the tables the eisa code uses should be gerneated by config. The problem with how the pci code and the eisa code deal with devices is that they can't be disabled by userconfig, and eisa/pci devices can take unit numbers reservered for isa devices that use the same driver. I already have some plans to clean up the tables that config generates to make them more extensible and then have both pci and eisa devices use entries generated by config. As to the EISA code, I just don't like the way it does its probing. I'm changing the probe routine so that it passess the id strings to the probe routine of each installed driver until it finds a match (just like pci). I'll also be adding shared interrupt support and have the drivers explicitly register their interrupt handlers. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================