Date: Wed, 23 Oct 2013 13:35:10 -0400 From: Eitan Adler <lists@eitanadler.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "Julian H. Stacey" <jhs@berklix.com>, "Andrey V. Elsukov" <bu7cher@yandex.ru>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: [rfc] removing the NDISulator Message-ID: <CAF6rxg=H_zf2nBSreQqMUgG5kizvPaAeR5H0hVPmfcA661UMTQ@mail.gmail.com> In-Reply-To: <CAJ-VmomzydOD-M1oePMuqrgdBCFMTXKCZcGVwu%2BLFTnHTGg0Kw@mail.gmail.com> References: <5265878B.1050809@yandex.ru> <201310212146.r9LLkqZ1044966@fire.js.berklix.net> <CAJ-VmomzydOD-M1oePMuqrgdBCFMTXKCZcGVwu%2BLFTnHTGg0Kw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd <adrian@freebsd.org> 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. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=H_zf2nBSreQqMUgG5kizvPaAeR5H0hVPmfcA661UMTQ>