Date: Wed, 17 Dec 2014 15:54:56 -0800 From: Adrian Chadd <adrian@freebsd.org> To: "K. Macy" <kmacy@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Nikos Vassiliadis <nvass@gmx.com> Subject: Re: OT: github.com version of NDISulator Message-ID: <CAJ-VmonoWu=BxeX%2B_Vg0BWoGm9qyPwKCw7rpGNqj3p-4TuJROg@mail.gmail.com> In-Reply-To: <CAHM0Q_M7aFfu6xKw6fFLhTRyNf8UDdy=SJikvDj02VJAodWtPA@mail.gmail.com> References: <54898CE7.80509@gmx.com> <5491A7B6.9000703@gmx.com> <CAJ-VmonRb%2Bs82BUf%2BaTsdCkGwQ53z4PzakjTreaUj_dveyGPkQ@mail.gmail.com> <CAHM0Q_M7aFfu6xKw6fFLhTRyNf8UDdy=SJikvDj02VJAodWtPA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17 December 2014 at 14:04, K. Macy <kmacy@freebsd.org> wrote: > On Wed, Dec 17, 2014 at 11:04 AM, Adrian Chadd <adrian@freebsd.org> wrote: >> hi, >> >> The ndis code is (a) not maintained, and (b) not going to be updated >> for the newer NDIS API that drivers are slowly being changed over to >> use. > > > Lack of interest? Too much work? .. it's a bit of both. The earlier NDIS stuff had everything pretend to be an ethernet driver. So the wifi device drivers include a complete wifi stack and expose an 802.3 device. So, later versions of the NDIS interface (starting with 6, I think) expose increasingly more wifi specific bits, so the NDIS API needs to grow and the net80211 layer needs to grow these features. The API for drivers is also deserialised (ie, not pretending everything is running in a single driver thread context.) Have a read: http://msdn.microsoft.com/en-us/library/windows/hardware/ff560690%28v=vs.85%29.aspx -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonoWu=BxeX%2B_Vg0BWoGm9qyPwKCw7rpGNqj3p-4TuJROg>