radiotap.netbsd.org archive mirror
 help / color / mirror / Atom feed
From: "C. McPherson" <ccmcphe-H+0wwilmMs3R7s880joybQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: linux-wireless
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Re: Vendor Namespace Question
Date: Tue, 04 Nov 2014 15:18:39 -0500	[thread overview]
Message-ID: <5459349F.9020903@verizon.net> (raw)
In-Reply-To: <1415130476.2064.22.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>

Thanks so much for the info Johannes. I did notice that rx_status was 
getting full.  I'll go ahead and put it in skb->data, that's a good idea.
Clyde

On 11/04/2014 02:47 PM, Johannes Berg wrote:
> On Tue, 2014-11-04 at 13:37 -0500, C. McPherson wrote:
>> Hello all:
>> I was just trying to use the latest stable backports-3.18-rc1-1 and I
>> noticed that there is no longer structure members in the
>> ieee80211_rx_status structure for Vendor namespace information?  In my
>> backports 3.14 version I used them to add some register information to
>> the radiotap header in the lab. How does one use the vendor name space
>> without those structure members?
> We removed this from the Linux kernel because there was no driver using
> it and we needed the space for other purposes. That said, it shouldn't
> be too difficult to put it back by keeping the OUI/subtype also in the
> skb->data rather than the rx_status (which is now full enough to no
> longer have space for it, I believe)
>
> johannes
>
>

  parent reply	other threads:[~2014-11-04 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 18:37 Vendor Namespace Question C. McPherson
     [not found] ` <54591CF9.7030106-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2014-11-04 19:47   ` Johannes Berg
     [not found]     ` <1415130476.2064.22.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2014-11-04 20:18       ` C. McPherson [this message]
     [not found]         ` <5459349F.9020903-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2014-11-06 22:31           ` Johannes Berg
     [not found]             ` <1415313070.17015.19.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2014-11-12 20:55               ` C. McPherson

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=5459349F.9020903@verizon.net \
    --to=ccmcphe-h+0wwilmms3r7s880joybq@public.gmane.org \
    --cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).