From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 13 17:29:15 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 477FD106564A for ; Sun, 13 Nov 2011 17:29:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 014178FC0A for ; Sun, 13 Nov 2011 17:29:14 +0000 (UTC) Received: by vcbfo14 with SMTP id fo14so6645172vcb.13 for ; Sun, 13 Nov 2011 09:29:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Wj+24lo0Yd3uWNrnJgjYMTnUPT1EHMuaWfo18gwdyF4=; b=Z4Lzi8+TdWajOjv9NxG7UOMwEm8feMEO3VBZJginq3qq1WCorJV1WrE74tizphP6Zo Krm+GS+JO6u5gt27ExqKw7d9houvtqQFCq3wyGFVpm2hvsEktPyqlJvt67LEZPwkx6aY LD7dnSOHAzWjh2kQ3mwT2jrK1pkvolwpqfFuM= MIME-Version: 1.0 Received: by 10.52.92.84 with SMTP id ck20mr30763429vdb.88.1321205354292; Sun, 13 Nov 2011 09:29:14 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.29.198 with HTTP; Sun, 13 Nov 2011 09:29:14 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Nov 2011 09:29:14 -0800 X-Google-Sender-Auth: nc4VPHoWDVNOUnt6fLHaRvcbqN8 Message-ID: From: Adrian Chadd To: Ninad Adi Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 13 Nov 2011 17:29:15 -0000 On 13 November 2011 00:14, Ninad Adi wrote: > Dear Sirs, > > Why is that iwn driver in FreeBSD is coded in just one file, why isnt > it distributed according to its features, it would be easy to > understand, develop and debug > such kind of framework. Hi, It's mostly historical. If you'd like to take charge of maintaining iwn then please feel free to propose splitting it up. :) Adrian