From owner-freebsd-wireless@FreeBSD.ORG Wed Nov 30 08:36:25 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3F62106566B for ; Wed, 30 Nov 2011 08:36:25 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 98B848FC13 for ; Wed, 30 Nov 2011 08:36:25 +0000 (UTC) Received: by qadc10 with SMTP id c10so115684qad.13 for ; Wed, 30 Nov 2011 00:36:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.31.132 with SMTP id y4mr579976qac.12.1322642184764; Wed, 30 Nov 2011 00:36:24 -0800 (PST) Sender: bschmidt@techwires.net Received: by 10.229.25.211 with HTTP; Wed, 30 Nov 2011 00:36:24 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Wed, 30 Nov 2011 09:36:24 +0100 X-Google-Sender-Auth: qXC4mV8fcE5NYZ-yY4sDFLr-pc8 Message-ID: From: Bernhard Schmidt To: Ninad Adi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Why does iwn driver in FreeBSD is coded in just one file. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2011 08:36:25 -0000 On Tue, Nov 29, 2011 at 20:52, Ninad Adi wrote: > Hereby, I officially =A0propose the splitting up of iwn driver code as > it is growing and will continue growing as > rate scaling improvements plus the P2P mode support would come into pictu= re. iwn(4) is imported (mostly, sans 11n support) unmodified from OpenBSD, up till now there isn't a single valid reason to split up any of the code. Heck, I've done my best to keep the code diff(1)able against the original code. If *you* gonna provide additional features to iwn(4) I might reconsider that decision, but I want to see some code first. Btw, any ratectl related stuff should go to net80211(4) not to the drivers, same for P2P, we have not a single line of code to support that currently. --=20 Bernhard