From owner-cvs-src@FreeBSD.ORG Mon Feb 23 19:07:13 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC68016A4CE; Mon, 23 Feb 2004 19:07:13 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4337643D2D; Mon, 23 Feb 2004 19:07:13 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i1O378kj038932; Mon, 23 Feb 2004 20:07:08 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 23 Feb 2004 20:07:07 -0700 (MST) Message-Id: <20040223.200707.35796907.imp@bsdimp.com> To: scottl@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20040223150304.F66630@pooker.samsco.home> References: <8758.1077551092@critter.freebsd.dk> <200402231551.14698.jhb@FreeBSD.org> <20040223150304.F66630@pooker.samsco.home> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: phk@phk.freebsd.dk cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: jhb@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha mem.c promcons.c src/sys/alpha/tlsb zs_tlsb.c src/sys/amd64/amd64 mem.c src/sys/cam cam_xpt.c src/sys/cam/scsi scsi_ch.c scsi_pass.c scsi_pt.c s X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 03:07:13 -0000 In message: <20040223150304.F66630@pooker.samsco.home> Scott Long writes: : Good planning now is worth a ton of #ifdefs later. I support what PHK is : aiming for here. I don't think that you really are away of the : significant differences between 4.x and 5.x and how messy it has become to : support both with the same source. Supporting the tip of both isn't that horrible (I do it with OLDCARD), but supporting all N versions of 4.x is ugly. : The 'MPSAFE' and 'FAST' lines will probably be either reversed or put : under bootverbose before 5.3. It would be nice if there was a way to : express these flags from within the probe line, but our driver model : doesn't suppor that at all. Tearing up the API for such a cosmetic : change probably isn't worthwhile right now, but might be considered if : we ever get a multi-pass newbus framwork. If we printed the probe information AFTER attach succeeded, then we could do it... Warner