From owner-freebsd-current@FreeBSD.ORG Mon Jul 9 22:40:24 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BFC9A16A41F for ; Mon, 9 Jul 2007 22:40:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9652413C44C for ; Mon, 9 Jul 2007 22:40:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3C04E46EFA; Mon, 9 Jul 2007 18:40:24 -0400 (EDT) Date: Mon, 9 Jul 2007 23:40:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Maksim Yevmenkin In-Reply-To: Message-ID: <20070709233036.V9997@fledge.watson.org> References: <20070613150534.D83504@fledge.watson.org> <20070613.212825.-957834923.imp@bsdimp.com> <20070709230022.D9997@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org, "M. Warner Losh" Subject: Re: HEADS UP: IPX over IP support removed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2007 22:40:24 -0000 On Mon, 9 Jul 2007, Maksim Yevmenkin wrote: >> Just realized you had a question in here, which I must have missed in the >> previous pass. What we're doing for i4b and netatm is leaving the code in >> the tree, but disconnecting it from the build for 7.0. So if things don't >> come together in time, we can just do that. I'm currently preparing a >> netatm patch, and Bjoern now has the i4b patch in the tree, so the ng_h4 >> bits are the only ones left after that. > > i could not make my xircom cbt pccard work under -current :( and could not > test my changes. also no one stepped forward and said that ng_h4(4) is being > used. so, i vote in favor of disconnecting ng_h4(4) from the build right > now. > > should i disconnect ng_h4(4) only or make a bigger change and retire all > support for serial bluetooth devices? Well, my interest here is only in eliminating NET_NEEDS_GIANT -- I don't mean to pass judgement on the more general class of devices, and as I know relatively little about them, couldn't do so in an informed way. My advice would be to leave everything that works, even if the devices are less common, as long as there's not a maintenance issue. And nothing says that ng_h4 can't come back in the future if people do turn up to do the testing. You might want to consider polling stable@ if you haven't already -- there's a much larger user community there. So I guess my advice is not to retire the rest if it's believed to work and isn't causing problems. Robert N M Watson Computer Laboratory University of Cambridge