Jes Sorensen writes:
>>> Also how do we make sure that distros don't enable
>>> CONFIG_RTL8XXXU_UNTESTED? They are notarious of enabling kconfig options
>>> without thinking.
>>
>> Some distros enable staging whether you ask them or not. I think
>>
Larry Finger writes:
> On 09/06/2015 09:43 AM, Kalle Valo wrote:
>> jes.soren...@redhat.com writes:
>>
>>> Per default only devices I have actually tested will be enabled. If
>>> you are interested in trying it out with other 8188cu/8188ru/819[12]cu
>>> dongles, you
Jes Sorensen writes:
> Kalle Valo writes:
>> jes.soren...@redhat.com writes:
>>
>>> Per default only devices I have actually tested will be enabled. If
>>> you are interested in trying it out with other 8188cu/8188ru/819[12]cu
>>> dongles, you need
Hi Johannes,
I am looking at devcoredump subsystem and I was wondering about the
lifetime of the devcd folder. With dev_coredumpm() the description says:
"If a previous one hasn't been read yet, the new coredump is
discarded.". I am wondering what "read" means here. For testing I call
Chor Teck Law writes:
>> On Tuesday 04 Aug 2015 à 20:02:23 (+0300), Kalle Valo wrote:
>>
>> > I haven't looked at the driver myself yet. Do you have any estimates
>> > how much duplication there is?
>>
>
> I do think that someone interested in this thread should compare the
On Mon, 2015-09-07 at 11:47 +0200, Arend van Spriel wrote:
> Hi Johannes,
>
> I am looking at devcoredump subsystem and I was wondering about the
> lifetime of the devcd folder. With dev_coredumpm() the description says:
> "If a previous one hasn't been read yet, the new coredump is
>
Maxime Bizon writes:
> but from my POV, your pattern is: build new chipset, obsolete previous
> chipset, fork current firmware, make uncompatible changes to both
> firmware & host driver to accomodate new chipset peculiarities.
>
> and eventually, if a customer requests a
This patch removes the preprocessor definition from the codes, as shown in the
following, which is not used anymore.
- WILC_FULLY_HOSTING_AP
Signed-off-by: Tony Cho
---
drivers/staging/wilc1000/linux_mon.c | 97 ---
Larry Finger writes:
>> It's easier that the driver has it's on directory as everything
>> (makefile, kconfig etc) is cleanly separated. And actually I would like
>> to create a new vendor directory for realtek and have this in
>>
This patch remove build build warning from Handle_SetOperationMode function.
Host interface operation mode has one of 4 types from AP_MODE, STATION_MODE,
GO_MODE and CLIENT_MODE.
This values are range from 0x01 to 0x04 if mode is set correctly.
If value of host interface operation is 0, it is not
This patch removes commented codes.
Signed-off-by: Chaehyun Lim
---
drivers/staging/wilc1000/coreconfigurator.c | 7 ---
drivers/staging/wilc1000/host_interface.c | 88 -
drivers/staging/wilc1000/linux_mon.c| 61
This patch adds error check if kzalloc is failed.
Signed-off-by: Chaehyun Lim
---
drivers/staging/wilc1000/linux_wlan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/wilc1000/linux_wlan.c
b/drivers/staging/wilc1000/linux_wlan.c
index
This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC.
It is inside the spin lock region.
Signed-off-by: Chaehyun Lim
---
drivers/staging/wilc1000/wilc_msgqueue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 09/07/2015 04:06 AM, Kalle Valo wrote:
Larry Finger writes:
On 09/06/2015 09:43 AM, Kalle Valo wrote:
jes.soren...@redhat.com writes:
Per default only devices I have actually tested will be enabled. If
you are interested in trying it out with other
This patch replaces WILC_MALLOC with kzalloc.
Signed-off-by: Chaehyun Lim
---
drivers/staging/wilc1000/linux_wlan.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/wilc1000/linux_wlan.c
b/drivers/staging/wilc1000/linux_wlan.c
index
On 09/07/2015 11:54 AM, Johannes Berg wrote:
On Mon, 2015-09-07 at 11:47 +0200, Arend van Spriel wrote:
Hi Johannes,
I am looking at devcoredump subsystem and I was wondering about the
lifetime of the devcd folder. With dev_coredumpm() the description says:
"If a previous one hasn't been read
Updated to
net.git: 46cdc9b (ie. with mac80211 2015-09-04)
+ iwlwifi-next.git commits up to 5bff653
iwlwifi firmware: 16.215201.0
now connecting to my WPA-802.1X with a Intel 7260 fails, see dmesg.
From the wifi's wpa_supplicant file (actually wicd somehow accumulated
different ones for this
David Lin writes:
> The Linux driver for WRT1900AC. The work was initially developed as part of
> openwrt effort and maintained on https://github.com/kaloz/mwlwifi.
>
> This is still work in progress, with 8864 chipset more mature and tested,
> while 8897 for the similar use
From: Colin Ian King
The check for send_pkt being NULL is redundant before the call
to htc_reclaim_txctrl_buf, therefore it should be removed. This was
detected by static analysis by cppcheck.
Signed-off-by: Colin Ian King
---
Jes Sorensen writes:
>>> +static int rtl8xxxu_debug /* = 0 */; /* Avoid pointless checkpatch noise */
>>
>> Either assign it to zero or ignore the checkpatch warning, but please
>> don't do this.
>
> Problem is if I leave the = 0 some people will send pointless patches
David Lin writes:
> The Linux driver for WRT1900AC. The work was initially developed as part of
> openwrt effort and maintained on https://github.com/kaloz/mwlwifi.
>
> This is still work in progress, with 8864 chipset more mature and tested,
> while 8897 for the similar use
Dear all,
I'm having some issues in a modified version of mac80211, which I hope
you will help me with.
I want to report a lower bound of the channel utilization to which a
mesh device is tuned in for a research project. So far, I can read
successfully from debugfs this new statistic updated
> Kalle Valo writes:
>
> David Lin writes:
>
> > The Linux driver for WRT1900AC. The work was initially developed as
> > part of openwrt effort and maintained on https://github.com/kaloz/mwlwifi.
> >
> > This is still work in progress, with 8864 chipset
On Mon, Sep 7, 2015 at 1:44 PM, ferran wrote:
>
> So firstly, why can't I call drv_get_tsf from there? Is it because TSF
> is exactly then being reset? Secondly, I feel unsafe about
You left out posting the actual panic/warning you got, but one
possibility is beacon_get is
On 2015년 09월 08일 00:36, Chaehyun Lim wrote:
This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC.
It is inside the spin lock region.
Signed-off-by: Chaehyun Lim
---
drivers/staging/wilc1000/wilc_msgqueue.c | 2 +-
1 file changed, 1 insertion(+), 1
On Tue, Sep 08, 2015 at 11:23:07AM +0900, Tony Cho wrote:
>
>
> On 2015년 09월 08일 00:36, Chaehyun Lim wrote:
> >This patch use kmalloc with GFP_ATOMIC instead of WILC_MALLOC.
> >It is inside the spin lock region.
> >
> >Signed-off-by: Chaehyun Lim
> >---
> >
Hi Anreas,
On Mon, 2015-09-07 at 15:40 +0200, Andreas Reis wrote:
> Updated to
> net.git: 46cdc9b (ie. with mac80211 2015-09-04)
> + iwlwifi-next.git commits up to 5bff653
> iwlwifi firmware: 16.215201.0
>
> now connecting to my WPA-802.1X with a Intel 7260 fails, see dmesg.
>
> From the
> Kalle Valo [mailto:kv...@codeaurora.org] writes:
>
> David Lin writes:
>
> > The Linux driver for WRT1900AC. The work was initially developed as
> > part of openwrt effort and maintained on https://github.com/kaloz/mwlwifi.
> >
> > This is still work in progress, with 8864
Now that a new mac80211-based driver for Realtek devices has been submitted,
it is time to reorganize the directories. Rather than having directories
rtlwifi and rtl818x be in drivers/net/wireless/, they will now be in
drivers/net/wireless/realtek/. This change simplifies the directory
structure,
This patch adds kfree(mgmt_tx) when memory allocation of mgmt_tx->buff
fails in the second calls of kmalloc() to avoid the memory leak from mgmt_tx
first allocated before the second calls of kmalloc().
Signed-off-by: Tony Cho
Signed-off-by: Chris Park
This patch removes a preprocessor definition, SWITCH_LOG_TERMINAL,
which is not used. Enabling this definition affects the performance.
Signed-off-by: Tony Cho
---
drivers/staging/wilc1000/linux_wlan.c| 6 --
drivers/staging/wilc1000/wilc_wlan_cfg.c | 8
2
Hi,
replying to an older thread:
David Lin writes:
>> > +++ b/drivers/net/wireless/mwlwifi/Kconfig
>> > @@ -0,0 +1,17 @@
>> > +config MWLWIFI
>> > + tristate "Marvell Wireless WiFi driver (mwlwifi)"
>> > + depends on PCI && MAC80211 && MWIFIEX_PCIE=n
>>
>> Uh, what's with
Hello,
Thanks for helping me. I have some more questions related to parallel
usage of p2p and STA (station) interface.
I use a Nexus 5 device which has a BCM4339 [1] chip and it seems that
it's possible to transfer data in parallel using two connections: one
based on Wi-Fi direct(p2p, 2.4Ghz)
Kalle Valo writes:
> Hi,
>
> replying to an old thread first.
>
> Jes Sorensen writes:
>
>> Kalle Valo writes:
>>> jes.soren...@redhat.com writes:
>>>
MAINTAINERS |8 +
On 09/07/2015 01:43 PM, Jes Sorensen wrote:
Kalle Valo writes:
Hi,
replying to an old thread first.
Jes Sorensen writes:
Kalle Valo writes:
jes.soren...@redhat.com writes:
MAINTAINERS |
35 matches
Mail list logo