The NDISulator is a crutch from a time when there wasn't _any_ real
alternative.
There are plenty of alternatives now. What's lacking is desire and
person-power. But the datasheets are there, or the vendor code has been
released, or there's linux/otherbsd drivers.
Leaving it in there is just dela
"Andrey V. Elsukov" wrote:
> I'm agree. While there are still some devices without native drivers,
> but that work via NDISulator, we should keep it.
Yes, best keep it while it helps some people.
Adrian Chadd wrote:
> It's honestly about time that these were updated, fixed and/or ported to
>
On 21 October 2013 12:59, Andrey V. Elsukov wrote:
> On 19.10.2013 10:01, Thomas Mueller wrote:
> > I too would like to see more effort writing new Ethernet and wifi
> > drivers and porting from other operating systems.
> >
> > But I would like to keep the NDISulator/NDISwrapper as a fallback.
>
On 19.10.2013 10:01, Thomas Mueller wrote:
> I too would like to see more effort writing new Ethernet and wifi
> drivers and porting from other operating systems.
>
> But I would like to keep the NDISulator/NDISwrapper as a fallback.
>
> There are still wifi adapters, Ethernet too, where there is
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
