[Top] [All Lists]

Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack

To: Sam Leffler <sam@xxxxxxxxx>
Subject: Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Mon, 6 Sep 2004 23:47:01 -0700
Cc: vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, acx100-devel@xxxxxxxxxxxxxxxxxxxxx, jt@xxxxxxxxxxxxxxxxxx, jkmaline@xxxxxxxxx, prism54-devel@xxxxxxxxxxx
In-reply-to: <200409062132.49356.sam@xxxxxxxxx>
References: <200408312111.02438.vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <757AB580-0030-11D9-9224-000A95AD0668@xxxxxxxxx> <20040906182328.08faf843.davem@xxxxxxxxxxxxx> <200409062132.49356.sam@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 6 Sep 2004 21:32:49 -0700
Sam Leffler <sam@xxxxxxxxx> wrote:

> Actually, this is the first time you've said anything to me about this code.  

I do remember telling you how much I was against this element of
your design.  At the time, you were not willing to rearchitect things
and you were in a sort-of bug-fix only mode.

> Perhaps you can point me at a description of what a "true network stack" 
> means 
> to you.

It means passing the 802.11 protocol packets into the networking
just like any other type of packet, via netif_rx() or netif_receive_skb().
Creating an ETH_P_80211 protocol type and registering the stack via
dev_add_pack() just like any other real protocol layer does.

Then responses generated in that 802.11 stack need to feed packets back
out to the network via the normal and usual methods of transmitting
packets in the networking, namely dev_queue_xmit().

That is exactly what my shell protocol layer does, and it is exactly
how a real 802.11 soft stack should be implemented and operate.

<Prev in Thread] Current Thread [Next in Thread>