From: Vladimir Kondratiev <vkondra@mail.ru>
To: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
Cc: acx100-devel@lists.sourceforge.net,
"David S. Miller" <davem@davemloft.net>,
greg chesson <greg@atheros.com>,
hadi@cyberus.ca, Jeff Garzik <jgarzik@pobox.com>,
"Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
netdev@oss.sgi.com, prism54-devel@prism54.org, sam@errno.com
Subject: Re: generic 802.11 stack
Date: Wed, 15 Sep 2004 08:44:38 +0300 [thread overview]
Message-ID: <200409150844.45242.vkondra@mail.ru> (raw)
In-Reply-To: <20040915031732.GL7839@ruslug.rutgers.edu>
[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]
Let me answer to the set of questions raised:
- dual licensing: I am not ready to answer for legal. I will discuss with
proper people and answer.
- code style: regardless of answer on question above, I intend to do Linux
work and will not care about compatibility macros. I really dislike such
macros, they do make code hard to understand.
- information sharing (driver-stack): good question indeed. I am currently
evaluating it. This far, I think I will supply some standard link layer
information per packet. Like rate, RSSI etc. For Tx, it will include also
crypto key for hardware assisted encryption, type of protection (RTS/CTS
etc.) I believe it should be sufficient. To prove it, I am going to write
some dummy .11 driver that will be capable to simulate any Rx, with user
interface for feeding packets. I will use this driver to debug stack.
It is complex issue to support all combination of job separation between host
and NIC, I will choose some model like "NIC do almost nothing" and will
develop around it.
Vladimir.
On Wednesday 15 September 2004 06:17, Luis R. Rodriguez wrote:
LR> On Tue, Sep 14, 2004 at 11:05:45PM -0400, Jeff Garzik wrote:
LR> > On Tue, Sep 14, 2004 at 11:02:11PM -0400, Luis R. Rodriguez wrote:
LR> > > I proposed dual licensing not to specifically allow clear
compatibility LR> > > among linux and the BSDs on the 802.11 work, but to
allow BSDers to do LR> > > whatever they want with what we come up with --
help with code sharing. LR> >
LR> >
LR> > Overall, He Who Writes The Code Gets To Choose.
LR> >
LR> > My own personal opinion is that the BSD license goes against the stated
LR> > spirit of Linux -- contribute back. But that's just me.
LR> >
LR>
LR> Agreed -- but in this case I feel we're the bigger crowd so I wanted to
LR> address to the *author* that I feel we should be considerate to the BSD
LR> crowd.
LR>
LR> Luis
LR>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-15 5:44 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 18:11 [RFC] acx100 inclusion in mainline; generic 802.11 stack Denis Vlasenko
2004-08-31 18:21 ` Jeff Garzik
2004-08-31 19:14 ` Vladimir Kondratiev
2004-08-31 21:37 ` Luis R. Rodriguez
2004-08-31 22:06 ` Vladimir Kondratiev
2004-09-01 2:22 ` Jouni Malinen
2004-09-02 20:24 ` Vladimir Kondratiev
2004-09-02 20:33 ` Jeff Garzik
2004-09-03 17:37 ` Vladimir Kondratiev
2004-09-03 20:29 ` Jeff Garzik
2004-09-06 18:13 ` Sam Leffler
2004-09-06 18:57 ` Vladimir Kondratiev
2004-09-06 19:30 ` Sam Leffler
2004-09-06 20:09 ` Vladimir Kondratiev
2004-09-06 23:04 ` Sam Leffler
2004-09-07 1:23 ` David S. Miller
2004-09-07 4:32 ` Sam Leffler
2004-09-07 6:47 ` David S. Miller
2004-09-07 17:22 ` Vladimir Kondratiev
2004-09-07 17:32 ` David S. Miller
2004-09-07 18:06 ` Vladimir Kondratiev
2004-09-07 18:08 ` David S. Miller
2004-09-07 18:41 ` Vladimir Kondratiev
2004-09-07 19:10 ` David S. Miller
2004-09-07 19:54 ` Vladimir Kondratiev
2004-09-09 2:40 ` Sam Leffler
2004-09-09 4:36 ` Luis R. Rodriguez
2004-09-07 17:03 ` [RFC] acx100 inclusion in mainline; " greg chesson
2004-09-07 17:10 ` David S. Miller
2004-09-07 18:14 ` greg chesson
2004-09-07 18:16 ` David S. Miller
2004-09-08 7:38 ` jamal
2004-09-08 16:02 ` greg chesson
2004-09-08 19:51 ` Vladimir Kondratiev
2004-09-08 20:52 ` greg chesson
2004-09-08 21:54 ` Vladimir Kondratiev
2004-09-09 17:06 ` greg chesson
2004-09-12 18:03 ` Vladimir Kondratiev
2004-09-13 0:09 ` Jeff Garzik
2004-09-13 0:45 ` David S. Miller
2004-09-15 17:57 ` James Ketrenos
2004-09-13 0:14 ` David S. Miller
2004-09-13 5:39 ` Vladimir Kondratiev
2004-09-13 5:50 ` Jeff Garzik
2004-09-13 23:21 ` David S. Miller
2004-09-14 5:14 ` Vladimir Kondratiev
2004-09-14 5:35 ` David S. Miller
2004-09-14 23:55 ` Luis R. Rodriguez
2004-09-15 0:11 ` Jeff Garzik
2004-09-15 0:51 ` greg chesson
2004-09-15 1:19 ` Jeff Garzik
2004-09-15 3:02 ` Luis R. Rodriguez
2004-09-15 3:05 ` Jeff Garzik
2004-09-15 3:17 ` Luis R. Rodriguez
2004-09-15 5:44 ` Vladimir Kondratiev [this message]
2004-09-15 14:47 ` greg chesson
2004-09-15 15:55 ` David S. Miller
2004-09-15 16:48 ` Sam Leffler
2004-09-15 17:06 ` David S. Miller
2004-09-28 12:20 ` [RFC] acx100 inclusion in mainline; " Luis R. Rodriguez
2004-09-28 20:29 ` Vladimir Kondratiev
2004-09-29 0:48 ` Luis R. Rodriguez
2004-09-29 7:10 ` Vladimir Kondratiev
2004-09-29 8:00 ` Luis R. Rodriguez
2004-10-01 14:30 ` Vladimir Kondratiev
2004-10-01 22:53 ` David S. Miller
2004-10-01 23:25 ` Vladimir Kondratiev
2004-10-02 0:11 ` David S. Miller
2004-09-08 21:19 ` [Acx100-devel] Re: [RFC] acx100 inclusion in mainline; " Denis Vlasenko
2004-09-09 3:31 ` Sam Leffler
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=200409150844.45242.vkondra@mail.ru \
--to=vkondra@mail.ru \
--cc=acx100-devel@lists.sourceforge.net \
--cc=davem@davemloft.net \
--cc=greg@atheros.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.org \
--cc=sam@errno.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.