From: Gabor Juhos <juhosg@openwrt.org>
To: Daniel Kuehn <daniel@kuehn.se>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ath9k-devel@lists.ath9k.org
Subject: Re: [PATCH] Seeing as alot of ath9k devices is PCI/PCIe or their mini equivalent it makes sense to set ATH9K_PCI to y by default
Date: Thu, 17 Nov 2011 16:13:53 +0100 [thread overview]
Message-ID: <4EC524B1.2070200@openwrt.org> (raw)
In-Reply-To: <20111109235757.79821a20@Artemis>
2011.11.09. 23:57 keltezéssel, Daniel Kuehn írta:
> from: Daniel Kuehn <daniel@kuehn.se>
>
> Most ath9k devices are PCI/PCIe based, therefor making PCI/PCIe support
> default y helps those porting a config from 2.6 kernel series
> from getting "non-functional" wireless drivers with 3.x kernel series.
>
> Signed-off-by: Daniel Kuehn <daniel@kuehn.se>
The option was enabled in the past but it has been removed a few months ago by
the following commit:
commit 64bd0821a3b66c3307d7a4ee5523e3e35ec2df0e
Author: Tao Ma <boyu.mt@taobao.com>
Date: Wed May 25 09:44:05 2011 +0800
wireless: Default to 'n' for 2 new added devices in Kconfig.
We make oldconfig every time when a new kernel arrives, but
if we don't have such a device(I guess this is the most common
case for a new device), the default value should be 'n' so
that the kernel size we build doesn't grow up too much quickly.
For anyone who has the device, it is OK for them to turn it on
by themselves.
Cc: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Tao Ma <boyu.mt@taobao.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
In my opinion it should not be added again.
Regards,
Gabor
next prev parent reply other threads:[~2011-11-17 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 22:57 [PATCH] Seeing as alot of ath9k devices is PCI/PCIe or their mini equivalent it makes sense to set ATH9K_PCI to y by default Daniel Kuehn
2011-11-17 15:13 ` Gabor Juhos [this message]
2011-11-17 15:39 ` Daniel Kuehn
2011-11-17 18:44 ` Gabor Juhos
2011-11-17 20:56 ` Daniel Kuehn
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=4EC524B1.2070200@openwrt.org \
--to=juhosg@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=daniel@kuehn.se \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).