From owner-cvs-all Tue Jul 4 4:33: 4 2000 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1B87C37B550; Tue, 4 Jul 2000 04:32:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id NAA13366; Tue, 4 Jul 2000 13:32:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Nick Hibma , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys bus.h bus_private.h src/sys/kern subr_bus.c In-reply-to: Your message of "Tue, 04 Jul 2000 04:30:32 PDT." <200007041130.EAA02524@mass.osd.bsdi.com> Date: Tue, 04 Jul 2000 13:32:55 +0200 Message-ID: <13364.962710375@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007041130.EAA02524@mass.osd.bsdi.com>, Mike Smith writes: >Firstly - I don't buy that you can't uniquely identify the device up >front. This would be a violation of the PCI spec, just for starters. It *is* a violation of the PCI spec, but that's just a fact of life, not all hardware lives up to what the standards intended. But even with the identification problem aside, I still have seen no acceptable way to attach one driver to two new-bus devices... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message