Ben Greear wrote:
> For the third set, why limit to a single interface. Can't we run IBSS + AP
> (and plus stations, for that matter), all at the same time with ath9k?
TSF would jump around since the HW would sync with the
received beacons and this will happen in both IBSS and station
mode. Hence
Building with the attached random configuration file,
ERROR: "cfg80211_wext_siwscan"
[drivers/net/wireless/orinoco/orinoco.ko] undefined!
ERROR: "cfg80211_wext_giwretry"
[drivers/net/wireless/orinoco/orinoco.ko] undefined!
ERROR: "cfg80211_wext_siwmode"
[drivers/net/wireless/orinoco/orinoco.ko] un
>>> "closed" is rather misleading, since you most certainly should *not*
>do
>>> dev_close() [and don't, but how should I know reading the commit
>log?]
>>>
>>> johannes
>>>
>>
>> Yes, I see.
>> I meant that actually stop_ap leaves device in state similar to
>ndo_stop,
>> where it is non opera
Hey Bob,
Thank you for your fast reply. I did a little more research the day
after your reply and I succeeded on it.
The issue was that the kernel's regulatory domain isn't set by default.
# iw reg get
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 40), (N/A, 2
On 04/07/2015 09:33 AM, Ben Greear wrote:
> On 04/06/2015 10:17 PM, Janusz Dziedzic wrote:
>> On 7 April 2015 at 07:12, Michal Kazior wrote:
>>> On 7 April 2015 at 02:39, Ben Greear wrote:
Has anyone tried running ath10k to ath9k IBSS?
I'm trying this with a somewhat hacked 4.0-rc6
Rafał Miłecki writes:
> Signed-off-by: Rafał Miłecki
> ---
> Kalle: this bug is there since ever, I guess this patch can be queued for
> next.
Thanks, applied.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vge
> This patch fix a spelling typo in MODULE_DESCRIPTION in
> wl1251/main.c
>
> Signed-off-by: Masanari Iida
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
> From: Miaoqing Pan
>
> ar9550 or later chips, the AR_GPIO_IN_OUT register only can
> control GPIO[0:3]. For the extra GPIO, use standard GPIO calls
> instead of WMAC internal registers.
>
> Signed-off-by: Miaoqing Pan
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscri
> Use bool constants as the return values instead of 1 and 0.
>
> Signed-off-by: Joe Perches
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordom
> rtl8192cu can't connect to AP after physical reconnect.
> according to dmesg, that problem's cause was DHCP timeout.
>
> rtl_is_special_data function checks packet type for adjusting rate.
> when that function is called from _rtl_rc_get_highest_rix, it can not
> calculate offset correctly. so i
> From: Fred Chou
>
> As the driver may send multiple wmi commands with identical cmd id,
> it is more robust to check seq number for timeout instead.
>
> Signed-off-by: Fred Chou
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscribe from this list: send the line "unsubs
"Grumbach, Emmanuel" writes:
> Hi Kalle,
>
> This is for 4.1. A bunch of work all over from the team.
> I'll be away for a week or so, but I'll monitor email, but I hope you
> won't have issues with this.
> Let me know. Thanks!
>
>
> The following changes since commit 2c44be81f0fc147eed9dc63e2601
On 04/06/2015 10:17 PM, Janusz Dziedzic wrote:
> On 7 April 2015 at 07:12, Michal Kazior wrote:
>> On 7 April 2015 at 02:39, Ben Greear wrote:
>>> Has anyone tried running ath10k to ath9k IBSS?
>>>
>>> I'm trying this with a somewhat hacked 4.0-rc6 kernel,
>>> and latest wpa_supplicant.
>>>
>>> a
Vladimir Kondratiev writes:
> On Monday, March 30, 2015 10:45:56 AM Johannes Berg wrote:
>> On Mon, 2015-03-30 at 11:28 +0300, Vladimir Kondratiev wrote:
>> > cfg80211_ops.stop_ap supposed to have interface closed
>> > as post condition. Fulfill this requirement.
>>
>> "closed" is rather mislead
Every tracing file must have its own TRACE_SYSTEM defined.
The iwlwifi tracepoint header broke this and added in the middle
of the file:
#undef TRACE_SYSTEM
#define TRACE_SYSTEM iwlwifi_io
#undef TRACE_SYSTEM
#define TRACE_SYSTEM iwlwifi_ucode
#undef TRACE_SYSTEM
#define TRACE_SYSTEM iwlw
Every tracing file must have its own TRACE_SYSTEM defined.
The brcmsmac tracepoint header broke this and added in the middle
of the file:
#undef TRACE_SYSTEM
#define TRACE_SYSTEM brcmsmac
#undef TRACE_SYSTEM
#define TRACE_SYSTEM brcmsmac_tx
#undef TRACE_SYSTEM
#define TRACE_SYSTEM brcmsma
On 04/07/2015 09:05 AM, Ilan Peer wrote:
> Previously, VHT capabilities and supported MCSs where set for all
> bands, although VHT is only allowed on 5.2 GHz band. Fix it.
I saw a patch on ath10k list that enabled VHT for 2.4Ghz for
that driver/firmware...are you sure it is absolutely not supporte
Declare that MCS 0-9 are supported for all Rx chains.
Signed-off-by: Ilan Peer
---
drivers/net/wireless/mac80211_hwsim.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/mac80211_hwsim.c
b/drivers/net/wireless/mac80211_hwsim.c
index 2f0ebda..c5
Previously, VHT capabilities and supported MCSs where set for all
bands, although VHT is only allowed on 5.2 GHz band. Fix it.
Signed-off-by: Ilan Peer
---
drivers/net/wireless/mac80211_hwsim.c | 50 +--
1 file changed, 25 insertions(+), 25 deletions(-)
diff --gi
On Tue, 2015-04-07 at 10:21 -0400, Steven Rostedt wrote:
> On Tue, 07 Apr 2015 08:58:58 +0200
> Johannes Berg wrote:
>
> > On Mon, 2015-04-06 at 23:13 -0400, Steven Rostedt wrote:
> > > Every tracing file must have its own TRACE_SYSTEM defined.
> >
> > Oh, that requirement is new to me. I also h
On Tue, 07 Apr 2015 08:58:58 +0200
Johannes Berg wrote:
> On Mon, 2015-04-06 at 23:13 -0400, Steven Rostedt wrote:
> > Every tracing file must have its own TRACE_SYSTEM defined.
>
> Oh, that requirement is new to me. I also have the same in iwlwifi, with
> even more TRACE_SYSTEMs.
OK, the reaso
On Tue, 2015-04-07 at 08:55 -0400, Steven Rostedt wrote:
> Hmm, I must have missed the iwlwifi part, as that should have not built
> with an allmodconfig :-/
Dunno, it seems that should be selected with allmodconfig, and it has 5
different ones ... :)
> > I could merge through my tree but I gues
On Tue, 2015-04-07 at 12:07 +0200, Samuel Ortiz wrote:
> Hi Joe,
Hi Samuel.
> > Resending after 8 weeks with no reply/review.
[]
> Sorry for the lag. Patch applied to nfc-next now.
Oh, no worries, these were all just minor details,
thanks, Joe
--
To unsubscribe from this list: send the line "u
On Tue, 07 Apr 2015 08:58:58 +0200
Johannes Berg wrote:
> On Mon, 2015-04-06 at 23:13 -0400, Steven Rostedt wrote:
> > Every tracing file must have its own TRACE_SYSTEM defined.
>
> Oh, that requirement is new to me. I also have the same in iwlwifi, with
> even more TRACE_SYSTEMs.
Well, it's ne
From: Johannes Berg
If the connect request from userspace didn't include an extended
capabilities IE, create one using the driver capabilities. This
fixes VHT associations, since those need to set the operating mode
notification capability.
Reviewed-by: Gregory Greenman
Signed-off-by: Johannes
From: Johannes Berg
As the next patch will require the IE splitting utility functions
in cfg80211, move them there from mac80211.
Signed-off-by: Johannes Berg
---
include/net/cfg80211.h | 58 ++
include/net/mac80211.h | 28 ---
Hi Joe,
On Tue, Apr 07, 2015 at 12:17:00AM -0700, Joe Perches wrote:
> Add missing terminating newlines to nfc_info and nfc_err
> to avoid possible interleaving from other messages.
>
> Miscellanea:
>
> o typo fix of "unknonwn" in message
> o remove unnecessary OOM messages as there's a generic
On Mon, 2015-04-06 at 10:55 +0530, deepak kumar Pradhan wrote:
> Driver used for Access point is madwifi(0.9.3) and Access point also
> added to the Bridge with the wds support.
> (We don't have access to target source code so we can't modify code on
> target platform)
>
> So it looks like madwif
Add missing terminating newlines to nfc_info and nfc_err
to avoid possible interleaving from other messages.
Miscellanea:
o typo fix of "unknonwn" in message
o remove unnecessary OOM messages as there's a generic dump_stack()
o realign arguments
Signed-off-by: Joe Perches
---
Adding Andrew Mor
On Mon, 2015-04-06 at 23:13 -0400, Steven Rostedt wrote:
> Every tracing file must have its own TRACE_SYSTEM defined.
Oh, that requirement is new to me. I also have the same in iwlwifi, with
even more TRACE_SYSTEMs.
> The mac80211 tracepoint header broke this and add in the middle
> of the file h
30 matches
Mail list logo
