* Q: ieee80211_txb
@ 2005-05-29 10:47 Meelis Roos
2005-05-30 2:34 ` Zhu Yi
0 siblings, 1 reply; 2+ messages in thread
From: Meelis Roos @ 2005-05-29 10:47 UTC (permalink / raw)
To: netdev
I tried to understand the new 802.11 stack API and met some things I
couldn't understand by just looking at the code.
My main question is currently struct ieee80211_txb. How is it meant to
be used? How driver-specific is it - should it fit all drivers or does
it assume some specific DMA set-up?
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Q: ieee80211_txb
2005-05-29 10:47 Q: ieee80211_txb Meelis Roos
@ 2005-05-30 2:34 ` Zhu Yi
0 siblings, 0 replies; 2+ messages in thread
From: Zhu Yi @ 2005-05-30 2:34 UTC (permalink / raw)
To: Meelis Roos; +Cc: netdev
On Sun, 2005-05-29 at 13:47 +0300, Meelis Roos wrote:
> I tried to understand the new 802.11 stack API and met some things I
> couldn't understand by just looking at the code.
>
> My main question is currently struct ieee80211_txb. How is it meant to
> be used? How driver-specific is it - should it fit all drivers or does
> it assume some specific DMA set-up?
The ieee80211_txb should not be driver specific. ->fragments is struct
sk_buff, indicates the packet skb or the fragmentation skb list for
software based fragmentation. And others members are self explained.
Currently it fits the ipw* drivers (you see a reserved word is used), we
should change it to be more generic and provide enough info for every
wireless driver.
Thanks,
-yi
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-05-30 2:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-29 10:47 Q: ieee80211_txb Meelis Roos
2005-05-30 2:34 ` Zhu Yi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).