From owner-freebsd-hackers Wed Jun 10 14:45:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27460 for freebsd-hackers-outgoing; Wed, 10 Jun 1998 14:45:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27298; Wed, 10 Jun 1998 14:44:47 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA13468; Wed, 10 Jun 1998 14:42:45 -0700 (PDT) Message-Id: <199806102142.OAA13468@implode.root.com> To: Terry Lambert cc: me@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: new config In-reply-to: Your message of "Wed, 10 Jun 1998 17:35:53 -0000." <199806101735.KAA29235@usr01.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 10 Jun 1998 14:42:45 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >1) There was a driver setup disk. It knew how to identify the > card and determine the interrupt. The FreeBSD driver could > have done this as well, but it simply didn't have the code > for it. This would not have been a destructive probe; the > chip had already been located. In most cases, the software interface specification for how to do this is unavailable. I do actually have some info for WD/SMC cards, which is why I added support for "?" for the interrupt, in which case the kernel reads it from the EEPROM. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message