netdev
[Top] [All Lists]

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

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack
From: jamal <hadi@xxxxxxxxxx>
Date: 08 Sep 2004 03:38:36 -0400
Cc: greg chesson <greg@xxxxxxxxxxx>, sam@xxxxxxxxx, vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx, acx100-devel@xxxxxxxxxxxxxxxxxxxxx, jt@xxxxxxxxxxxxxxxxxx, jkmaline@xxxxxxxxx, prism54-devel@xxxxxxxxxxx
In-reply-to: <20040907101027.7547e591.davem@xxxxxxxxxxxxx>
Organization: jamalopolis
References: <200408312111.02438.vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <757AB580-0030-11D9-9224-000A95AD0668@xxxxxxxxx> <20040906182328.08faf843.davem@xxxxxxxxxxxxx> <200409062132.49356.sam@xxxxxxxxx> <413DE9ED.30300@xxxxxxxxxxx> <20040907101027.7547e591.davem@xxxxxxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Tue, 2004-09-07 at 13:10, David S. Miller wrote:
> On Tue, 07 Sep 2004 10:03:41 -0700
> greg chesson <greg@xxxxxxxxxxx> wrote:
> 
> > What about eth_type_trans()?
> 
> It determines the protocol type from the ethernet header
> fields.  It is a simple shorthand header field fetcher,
> not a protocol stack.
> 
> You would need a eth80211_type_trans() for wireless
> drivers too, and surprise surprise my skeleton 802.11
> stack code in fact does exactly this.

Or as Andi has been suggesting for sometime, not invoke it all ;->
This is possible if the DMA descriptor already has all the info
needed (quiet a few modern hardware can be programmed to do this).
.. er, at the driver level. So this is not "a gross input packet
hooked eater thing that's an ugly wart bolted onto the
side of the driver API.";->

cheers,
jamal




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