From owner-freebsd-current Thu Jan 6 8:32:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 38728157C1; Thu, 6 Jan 2000 08:32:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA11780; Thu, 6 Jan 2000 09:32:04 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA77504; Thu, 6 Jan 2000 09:32:04 -0700 (MST) Message-Id: <200001061632.JAA77504@harmony.village.org> To: Eivind Eklund Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: committers@FreeBSD.org, current@FreeBSD.org In-reply-to: Your message of "Thu, 06 Jan 2000 17:26:04 +0100." <20000106172604.T13922@bitbox.follo.net> References: <20000106172604.T13922@bitbox.follo.net> <20000106122256.B13922@bitbox.follo.net> <200001060927.UAA03779@avalon.reed.wattle.id.au> <38746AEC.167EB0E7@elischer.org> <20000106122256.B13922@bitbox.follo.net> <200001061609.JAA77304@harmony.village.org> Date: Thu, 06 Jan 2000 09:32:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000106172604.T13922@bitbox.follo.net> Eivind Eklund writes: : On Thu, Jan 06, 2000 at 09:09:22AM -0700, Warner Losh wrote: : > The laptop support is approx that of 3.x. The fe device is no longer : > supported as a pccard. The sn device has been added. The YE_DATA : > floppy device isn't supported, but could be if some is motivated to : > fix it. There may be a few lingering hot plug issues in the old : > code's migration to newbus. There's also preliminary support for ata flash and ata cdroms that is new, as well as linksys support (although I think the linksys stuff is in 3.x now). I have hardware for fdc and fe changes, but not the time right now. Xircom has preliminary support as well, but that is broken at the moment. : How much benefit would you be getting by having 4.0 ship with newcard : instead of what's there now? E.g, by having 4.0-PAO relate to newcard : rather than what's in presently? I'm not sure that there is a huge advantage to having 4.0 ship with a fully functional newcard. As it stands now, there will likely be a PAO 4.0 release which brings forward much of the PAO3 functionality that hasn't yet been merged. In the 4.1 timeframe I think we'll see a more agressive move to newcard and by 4.2 see the differences between regular FreeBSD and PAO diminish quite a bit. However, that's just a guess. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message