From: C. McPherson <ccmcphe@verizon.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] iwpriv and ath9k driver
Date: Sun, 30 Oct 2011 13:23:16 -0400 [thread overview]
Message-ID: <4EAD8804.90306@verizon.net> (raw)
In-Reply-To: <1319584766.14989.YahooMailNeo@web38002.mail.mud.yahoo.com>
I am using iwpriv (Private IOCTL's). You have to modify cfg80211
(should be under net/wireless). I put my iwpriv's in the wext-compat.c
file. You have to do this because ath9k uses mac80211 API and cfg80211 API.
-Tex
On 10/25/2011 07:19 PM, just login wrote:
> Hi,
>
> I have a recent (daily) from compat-wireless and have the (ath9k
> AR9160) driver working fine.
>
> I wanted to play with private extensions, if any - with iwpriv and see
> "No private ioctls" for the wlan0 interface.
>
> Is this expected or should I be using some compile time flags to
> enable visibility of private extensions to iwpriv for the ath9k driver.
>
> Thanks
> -J
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111030/e9f2b7ca/attachment.htm
prev parent reply other threads:[~2011-10-30 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <195AAF39-2B75-4D7B-A1E8-CACFD47717D1@comcast.net>
2011-10-20 20:27 ` [ath9k-devel] Fwd: Kernel warning in ath9k related to wpa_supplicant scanning Bryan Phillippe
2011-10-24 23:29 ` Mohammed Shafi
2011-10-25 23:19 ` [ath9k-devel] iwpriv and ath9k driver just login
2011-10-30 17:23 ` C. McPherson [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=4EAD8804.90306@verizon.net \
--to=ccmcphe@verizon.net \
--cc=ath9k-devel@lists.ath9k.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.