All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Fix a WARNING in suspend/resume with IBSS
Date: Sat, 02 Jun 2012 20:30:38 +0200	[thread overview]
Message-ID: <4FCA5BCE.8080104@openwrt.org> (raw)
In-Reply-To: <CAHD-aq+wyT2Rm-uYaA34Wspm1+J79=eyCbpiD=T4ti3Bv-MP9g@mail.gmail.com>

On 2012-06-02 8:14 PM, Guido Iribarren wrote:
> On Sat, Jun 2, 2012 at 2:45 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
>>
>> The sets are mutually exclusive, and there are implied sets of each
>> interface with a max number of 1. So for example, in iwlwifi we don't
>> advertise IBSS in the combinations at all, because it's not compatible
>> with anything. In your case, I think the same applies, since you said
>>
>>        if the first interface is ADHOC we cannot have any other
>>        interface. we cannot add an ADHOC interface if there is already
>>        an interface is present
> 
> I've been following the thread and still can't get this confusion out
> of my head:
> i'm currently using kernel 3.3.2 (openwrt trunk r31439), with Atheros
> AR9285 and i can succesfully combine IBSS interface with AP or STA
> modes...
> 
> # iw dev
> phy#0
> 	Interface wlan0-1
> 		ifindex 11
> 		type AP
> 	Interface wlan0-2
> 		ifindex 10
> 		type IBSS
> 	Interface wlan0
> 		ifindex 9
> 		type AP
> 
> So, does this patch mean this functionality will be lost in future
> versions of ath9k?
> or maybe it is officially unsupported and openwrt has patches applied?
> or, even worse, I completely misunderstood what you're talking about?
> (in that case i'm sorry for the noise)
It's officially unsupported, OpenWrt has patches to enable it.

- Felix

WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: Guido Iribarren <guidoiribarren@buenosaireslibre.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Rodriguez Luis <rodrigue@qca.qualcomm.com>,
	ath9k-devel@lists.ath9k.org,
	Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>,
	Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Subject: Re: [ath9k-devel] [PATCH] ath9k: Fix a WARNING in suspend/resume with IBSS
Date: Sat, 02 Jun 2012 20:30:38 +0200	[thread overview]
Message-ID: <4FCA5BCE.8080104@openwrt.org> (raw)
In-Reply-To: <CAHD-aq+wyT2Rm-uYaA34Wspm1+J79=eyCbpiD=T4ti3Bv-MP9g@mail.gmail.com>

On 2012-06-02 8:14 PM, Guido Iribarren wrote:
> On Sat, Jun 2, 2012 at 2:45 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
>>
>> The sets are mutually exclusive, and there are implied sets of each
>> interface with a max number of 1. So for example, in iwlwifi we don't
>> advertise IBSS in the combinations at all, because it's not compatible
>> with anything. In your case, I think the same applies, since you said
>>
>>        if the first interface is ADHOC we cannot have any other
>>        interface. we cannot add an ADHOC interface if there is already
>>        an interface is present
> 
> I've been following the thread and still can't get this confusion out
> of my head:
> i'm currently using kernel 3.3.2 (openwrt trunk r31439), with Atheros
> AR9285 and i can succesfully combine IBSS interface with AP or STA
> modes...
> 
> # iw dev
> phy#0
> 	Interface wlan0-1
> 		ifindex 11
> 		type AP
> 	Interface wlan0-2
> 		ifindex 10
> 		type IBSS
> 	Interface wlan0
> 		ifindex 9
> 		type AP
> 
> So, does this patch mean this functionality will be lost in future
> versions of ath9k?
> or maybe it is officially unsupported and openwrt has patches applied?
> or, even worse, I completely misunderstood what you're talking about?
> (in that case i'm sorry for the noise)
It's officially unsupported, OpenWrt has patches to enable it.

- Felix

  reply	other threads:[~2012-06-02 18:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01  6:39 [ath9k-devel] [PATCH] ath9k: Fix a WARNING in suspend/resume with IBSS Mohammed Shafi Shajakhan
2012-06-01  6:39 ` Mohammed Shafi Shajakhan
2012-06-01  6:44 ` [ath9k-devel] " Johannes Berg
2012-06-01  6:44   ` Johannes Berg
2012-06-01  7:09   ` [ath9k-devel] " Mohammed Shafi Shajakhan
2012-06-01  7:09     ` Mohammed Shafi Shajakhan
2012-06-01  7:13     ` [ath9k-devel] " Johannes Berg
2012-06-01  7:13       ` Johannes Berg
2012-06-02 15:27       ` [ath9k-devel] " Mohammed Shafi Shajakhan
2012-06-02 15:27         ` Mohammed Shafi Shajakhan
2012-06-02 17:45         ` [ath9k-devel] " Johannes Berg
2012-06-02 17:45           ` Johannes Berg
2012-06-02 18:14           ` [ath9k-devel] " Guido Iribarren
2012-06-02 18:14             ` Guido Iribarren
2012-06-02 18:30             ` Felix Fietkau [this message]
2012-06-02 18:30               ` Felix Fietkau
2012-06-04 15:46           ` Mohammed Shafi Shajakhan
2012-06-04 15:46             ` Mohammed Shafi Shajakhan

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=4FCA5BCE.8080104@openwrt.org \
    --to=nbd@openwrt.org \
    --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.