public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Gordon <digigordo@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: Rate information in ad-hoc and mesh mode
Date: Tue, 20 Oct 2009 11:41:09 -0400	[thread overview]
Message-ID: <86201b3f0910200841w7e512fa3i31012477cbf55d56@mail.gmail.com> (raw)
In-Reply-To: <200910201714.34866.hs4233@mail.mn-solutions.de>

I am using version 2.6.28 of the kernel.  We are using our own
wireless driver.  However, the problem does not appear to be in the
driver.  The iw utility uses the SIOCGIWRATE ioctl to get rate
information.  This ioctl is handled by the ieee80211_ioctl_giwrate
function in net/mac80211/wext.c in the 2.6.28 version of the kernel.
This function returns immediately if sdata->vif.type !=
NL80211_IFTYPE_STATION, which will be the case for ad-hoc mode.



On Tue, Oct 20, 2009 at 11:14 AM, Holger Schurig
<hs4233@mail.mn-solutions.de> wrote:
>> I notice that the ieee80211_ioctl_giwrate function in wext.c only
>> returns rate information for stations associated to an AP.  It does
>> not return rate information for stations operating in ad-hoc mode or
>> as a mesh point.  Is there a reason this function is not supported in
>> those modes?  Is this a deliberate decision or just an oversight?
>
> You need to give more context. What driver, what kernel?
>
>
> A quick
>
>   ack-grep ieee80211_ioctl_giwrate include/net include/linux \
>                                    net/wireless net/mac80211 \
>                                    drivers/net/wireless
>
> didn't reveal the function you've mentioned, at least not in the
> current wireless-testing kernel.
>
> --
> http://www.holgerschurig.de
>

  reply	other threads:[~2009-10-20 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 14:10 Rate information in ad-hoc and mesh mode Charles Gordon
2009-10-20 15:14 ` Holger Schurig
2009-10-20 15:41   ` Charles Gordon [this message]
2009-10-21  1:10 ` Johannes Berg

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=86201b3f0910200841w7e512fa3i31012477cbf55d56@mail.gmail.com \
    --to=digigordo@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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