From owner-freebsd-hackers  Sun Jul 20 16:23:04 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA07477
          for hackers-outgoing; Sun, 20 Jul 1997 16:23:04 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA07472;
          Sun, 20 Jul 1997 16:22:50 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA09987; Sun, 20 Jul 1997 16:20:36 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199707202320.QAA09987@phaeton.artisoft.com>
Subject: Re: pcireg.h lost children... ?
To: se@FreeBSD.ORG (Stefan Esser)
Date: Sun, 20 Jul 1997 16:20:36 -0700 (MST)
Cc: Shimon@i-connect.net, freebsd-hackers@FreeBSD.ORG, se@FreeBSD.ORG
In-Reply-To: <19970718202558.63332@mi.uni-koeln.de> from "Stefan Esser" at Jul 18, 97 08:25:58 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> One of the changes to the PCI code, that might follow (I have
> not completely made up my mind) is, that the probe will just
> associate a driver with a list of vendor/device IDs, and there
> will no longer be a xxx_probe() function in the drivers.

How does a PCI driver for, for instance, a DEC chip based ethernet
board find boards for which a vendor/driver assignment has not yet
been made?

Currently, the probe code will find the board, and it will just work.

One big problem I can see this causing (though I admit it cures
one of my loudest complaints: destructive probing) is that the
vendor/device/driver association list could quicly get too large
to fit on the same floppy as the BSD kernel.  8-(.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.