From: Arend van Spriel <arend@broadcom.com>
To: "C. McPherson" <ccmcphe@verizon.net>,
Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: <backports@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Netlink Question
Date: Thu, 14 Aug 2014 10:18:15 +0200 [thread overview]
Message-ID: <53EC70C7.2030008@broadcom.com> (raw)
In-Reply-To: <53EBB602.7060901@verizon.net>
On 08/13/2014 09:01 PM, C. McPherson wrote:
>
> On 08/12/2014 05:32 AM, Krishna Chaitanya wrote:
>> On Tue, Aug 12, 2014 at 2:12 PM, Arend van Spriel <arend@broadcom.com>
>> wrote:
>>> + linux-wireless
>>>
>>> Not really a backports question so adding linux-wireless
>>>
>>> On 08/11/2014 09:21 PM, C. McPherson wrote:
>>>> I have some private WiFi ioctl's that are associated with a couple of
>>>> drivers and I would like to convert those private ioctl's into netlink.
>>>> Does anyone know if there is any documentation on this or a URL that I
>>>> could reference before I attempt?
>>>
>>> I guess the "private WiFi ioctl's" you are referring to are the ones
>>> used in Android wpa_supplicant driver_cmd lib? There is no real
>>> cookbook on how to add nl80211 commands (maybe I am wrong here), but
>>> there are sufficient patches to be found in the linux-wireless
>>> archive. A recent one about key management offload adds a couple of
>>> commands and attributes which may give an idea what is needed:
>>>
>>> http://mid.gmane.org/1406076875-8549-1-git-send-email-clanctot@qca.qualcomm.com
>>>
>>>
>>> Obviously, you need to modify the "couple of drivers" to deal with
>>> the nl80211 netlink commands.
>>>
>> We had same requirement in our driver, we have patched the iw to send
>> custom commands specific to our hardware and used NL80211_CMD_TESTMODE
>> to process and send it to driver.
>> --
>> To unsubscribe from this list: send the line "unsubscribe backports" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> Yeah thanks a lot, I could use NL80211_CMD_TESTMODE, I'll have to check
> that out. I was also thinking about using NL80211_CMD_VENDOR. These
> IOCTL's are not and will not be used by wpa_supplicant (but I will check
> out the URL you sent), they are just some custom commands we use with
> several chipsets.
If you are using recent kernel or backports package, I would say go for
the vendor command. It is quite similar to TESTMODE except that it is
always enabled, ie. not depending on kernel config.
However, if the custom commands would add functionality that might be
interesting to linux-wireless drivers in general you may consider adding
them as nl80211 commands.
Regards,
Arend
prev parent reply other threads:[~2014-08-14 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53E917AB.3020002@verizon.net>
2014-08-12 8:42 ` Netlink Question Arend van Spriel
2014-08-12 9:32 ` Krishna Chaitanya
2014-08-13 19:01 ` C. McPherson
2014-08-14 8:18 ` Arend van Spriel [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=53EC70C7.2030008@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=ccmcphe@verizon.net \
--cc=chaitanya.mgit@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;
as well as URLs for NNTP newsgroup(s).