public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Pavel Roskin <proski@gnu.org>
Cc: netdev@vger.kernel.org, madwifi-devel@lists.sourceforge.net
Subject: Re: d80211: ANNOUNCE: DadWifi, a port of MadWifi	to d80211
Date: Tue, 17 Oct 2006 21:55:32 -0700	[thread overview]
Message-ID: <20061017215532.3d3c769a@dads-laptop> (raw)
In-Reply-To: <1161145560.2285.32.camel@portland>

On Wed, 18 Oct 2006 00:26:00 -0400
Pavel Roskin <proski@gnu.org> wrote:

> Hello!
> 
> On Tue, 2006-10-17 at 18:51 -0700, Stephen Hemminger wrote:
> > I would consider this a BAD thing. You are creating a derived work
> > out of GPL and non-GPL software. This actually will hurt the possible acceptance
> > of the d80211 stack into the mainline kernel.
> 
> On the contrary, I think this effort with spur interest in d80211,
> Atheros hardware and stimulate development of OpenHAL.  It will also put
> additional pressure on Atheros to open HAL sources.

HAL's are bad as well. You want a real driver, not one that has multiple
layers of indirection.

> The technical ability of d80211 to handle a popular chipset would hardly
> undermine its chances to be included into the kernel.  It takes more
> that one step to achieve free in-kernel support for Atheros chipsets.
> DadWifi may be one of those steps, OpenHAL or open-sourcing the Atheros
> HAL would be the other.

If Atheros does open source their existing driver. Someone will need to
do a new driver that gets rid of the HAL layer.

> If DadWifi succeeds at supplanting MadWifi, it will reduce the
> proliferation of incompatible 802.11 stacks for Linux.  The FreeBSD
> stack included in MadWifi will become obsolete.
> 
> There are many great ideas involving meshing networks that require
> support at the 802.11 MAC layer because they are tied to the WDS
> implementation.  Those efforts can be shared if the MAC layer is shared.
> A company doing mesh networking on Atheros today could switch to
> Broadcom tomorrow if Broadcom makes better chips, or vice versa.  
> Users of DadWifi would contribute fixes that would affect users of other
> chipsets.
> 
> Should d80211 be merged with the existing 802.11 stack in the kernel,
> users of DadWifi would be among the testers, and they will ensure that
> useful features of d80211 are not lost.

As a test or transition vehicle it is a DadWifi is good, but hopefully it
won't slow the progress to a real open source solution

> Unless I'm missing something obvious, I don't see absolutely anything
> that could harm the chances of d80211 to make it to the mainline
> kernel.

Christoph et. all will insist that everything be EXPORT_SYMBOL_GPL.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-10-18  4:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061018001403.GA22990@devicescape.com>
2006-10-18  0:42 ` [Madwifi-devel] d80211: ANNOUNCE: DadWifi, a port of MadWifi to d80211 Kel Modderman
2006-10-18  1:51 ` Stephen Hemminger
2006-10-18  4:26   ` Pavel Roskin
2006-10-18  4:55     ` Stephen Hemminger [this message]
2006-10-18  6:20       ` [Madwifi-devel] " Pavel Roskin
2006-10-18 10:16 ` Christoph Hellwig
2006-10-18 15:27   ` Jiri Benc
2006-10-19  1:18   ` [Madwifi-devel] " Matt Brown
2006-10-19  2:08     ` Jim Thompson
2006-10-19  2:17       ` Matt Brown
2006-10-18  0:14 David Kimdon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061017215532.3d3c769a@dads-laptop \
    --to=shemminger@osdl.org \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=proski@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox