From: Dan Williams <dcbw@redhat.com>
To: Pavel Ivanov <paivanof@gmail.com>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
"Jouni Malinen" <jmalinen@atheros.com>,
"Vasanthakumar Thiagarajan" <vasanth@atheros.com>,
"Senthil Balasubramanian" <senthilkumar@atheros.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath9k: make driver usable standalone
Date: Thu, 18 Aug 2011 14:20:15 -0500 [thread overview]
Message-ID: <1313695217.23920.4.camel@dcbw.foobar.com> (raw)
In-Reply-To: <CAG1a4rvQTA7UgxLOxu_cC88grjHttyjPD_4kyDhb7Y9FcBBkLQ@mail.gmail.com>
On Thu, 2011-08-18 at 00:01 -0400, Pavel Ivanov wrote:
> > Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
> > configuration tool.
>
> I've just tried to use iw and it didn't quite work for me. Maybe it's
> interfering with something installed in Ubuntu by default but
Ubuntu installs NetworkManager by default, so if you want to manually
control the wifi card you'll have to tell NM to ignore the wifi device,
or turn NM off temporarily.
> connect/disconnect commands didn't seem to do anything. And why these
> commands can be executed only as root?
Because poking and configuring hardware is a privileged operation; tools
like NetworkManager selectively poke holes through that wall and often
require administrator passwords to do it, but at the end of the day its
an operation that can affect security and stability, and that means it
needs to be privileged.
In the end, you probably want to be using wpa_supplicant instead of
trying to configure stuff with iw directly.
Dan
> Well, maybe in Ubuntu 11.10 it will work better.
>
>
> Pavel
>
>
> 2011/8/17 Gábor Stefanik <netrolller.3d@gmail.com>:
> > 2011/8/17 Pavel Ivanov <paivanof@gmail.com>:
> >>> WIRELESS_EXT is not required for configuring wireless on recent
> >>> kernels - in fact, the WEXT API is deprecated in favor of nl80211 now.
> >>
> >> Since what version it's deprecated? Do user-space tools know about this new API?
> >>
> >> Neither iwconfig nor iwlist worked for me without WIRELESS_EXT.
> >>
> >>
> >> Pavel
> >>
> >
> > Iwconfig and iwlist are themselves deprecated. Iw is the new wireless
> > configuration tool.
> >
> >>
> >> 2011/8/17 Gábor Stefanik <netrolller.3d@gmail.com>:
> >>> On Wed, Aug 17, 2011 at 5:28 AM, Pavel Ivanov <paivanof@gmail.com> wrote:
> >>>> When ath9k is the only wireless driver included in the build
> >>>> WIRELESS_EXT configuration option becomes undefined. Because of that
> >>>> driver becomes essentially unusable as you can't actually connect to
> >>>> any WiFi network. By including WIRELESS_EXT into Kconfig we ensure
> >>>> that build with ath9k and without other drivers (having WIRELESS_EXT
> >>>> selected in their Kconfig) is actually usable.
> >>>
> >>> WIRELESS_EXT is not required for configuring wireless on recent
> >>> kernels - in fact, the WEXT API is deprecated in favor of nl80211 now.
> >>>
> >>>>
> >>>> Signed-off-by: Pavel Ivanov <paivanof@gmail.com>
> >>>> ---
> >>>>
> >>>> diff --git a/drivers/net/wireless/ath/ath9k/Kconfig
> >>>> b/drivers/net/wireless/ath/ath9k/Kconfig
> >>>> index d9c08c6..2573f77 100644
> >>>> --- a/drivers/net/wireless/ath/ath9k/Kconfig
> >>>> +++ b/drivers/net/wireless/ath/ath9k/Kconfig
> >>>> @@ -11,6 +11,7 @@ config ATH9K
> >>>> select LEDS_CLASS
> >>>> select NEW_LEDS
> >>>> select ATH9K_COMMON
> >>>> + select WIRELESS_EXT
> >>>> ---help---
> >>>> This module adds support for wireless adapters based on
> >>>> Atheros IEEE 802.11n AR5008, AR9001 and AR9002 family
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" 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:[~2011-08-18 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 3:28 [PATCH] ath9k: make driver usable standalone Pavel Ivanov
2011-08-17 5:57 ` Gábor Stefanik
2011-08-17 15:56 ` Pavel Ivanov
2011-08-17 16:25 ` Gábor Stefanik
2011-08-17 22:51 ` Valdis.Kletnieks
2011-08-17 23:20 ` Larry Finger
2011-08-18 19:18 ` Dan Williams
2011-08-18 4:01 ` Pavel Ivanov
2011-08-18 5:19 ` Adrian Chadd
2011-08-18 19:20 ` Dan Williams [this message]
2011-08-18 19:30 ` Pavel Ivanov
2011-08-18 20:35 ` Dan Williams
2011-08-18 22:56 ` Pavel Ivanov
2011-08-19 1:25 ` Johannes Berg
2011-08-19 4:27 ` Pavel Ivanov
2011-08-18 21:26 ` Luis R. Rodriguez
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=1313695217.23920.4.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=jmalinen@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=netrolller.3d@gmail.com \
--cc=paivanof@gmail.com \
--cc=senthilkumar@atheros.com \
--cc=vasanth@atheros.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