From owner-freebsd-current Fri Dec 10 13:47: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 27F3E14D62 for ; Fri, 10 Dec 1999 13:47:02 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA52602; Fri, 10 Dec 1999 14:46:36 -0700 (MST) (envelope-from ken) Message-Id: <199912102146.OAA52602@panzer.kdm.org> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <7282.944861570@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 10, 1999 10:32:50 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Fri, 10 Dec 1999 14:46:36 -0700 (MST) Cc: imp@village.org (Warner Losh), current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote... > In message <199912102115.OAA25113@harmony.village.org>, Warner Losh writes: > > >: The ATA driver went golden now, and to make sure nobody is distracted > >: from testing it before 4.0-RELEASE is cut, the wd driver will be > >: removed. > >: > >: It's really that simple. > > > >Isn't that unprecidented? In the past there has always been a period > >of shakeout between the two events longer than a couple of days. > > Well, the only precedent we have is CAM/SCSI, and it was done the > same way. I don't think you should look at the CAM integration as a precendent for the current ATA situation. We had a switchover from the old SCSI layer to CAM instead of a transition because it would have been much more difficult to have both SCSI layers in the tree at the same time. In the case of the ATA code, both it and the wd driver have existed in the tree for quite a while, apparantly without problems. So I don't think there is a real parallel there. IMO, if the ATA driver supports all the chipsets that the wd driver does, then it's probably okay to throw the switch to get people testing the new driver. If it doesn't, though, I think we should wait on throwing the switch until it supports them all. Unlike the CAM case, there isn't a compelling reason to throw the switch before the new code supports every chipset. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message