From owner-freebsd-scsi Thu Jan 20 18:22:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0141D15438 for ; Thu, 20 Jan 2000 18:22:56 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA81562 for ; Thu, 20 Jan 2000 19:22:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA07743 for ; Thu, 20 Jan 2000 19:22:41 -0700 (MST) Message-Id: <200001210222.TAA07743@harmony.village.org> To: freebsd-scsi@freebsd.org Subject: aha question Date: Thu, 20 Jan 2000 19:22:41 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How important is hard wiring a aha device? I'm reworking the aha driver to support probing for the self identification and to better support plug and play. In order to do this, I have created an identify routine which scans all the devices in the traditional self probing order and adds device children as needed. The only problem with this that I can see is that it destroys the ability to hardwire aha instances to unit numbers in the config file. While no pci drivers support this, and the isa ep driver provide strong evidence that I don't need to support this, I thought I'd ask here. Also, if I need to support this, how would I go about doing that? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message