From owner-freebsd-hardware Fri Jun 5 08:53:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17299 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 08:53:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17159 for ; Fri, 5 Jun 1998 08:51:33 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA21393; Fri, 5 Jun 1998 11:51:27 -0400 (EDT) Date: Fri, 5 Jun 1998 11:51:27 -0400 (EDT) From: "Matthew N. Dodd" To: Dexter McNeil cc: hardware@FreeBSD.ORG Subject: Re: DPT driver in V2.2.6 - EISA support anytime soon? In-Reply-To: <19980605001628.24925@panix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 5 Jun 1998, Dexter McNeil wrote: > I have the 2.2.6 release CDROMS, and have it up on a test box > (still need to do a cvsup...) I noticed that there is now a DPT device > driver, but support for EISA controllers is listed in the 'to do' > column. :-( Check sys/i386/eisa/dpt_eisa.[ch] :) > Any idea when (if?) there will be support for the EISA > controllers? I have two of them (PM2012B and a 2122) that I'd like to > use with FreeBSD. I'd offer to do the work, but unless someone can draw > a paint-by-numbers outline that I can fill in, I'd be pretty lost.... I've got a PM2012B which I was unable to get working correctly (may just be me) and a PM2022 which does work. There are some problems with the EISA probe/attach that I still have to fix but I'd ask that you compile a kernel with the drivers and see if it works. I've been trying to work out a better way of retrieveing the board config but my attempts to read any useful information from the EISA config registers have produced garbage. The current method sets up a mostly empty DPT config structure and issues an EATA command to read the board config. I suspect this causes problems with some versions of the card (it did with some of mine.) but not all. Anyhow, try it and see what you get. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message