From owner-freebsd-wireless@FreeBSD.ORG  Thu Oct 24 03:46:19 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 8B48C133
 for <freebsd-wireless@freebsd.org>; Thu, 24 Oct 2013 03:46:19 +0000 (UTC)
 (envelope-from mueller6721@twc.com)
Received: from cdptpa-oedge-vip.email.rr.com
 (cdptpa-outbound-snat.email.rr.com [107.14.166.226])
 by mx1.freebsd.org (Postfix) with ESMTP id 546A325EF
 for <freebsd-wireless@freebsd.org>; Thu, 24 Oct 2013 03:46:19 +0000 (UTC)
Received: from [74.130.200.176] ([74.130.200.176:43072] helo=localhost)
 by cdptpa-oedge02 (envelope-from <mueller6721@twc.com>)
 (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP
 id CB/9C-15942-A0898625; Thu, 24 Oct 2013 03:46:18 +0000
Date: Thu, 24 Oct 2013 03:46:18 +0000
Message-ID: <CB.9C.15942.A0898625@cdptpa-oedge02>
From: "Thomas Mueller" <mueller6724@bellsouth.net>
To: freebsd-wireless@freebsd.org
References: <5265878B.1050809@yandex.ru>
 <201310212146.r9LLkqZ1044966@fire.js.berklix.net>
 <CAJ-VmomzydOD-M1oePMuqrgdBCFMTXKCZcGVwu+LFTnHTGg0Kw@mail.gmail.com>
 <CAF6rxg=H_zf2nBSreQqMUgG5kizvPaAeR5H0hVPmfcA661UMTQ@mail.gmail.com>
 <52684E48.20709@unsane.co.uk>
 <CAJ-VmokS-MniCLW2WSEqNxCOOqnY9Ko6p47rngWXabY9biBgPQ@mail.gmail.com>
Subject: Re: [rfc] removing the NDISulator
X-RR-Connecting-IP: 107.14.168.130:25
X-Cloudmark-Score: 0
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2013 03:46:19 -0000

 
> The later driver model isn't supported by ndisulator. We'd have to
> implement all the newer NDIS stuff for wifi and ethernet.
        
> In the later NDIS layer the Microsoft Wireless Services implement a bunch
> of stuff that used to be up to the driver. Ie, the driver just exposed an
> ethernet "device" with some extra bits for wifi. Ie, the whole stack runs
> in the driver. That has changed.
        
...

> This is why I'd rather us bite the bullet now and deprecate it, versus have
> it in there and put in the work to upgrade it to handle NDIS 6.x drivers
> with the Microsoft wireless extensions stuff.

        

> -adrian

How much extra work would there be to update the ndis(ulator/wrapper)?

Would it be more than writing native FreeBSD drivers which might be ported 
from NetBSD, OpenBSD and Linux?

What about cases where specifications might be a trade secret?

How difficult is it to port or write a wifi or Ethernet driver for FreeBSD?

I have no experience writing device drivers but have some experience with C and C++.

I notice NetBSD and OpenBSD have drivers for some chips that FreeBSD lacks.

I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to
connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and
Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only)
and OpenBSD.

Tom