From owner-freebsd-current Sun Mar 19 11:40: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4F7BA37B6C6 for ; Sun, 19 Mar 2000 11:39:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA14764; Sun, 19 Mar 2000 20:38:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: peter@netplex.com.au (Peter Wemm) Cc: current@FreeBSD.ORG Subject: Re: HEADS UP; new options for -current! In-reply-to: Your message of "Sun, 19 Mar 2000 21:14:47 +0800." <20000319131447.E6EF21CD9@overcee.netplex.com.au> Date: Sun, 19 Mar 2000 20:38:56 +0100 Message-ID: <14762.953494736@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000319131447.E6EF21CD9@overcee.netplex.com.au>, Peter Wemm writes : >If you are using old drivers that haven't been newbusified yet, you will >need to add 'options COMPAT_OLDPCI' and/or 'options COMPAT_OLDISA' to your >kernel configs and regenerate. Otherwise you will get compile failures. I think this is premature. I tried to newbusify if_mn.c, but after having added about 50 lines of code to replace the current about 10, I gave up. We need a highlevel wrapper for newbus before we should force people to upgrade the old-style drivers. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message