From: Cedric Sodhi <manday@gmx.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Fighting with the driver
Date: Wed, 23 Feb 2011 17:56:48 +0100 [thread overview]
Message-ID: <20110223165648.GB1988@fly> (raw)
Hello everyone,
I'd like to ask for some help from you getting a
TL-WN721N
presumably based upon an Atheros 9271 chipset to work.
That's of course my priority, but I also have some questions, trying to
understand why it is so difficult to get this device to work.
So first of all, I have naively tried to simply compile the kernel with
CONFIG_ATH9K_HTC=y
and with the according ar9271.fw in /lib/firmware. It didn't work, the
device would not respond properly. My first question:
IF the correct drivers for this device exist, why are they not in the
kernel? Why is it not possible to have a specific CONFIG_ line in the
kernel that allows me to use my device - why does it have to get
complicated?
So after this didn't work I made some research and basically ended up
at
http://wireless.kernel.org/en/users/Drivers/ath9k_htc
I followed that guide, selecting, for reasons that remain unclear to me,
the required entries (as listed in that guide) as Module. I then tried
to make compat-wireless which unexpectedly requested that I also
compiled
CONFIG_CFG80211=m
instead of =y. So I did that. Question: Why is there no mention of that
in the guide?
I did that. And then make said, that
CONFIG_CFG80211_WEXT will be deactivated or not working
because CONFIG_WIRELESS_EXT=n and that iwconfig will not work. Well,
first of all I figured no way to enable WIRELESS_EXT, how would I? And
then, question: Why is that happening only for the ath9k_hcl driver from
compat-wireless? iwconfig works fine with the kernel-shipped ath9k_hcl
(although latter does not work with the chipset).
I then restarted, but I just got a couple of errors when wpa_supplicant
tried to start
ioctl[SIO...]: Operation not supported
which, I assume, has to do with wext being unfunctional. So what now? I
have to enable WIRELESS_EXT somehow? How? And why is there no mention of
all this in that guide?
Thanks for your help!
next reply other threads:[~2011-02-23 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 16:56 Cedric Sodhi [this message]
2011-02-23 17:23 ` [ath9k-devel] Fighting with the driver Cedric Sodhi
2011-02-24 15:23 ` Petr Štetiar
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=20110223165648.GB1988@fly \
--to=manday@gmx.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.