Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@adurom.com>
To: Eugene <wifi.mailing.list@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Custom commands for cfg80211 based driver (like iwpriv)
Date: Mon, 14 Jan 2013 09:18:59 +0200	[thread overview]
Message-ID: <87txqkz0yk.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CAMvjH0A69ZBCZc5qjm_cUYj3bDzSmneaz1u9CsPcJEm2T0Q1iw@mail.gmail.com> (Eugene's message of "Fri, 11 Jan 2013 13:32:05 +0200")

Eugene <wifi.mailing.list@gmail.com> writes:

> How to add custom configuration command for cfg80211 based driver.
>
> For WEXT was private IOCtls (iwpriv).
>
> What the recommended way for nl80211/cfg80211?

Luckily private commands are now banned, it was such a mess. Now you add
a new generic command to nl80211/cfg80211 so that all drivers can use
it. The benefit is that the driver can be changed without any
modifications to user space.

Only exceptions are NL80211_CMD_TESTMODE for low level factory/RF tests
and debugfs for developer debugging purposes.

-- 
Kalle Valo

  reply	other threads:[~2013-01-14  7:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 11:32 Custom commands for cfg80211 based driver (like iwpriv) Eugene
2013-01-14  7:18 ` Kalle Valo [this message]
2013-01-14 10:01   ` Eugene
2013-01-14 12:12     ` Julian Calaby
2013-01-14 12:50       ` Eugene
2013-01-14 13:38       ` Kalle Valo
2013-01-14 23:50         ` Julian Calaby
     [not found]     ` <87pq18yqrk.fsf@purkki.adurom.net>
     [not found]       ` <CAMvjH0DMZR65mHn2SY4gU6EOrpkC7h4mOqwLxCZtpbTFZxaa8A@mail.gmail.com>
     [not found]         ` <87libwynnt.fsf@purkki.adurom.net>
     [not found]           ` <CAMvjH0AbJ5ytfxxijuGMbNA2RPQGUR8iZSrrbZw1xcCPxdxD8Q@mail.gmail.com>
2013-01-14 13:47             ` Kalle Valo

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=87txqkz0yk.fsf@purkki.adurom.net \
    --to=kvalo@adurom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wifi.mailing.list@gmail.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