From: Daniel Kuehn <daniel@kuehn.se>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [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 21:56:31 +0100 [thread overview]
Message-ID: <20111117215631.2c2064b1@Artemis> (raw)
In-Reply-To: <4EC5562B.4050001@openwrt.org>
On Thu, 17 Nov 2011 19:44:59 +0100
Gabor Juhos <juhosg@openwrt.org> wrote:
> 2011.11.17. 16:39 keltez?ssel, Daniel Kuehn ?rta:
>
> > I agree with you there if it was removed before, maybe then only the help
> > section of ath9k should be changed to say that you have to enable either
> > PCI/PCIe or AHB support for it to work?
>
> Yes, adding a comment there would make sense, although that does not prevent
> to build ath9k without bus support.
Yeah, that is the initial problem I found that I wanted to try and patch, but
seeing as it only stands between either always enabling it, or forcing one or
the other bus always on if you choose ath9k I don't know what else could be
done except note in the help that you also need to enable bus support.
I haven't poked around that much with Kconfig but it clearly seems like there
isn't a way to default select y but make it possible to disable it...
So there doesn't seem to be a clear way to automagically include the most
common bus support for ath9k.
>
> -Gabor
Kind regards,
Daniel Kuehn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111117/dfc990f7/attachment.pgp
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Kuehn <daniel@kuehn.se>
To: Gabor Juhos <juhosg@openwrt.org>
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 21:56:31 +0100 [thread overview]
Message-ID: <20111117215631.2c2064b1@Artemis> (raw)
In-Reply-To: <4EC5562B.4050001@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Thu, 17 Nov 2011 19:44:59 +0100
Gabor Juhos <juhosg@openwrt.org> wrote:
> 2011.11.17. 16:39 keltezéssel, Daniel Kuehn írta:
>
> > I agree with you there if it was removed before, maybe then only the help
> > section of ath9k should be changed to say that you have to enable either
> > PCI/PCIe or AHB support for it to work?
>
> Yes, adding a comment there would make sense, although that does not prevent
> to build ath9k without bus support.
Yeah, that is the initial problem I found that I wanted to try and patch, but
seeing as it only stands between either always enabling it, or forcing one or
the other bus always on if you choose ath9k I don't know what else could be
done except note in the help that you also need to enable bus support.
I haven't poked around that much with Kconfig but it clearly seems like there
isn't a way to default select y but make it possible to disable it...
So there doesn't seem to be a clear way to automagically include the most
common bus support for ath9k.
>
> -Gabor
Kind regards,
Daniel Kuehn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-17 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 22:57 [ath9k-devel] [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-09 22:57 ` Daniel Kuehn
2011-11-17 15:13 ` [ath9k-devel] " Gabor Juhos
2011-11-17 15:13 ` Gabor Juhos
2011-11-17 15:39 ` [ath9k-devel] " Daniel Kuehn
2011-11-17 15:39 ` Daniel Kuehn
2011-11-17 18:44 ` [ath9k-devel] " Gabor Juhos
2011-11-17 18:44 ` Gabor Juhos
2011-11-17 20:56 ` Daniel Kuehn [this message]
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=20111117215631.2c2064b1@Artemis \
--to=daniel@kuehn.se \
--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.