From owner-freebsd-current@FreeBSD.ORG Wed Oct 23 17:40:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4E5B87AA for ; Wed, 23 Oct 2013 17:40:28 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 2870F200C for ; Wed, 23 Oct 2013 17:40:27 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id F0D8F4180E for ; Wed, 23 Oct 2013 17:40:25 +0000 (UTC) Message-ID: <52680A09.3000403@allanjude.com> Date: Wed, 23 Oct 2013 13:40:25 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [rfc] removing the NDISulator References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Wed, 23 Oct 2013 17:40:28 -0000 On 2013-10-23 13:35, Eitan Adler wrote: > On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote: >> If there are drivers that people absolutely need fixed then they should >> stand up and say "hey, I really would like X to work better!" and then >> follow it up with some encouraging incentives. Right now the NDISulator >> lets people work _around_ this by having something that kind of works for >> them but it doesn't improve our general driver / stack ecosystems. > I doubt most people prefer to use the ndisulator over a native driver. > However, many people don't have the skills, time, or money to provide > the incentives you are talking about. At this point ndisulator > provides a means to an end: working wireless and it isn't causing > significant strain on the project in terms of development effort. > > Our end users are not always developers and I think removing this > feature will hurt more than it will help. > > I think the point Adrian is trying to make, is that the NDISulator needs a maintainer, and rather than someone working on that hack, that person should spend their time on native drivers. As someone earlier in the thread pointed out, it doesn't seem that many drivers are NDISulatable anymore. The proposal is to remove it from 11 (2 years away). I am all for keeping it, if it works, but if it is unmaintained, what state will it be in 2 years from now? -- Allan Jude