From: Bruno Randolf <br1@einfach.org>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
linville@tuxdriver.com, yi.zhu@intel.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] iwlwif: remove compilation warnings iwl_add_radiotap
Date: Sat, 12 Jul 2008 14:57:06 +0200 [thread overview]
Message-ID: <200807121457.06795.br1@einfach.org> (raw)
In-Reply-To: <1ba2fa240807100747g285b5ff0of81bf619ad9ee3b9@mail.gmail.com>
On Thursday 10 July 2008 16:47:57 Tomas Winkler wrote:
> On Thu, Jul 10, 2008 at 4:52 PM, Johannes Berg
>
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2008-07-10 at 15:25 +0300, Tomas Winkler wrote:
> >> > what about using the generic function to add the radiotap header from
> >> > mac80211? it should be flexible enough to handle all devices by now.
> >>
> >> Why not go ahead.
> >
> > I always thought you were adding 11n stuff, but if that's not the case
> > (and we may make mac80211 do that at some point) then that'd be a nice
> > code removal.
>
> I have never really looked into radio tap so I don't want to make any
> statements here. If the 11n part can be done in mac80211 why not.
hi!
i'm currently working on a patch removing iwl's own radiotap header. while
doing that i noticed, that we currently don't have a field in
ieee80211_rx_status for the modulation used. for example iwl knows if the
frame was demodulated using CCK (RX_RES_PHY_FLAGS_MOD_CCK_MSK), thus it's
able to differentiate between B and G modes. in mac80211 we can't do that
right now.
i guess we could deduct the modulation from the rate
1, 2, 5.5, 11 -> CCK
everything else -> OFDM
but i'm not sure if this is always true. is there any hardware that also does
PBCC? also what about CCK-OFDM modes (b/g interoperability), do we have any
way to identify these?
what do you think, should we explicitly make a modulation field in rx_status
or should we implicitly deduct the modulation from the rates?
bruno
next prev parent reply other threads:[~2008-07-12 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 11:28 [PATCH 1/1] iwlwif: remove compilation warnings iwl_add_radiotap Tomas Winkler
2008-07-10 11:42 ` Bruno Randolf
2008-07-10 12:25 ` Tomas Winkler
2008-07-10 13:52 ` Johannes Berg
2008-07-10 14:47 ` Tomas Winkler
2008-07-12 12:57 ` Bruno Randolf [this message]
2008-07-12 21:34 ` Tomas Winkler
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=200807121457.06795.br1@einfach.org \
--to=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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