From: Zhu Yi <yi.zhu@intel.com>
To: Meelis Roos <mroos@linux.ee>
Cc: netdev@oss.sgi.com
Subject: Re: Q: ieee80211_txb
Date: Mon, 30 May 2005 10:34:18 +0800 [thread overview]
Message-ID: <1117420458.24850.36.camel@debian.sh.intel.com> (raw)
In-Reply-To: <Pine.SOC.4.61.0505291343360.4341@math.ut.ee>
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
prev parent reply other threads:[~2005-05-30 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 10:47 Q: ieee80211_txb Meelis Roos
2005-05-30 2:34 ` Zhu Yi [this message]
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=1117420458.24850.36.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=mroos@linux.ee \
--cc=netdev@oss.sgi.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 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).