On 2013-10-23 13:35, Eitan Adler wrote: > On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd <adrian_at_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. > > 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 JudeReceived on Wed Oct 23 2013 - 15:40:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:43 UTC