Hi Greg,
On Thu, Dec 4, 2014 at 3:39 PM, Greg Kroah-Hartman
wrote:
> On Thu, Dec 04, 2014 at 07:07:58AM +0530, Parth Sane wrote:
>> Hi,
>> I'd say I'm midway through with c programming(part of my computer
>> engineering degree course) and know a decent amount of git. So yes I'm
>> comfortable wri
On Thu, Dec 04, 2014 at 07:07:58AM +0530, Parth Sane wrote:
> Hi,
> I'd say I'm midway through with c programming(part of my computer
> engineering degree course) and know a decent amount of git. So yes I'm
> comfortable writing code.
Ok great, let's see if it's just a matter of some changes to th
Hi,
I'd say I'm midway through with c programming(part of my computer
engineering degree course) and know a decent amount of git. So yes I'm
comfortable writing code.
Also here's the link to an eBay listing for the same hardware.
http://www.ebay.com/itm/like/231051816145?lpid=82&item=231051816145&l
On Sun, Nov 30, 2014 at 06:55:12PM +, Parth Sane wrote:
> Hi Greg,
> You can find the source code attached as a tarball. It works and I have tested
> it myself. You only need to use make and make install for this.
This really looks like a variant of some existing devices, the rt2x00,
Ralink dr
From: Rafael J. Wysocki
After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks
depending on CONFIG_PM_RUNTIME may now be changed to depend on
CONFIG_PM.
Replace CONFIG_PM_RUNTIME with CONFIG_PM in drivers/nfc/trf797
Dave,
One last(?) batch of fixes hoping to make 3.18...
In this episode, we have another trio of rtlwifi fixes
repairing a little more damage from the major update of the
rtlwifi-family of drivers. These editing mistakes caused some
memory corruption and missed a flag critical to proper interrup
From: Hante Meuleman
Some 43602 devices are band specific and identify themselves
with different PCIE device ID. This patch adds support for the
43602 2.4G and 5.0G devices used in for example R8000 router.
Reviewed-by: Arend Van Spriel
Reviewed-by: Franky (Zhenhui) Lin
Reviewed-by: Pieter-Pau
From: Franky Lin
Use single message MSI to replace legacy interrupt.
Reviewed-by: Arend Van Spriel
Reviewed-by: Hante Meuleman
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Franky Lin
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/brcm80211/brcmfmac/pcie.c | 4
1 file ch
From: Hante Meuleman
The ifidx provided by FW needs to be offsetted when receiving data
packets.
Cc: sta...@vger.kernel.org # v3.17, v3.18
Reviewed-by: Arend Van Spriel
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Hante Meuleman
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/
From: Hante Meuleman
The vendor specific commands was always using main interface,
change this to use the by caller supplied interface.
Reviewed-by: Arend Van Spriel
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Hante Meuleman
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/brc
From: Hante Meuleman
Reviewed-by: Arend Van Spriel
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Hante Meuleman
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/brcm80211/brcmfmac/fwil.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/drive
From: Hante Meuleman
This patch adds support for multiple BSS interfaces (AP). In
total three AP configurations can be created. In order to use
multiple BSS firmware needs to support it.
Reviewed-by: Arend Van Spriel
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Hante Meuleman
Signed-off-
Hope this series can make it before the merge window. It contains
two patches that I marked for stable 3.18 as it is probably not
possible to pass them through the wireless tree this late in the
game.
This series add some BCM43602 PCIe ids which are used in Netgear R8000
and the other main feature
From: Hante Meuleman
Cc: sta...@vger.kernel.org # v3.17, v3.18
Reviewed-by: Arend Van Spriel
Reviewed-by: Pieter-Paul Giesberts
Signed-off-by: Hante Meuleman
Signed-off-by: Arend van Spriel
---
drivers/net/wireless/brcm80211/brcmfmac/msgbuf.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On Wed, Dec 3, 2014 at 10:58 AM, Brent Taylor wrote:
> On Wed, Dec 3, 2014 at 8:05 AM, Brent Taylor wrote:
>> On Tue, Dec 2, 2014 at 11:37 PM, Kalle Valo wrote:
>>> Brent Taylor writes:
>>>
On Dec 2, 2014 11:24 PM, "Kalle Valo" wrote:
>
> Brent Taylor writes:
>
> >I a
Arend,
Thanks, that is the publication!
I've tried to summarize the topic at
http://wiki.prplfoundation.org/wiki/Complying_with_FCC_rules_on_5ghz_wifi.
I hope that provides folks with enough background to understand what's
going on and the issues with fixing it. If you think you can add
additiona
On Wed, Dec 3, 2014 at 8:05 AM, Brent Taylor wrote:
> On Tue, Dec 2, 2014 at 11:37 PM, Kalle Valo wrote:
>> Brent Taylor writes:
>>
>>> On Dec 2, 2014 11:24 PM, "Kalle Valo" wrote:
Brent Taylor writes:
>I actually ran the wpa_supplicant with -t as the parameter not
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists. Otherwise return the global regdom.
When no wiphy-idx is specified, return the global regdomain as well as
all wiphy-specific regulatory domains in the system, via a new nested
list of attributes.
Ad
Ad-hoc requires beaconing for regulatory purposes. Validate that the
channel is valid for beaconing, and not only enabled.
Signed-off-by: Arik Nemtsov
Reviewed-by: Luis R. Rodriguez
---
net/wireless/reg.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/net/wireless/re
This patch fix the checkpatch.pl warning:
WARNING: space prohibited before semicolon
Signed-off-by: Anjana Sasindran
---
drivers/staging/rtl8723au/hal/odm_HWConfig.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723au/hal/odm_HWConfig.c
b/drive
From: Jonathan Doron
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
A self-managed wiphys only employs regulatory information obtained from
the FW and driver and does not use other cfg80211 sources like
beacon-hints, country-code IEs and hint
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can
distinguish them as such.
Signed-off-by: Arik Nemtsov
Revie
You may have noticed that Linus has released 3.18-rc7. So, the merge
window for 3.19 is around the corner!
For those that need a reminder, the opening of the merge window is
a _deadline_ for new features. Once the merge window opens, only
fixes will be accepted for 3.19. In fact, any non-fix pa
On Tue, Dec 2, 2014 at 11:37 PM, Kalle Valo wrote:
> Brent Taylor writes:
>
>> On Dec 2, 2014 11:24 PM, "Kalle Valo" wrote:
>>>
>>> Brent Taylor writes:
>>>
>>> >I actually ran the wpa_supplicant with -t as the parameter not
>>> > knowing how many 'd's I could put there before I hit the
On 3 December 2014 at 09:11, Kalle Valo wrote:
[...]
> diff --git a/drivers/net/wireless/ath/ath10k/core.c
> b/drivers/net/wireless/ath/ath10k/core.c
> index 0f4369e4f358..815d6e27aa53 100644
> --- a/drivers/net/wireless/ath/ath10k/core.c
> +++ b/drivers/net/wireless/ath/ath10k/core.c
> @@ -844,6
On 3 December 2014 at 09:10, Kalle Valo wrote:
[...]
> diff --git a/drivers/net/wireless/ath/ath10k/core.h
> b/drivers/net/wireless/ath/ath10k/core.h
> index e0999cdaa18f..8c839f68beac 100644
> --- a/drivers/net/wireless/ath/ath10k/core.h
> +++ b/drivers/net/wireless/ath/ath10k/core.h
[...]
> @@
On 12/02/14 22:40, Michael Tokarev wrote:
30.11.2014 15:04, Arend van Spriel wrote:
Thanks. Did not find what I was looking for, but I started working on
integrating btcoex related functionality. The attached patch will print
some info so I can focus on the required functionality for your devic
On 12/02/14 20:35, Arend van Spriel wrote:
On 12/02/14 01:31, John W. Linville wrote:
On Mon, Dec 01, 2014 at 04:27:25PM -0600, Eric Schultz wrote:
All,
I work for the prpl Foundation, an open source foundation organized by
a number of companies, most related to MIPS. One project we work with
On Tue, 2014-12-02 at 21:28 -0500, Richard Guy Briggs wrote:
> 1) Workshops (day 1)
FWIW, we're planning a wireless summit as a workshop here, which should
give us a little more breathing room than e.g. the 3-hour slot at LPC.
I'll put up the wiki page and other things and start working on an
age
From: Michal Kazior
Latest main firmware branch introduced a new WMI
ABI called wmi-tlv. It is not a tlv strictly
speaking but something that resembles it because
it is ordered and may have duplicate id entries.
This prepares ath10k to support new hw.
Signed-off-by: Michal Kazior
Signed-off-by
From: Michal Kazior
Since the 10.x fw branch support was introduced it
became apparent ath10k will need to be able to
deal with different fw ABIs eventually.
The patch creates an abstraction for dealing with
command and event structures across different ABIs
and mostly gets rid of the
ATH10K_FW_
From: Michal Kazior
Some functions can be shared across different WMI
ABIs. Make them public so different WMI backends
can use them from different source files in the
future.
Signed-off-by: Michal Kazior
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/wmi.c | 136 ++
From: Michal Kazior
This splits the actual event parsing into
intermediary structures to facilitate future
support of vastly different ABI WMI backends.
Signed-off-by: Michal Kazior
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/wmi.c | 383 +
d
Instead of using feature flags, add new 32 bit variable for managing different
WMI versions. This makes it firmware interface tests a bit less convoluted,
especially when we add one more interface.
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/core.c | 49 ++
Use the error handling style preferred in ath10k. Makes it easier to add
ath10k_init_firmware_features() function in the next patch.
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/core.c | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git
It's easier to manage firmware version differences when we configure them in
one place. Rename ath10k_core_init_max_sta_count() to
ath10k_core_init_firmware_features() and start moving most of the firmware
version ("features") handling to that function.
Signed-off-by: Kalle Valo
---
drivers/net/
Better to have this in same place as other firmware interface handling.
Signed-off-by: Kalle Valo
---
drivers/net/wireless/ath/ath10k/core.c |2 ++
drivers/net/wireless/ath/ath10k/htt_tx.c |5 -
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/ath
Hi,
here's v4 of Michal's patches to add WMI TLV interface support to
ath10k.
v4:
* fix error handling for ath10k_core_init_firmware_features()
* ar->htt.max_num_pending_tx = TARGET_TLV_NUM_MSDU_DESC
* use enum ath10k_fw_wmi_op_version op_version in struct ath10k_wmi
* add ATH10K_FW_WMI_OP_VE
38 matches
Mail list logo
