From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kris Reeves <myndzi@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Fwd: RTL8192CU / Kconfig
Date: Sat, 27 Apr 2013 10:02:58 -0500 [thread overview]
Message-ID: <517BE8A2.3020202@lwfinger.net> (raw)
In-Reply-To: <CABH51ZbDsx9hg9NtafyOk__62O=yO1sKkW2bf_DHEghSwSd=EQ@mail.gmail.com>
On 04/27/2013 07:02 AM, Kris Reeves wrote:
> This file:
> https://github.com/raspberrypi/linux/blob/rpi-3.6.y/drivers/net/wireless/rtl8192cu/Kconfig
>
> Should, I believe, include select statements for WIRELESS_EXT,
> WEXT_PRIV, and (maybe?) WEXT_SPY (I added it preemptively after the
> first two stopped compilation...)
All three of those are selected in net/wireless/Kconfig, thus they never need to
be selected by any specific wireless driver. Once you have NET defined, and are
not building for the S390 architecture, they should be automatic.
> The drivers won't compile without those options, but can be enabled in
> situations where they are not set.
>
> I realize this is the raspberry pi github page, but from what I can
> tell, these files didn't originate there and this driver is in staging
> on its way to mainline(?)
That driver has never been in staging - it went directly to mainline in kernel
2.6.38, i.e. more than two years ago.
> This file:
> https://github.com/torvalds/linux/blob/master/drivers/net/wireless/rtlwifi/Kconfig
>
> appears to be the equivalent and it doesn't look like it contains the
> relevant lines. I'm uncertain if they are necessary here.
As stated earlier, they are not needed in mainline.
> If you would, please inform me of the correct way to determine who I
> should report something like this to and how! I know there are various
> bugtrackers about but I can't seem to work out where I should go with
> it.
I am convinced that this is not a problem for mainline. I have not used any of
the ARM architectures, and it may be a problem there, but I have no way to test.
If so, the proper place to submit a patch would be the appropriate ARM tree.
Make certain that cfg80211 and mac80211 have been selected. If you are still
having a problem, post the .config that you are using *without* changing any of
the selection rules for the RTL8192CU.
I have read of alignment problems for the RPi in the lower-level USB routines
that affect rtl8192cu, but I don't know any of the details.
Larry
prev parent reply other threads:[~2013-04-27 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABH51ZYepRMcmW4wFUmOf9dcnB4X0X377mmwSXNo9AQGbsNAxA@mail.gmail.com>
2013-04-27 12:02 ` Fwd: RTL8192CU / Kconfig Kris Reeves
2013-04-27 15:02 ` Larry Finger [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=517BE8A2.3020202@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=myndzi@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;
as well as URLs for NNTP newsgroup(s).