| 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 18:23:28 -0700 |
| Cc: | vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, acx100-devel@xxxxxxxxxxxxxxxxxxxxx, jt@xxxxxxxxxxxxxxxxxx, jkmaline@xxxxxxxxx, prism54-devel@xxxxxxxxxxx |
| In-reply-to: | <757AB580-0030-11D9-9224-000A95AD0668@errno.com> |
| References: | <200408312111.02438.vda@port.imtp.ilyichevsk.odessa.ua> <757AB580-0030-11D9-9224-000A95AD0668@errno.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 6 Sep 2004 11:13:31 -0700 Sam Leffler <sam@xxxxxxxxx> wrote: > I've suggested this code as a good starting point for a "generic 802.11 > stack" but received only misinformed responses. Sam, I've told you multiple times why your stack isn't a good starting point. It isn't implemented as a true network stack, like IPV4, Appletalk, etc. Instead it's a gross input packet hooked packet eater thing that's an ugly wart bolted onto the side of the driver API. |
| Previous by Date: | Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack, Sam Leffler |
|---|---|
| Next by Date: | Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack, Sam Leffler |
| Previous by Thread: | Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack, Sam Leffler |
| Next by Thread: | Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack, Sam Leffler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |