From owner-freebsd-arch Tue Jun 13 11:12:21 2000 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id EA0A837BF73; Tue, 13 Jun 2000 11:12:14 -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 UAA11850; Tue, 13 Jun 2000 20:12:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: mjacob@feral.com, arch@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pci.c pcisupport.c pcivar.h In-reply-to: Your message of "Tue, 13 Jun 2000 10:41:15 PDT." <200006131741.KAA22559@mass.cdrom.com> Date: Tue, 13 Jun 2000 20:12:10 +0200 Message-ID: <11848.960919930@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200006131741.KAA22559@mass.cdrom.com>, Mike Smith writes: >> >> > The real situation is, in fact, just the opposite; there are *very* few >> > devices for which it is not possible to obtain, in a generic fashion, a >> > uniquifying token. >> >> So much so that the real issue now is "which one of 4 different drivers do >> want for driving your tulip chip based NIC?" > >The one that's maintained by someone that I can chase around the office >with the Damn Thing until he fixes it, of course. 8) Look at sys/dev/lmc and tell me if you want that to drive *your* tulip based card :-) -- 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 freebsd-arch" in the body of the message