From owner-freebsd-stable@FreeBSD.ORG Sat Jan 1 13:14:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1EA116A4E0; Sat, 1 Jan 2005 13:14:41 +0000 (GMT) Received: from central.local.mattsnetwork.co.uk (mattsnetwork.co.uk [82.152.151.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0038C43D2F; Sat, 1 Jan 2005 13:14:40 +0000 (GMT) (envelope-from matt@mattsnetwork.co.uk) Received: from workstation2.local.mattsnetwork.co.uk (workstation2.local.mattsnetwork.co.uk [192.168.0.142]) (authenticated bits=0)j01DEU6v088924 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Sat, 1 Jan 2005 13:14:31 GMT (envelope-from matt@mattsnetwork.co.uk) From: Matt Dawson To: "Simon L. Nielsen" Date: Sat, 1 Jan 2005 13:14:30 +0000 User-Agent: KMail/1.7.2 References: <200501011217.13171.matt@mattsnetwork.co.uk> <20050101125734.GF761@zaphod.nitro.dk> In-Reply-To: <20050101125734.GF761@zaphod.nitro.dk> X-Face: Zrm9At!%e{M_#Po+[-\; RFQih#L0/\!^6f8JS_1Nz,8`(@bR%|T,c)3:o6my`.sy$Rt)'^)ec9cWp!MmeH^Gp|Afl)BkcH1GENCBqb&wZ$cdqN27uYfD=jU@1:vWXf|)LmuVKo?1wuS68KeDX&3,#wZP2$N1Ao!_'mZOws67 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200501011314.30584.matt@mattsnetwork.co.uk> X-Spam-Status: No, score=-2.8 required=2.5 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on central.local.mattsnetwork.co.uk X-Virus-Scanned: ClamAV 0.80/640/Thu Dec 23 18:48:27 2004 clamav-milter version 0.80j18:48:27 2004 clamav-milter version 0.80j o X-Virus-Status: Clean cc: freebsd-stable@freebsd.org Subject: Re: MFCs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2005 13:14:42 -0000 On Saturday 01 Jan 2005 12:57, Simon L. Nielsen wrote: > Sam has already said that the wlan parts will not be MFC'ed since they > break the API/ABI. Hmm, that's what I thought. It seemed to touch too many other bits of the=20 networking code to be that simple. I will stick with 5.x for now. The ath=20 board is in the server providing hostap service. It would have been nice to= =20 have proper 54Mbps support instead of the current 11Mbps, but I can't risk= =20 all the other services this box runs breaking. Ah well... > > I would suspect (read I don't know for sure and it's S=F8ren's call) > that the ata changes are going to MFC'ed, but since there are some > quirks in the ata code in CURRENT at the moment, which are being > worked on, I wouldn't hold my breath for the MFC. I won't. I don't use the ITE RAID on the Gigabyte board anyway, and the=20 support for the VIA SATA is rock-solid. The reason I wanted to know was tha= t=20 I found this board to be solid and stable and it would be nice to be able t= o=20 recommend an AMD64 board with 100% support. Even the ACPI is flawless on th= is=20 board. Its one let-down is the ITE device which doesn't even work as a norm= al=20 ATA controller. Yes, OK, I should be running -CURRENT with an AMD64 anyway, I know ;-) Thanks for the information. =2D-=20 Matt Dawson. matt@mattsnetwork.co.uk MD2657-RIPE OpenNIC M_D9