From: Arend van Spriel <arend@broadcom.com>
To: "C. McPherson" <ccmcphe@verizon.net>
Cc: <backports@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Netlink Question
Date: Tue, 12 Aug 2014 10:42:51 +0200 [thread overview]
Message-ID: <53E9D38B.1060509@broadcom.com> (raw)
In-Reply-To: <53E917AB.3020002@verizon.net>
+ 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.
Regards,
Arend
> Thanks in advance
> Clyde
>
> --
> 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
next prev parent reply other threads:[~2014-08-12 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 19:21 Netlink Question C. McPherson
2014-08-12 8:42 ` Arend van Spriel [this message]
2014-08-12 9:32 ` Krishna Chaitanya
2014-08-13 19:01 ` C. McPherson
2014-08-14 8:18 ` Arend van Spriel
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 20:33 netlink question Giacomo
2002-04-10 11:20 Balazs Scheidler
2002-04-11 11:41 ` jamal
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=53E9D38B.1060509@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=ccmcphe@verizon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.