RE RE

This message is the last notification about U USD14.5 million bearing our Name as Beneficiary, all effort to reach you have not be successful, Please if you Receive this message kindly respond back stating your Desire to make the claim, Reconfirm your full name and age Mr. Mr.Campbell Neiman

RE: RE

Please confirm receipt of my previous mail..When can i call you -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

RE:

​Our new web mail has been improved with a new messaging system from Owa/outlook which also include faster usage on email, shared calendar, web-documents and the new 2015 anti-spam version. Please use the link below to complete your update for our new Owa/outlook improved web mail. CLICK HERE

Re:

Hi, I work with one of the major banks in Cambodia as the director of audit. I have a proposal for you, a very urgent and quick business that will be completed in 12 working days. I have just discovered documents relating to funds belonging to a deceased client of our bank, I went through all

Re:

Dear Esteemed Friend, My name is Mr. Amit Jain, I double as the Group Chief Operations Officer Emaar Properties and Chief Executive Officer Emaar Dubai. Let me know the possibilities of setting up a private investment in your country as I am interested in your region. I have interest in Real Es

Re:

Hi Arend, I am still experiencing the issue Sebastien initially described (no wlan0 device, "SDIO drive strength" warnings etc) on a Thinkpad Tablet 10 for the latest kernel release, 4.2. Doesn't the 4.2 kernel include the required fix? Thanks, Oleg -- To unsubscribe from this list: send the li

Re:

Please ignore, not sure why this landed without a subject. On Tue, Sep 27, 2016 at 9:50 AM, Rajat Jain wrote: > From: Wei-Ning Huang > > Date: Thu, 17 Mar 2016 11:43:16 +0800 > Subject: [PATCH] mwifiex: report wakeup for wowlan > > Enable notifying wakeup source to the PM core. This allow darkre

Re:

With profound love in my heart, I Kindly Oblige your interest to very important proposal.. It is Truly Divine and require your utmost attention.. S hlubokou láskou v mém srdci, Laskave jsem prinutit svuj zájem k návrhu .. Je velmi duležité, skutecne Divine a vyžadují vaši nejvyšší pozorn

Re:

Hello Recipient, My name is Mrs Amanda Jacob. I am 59 years old and I was diagnosed for cancer about 2 years ago. I will be going in for an operation later today.I decided to WILL/donate the sum of (Fourteen Millions Two Hundred Fifty Eight Thousand United States Dollars) to you for the good

Re:

Attn: I am wondering why You haven't respond to my email for some days now. reference to my client's contract balance payment of (11.7M,USD) Kindly get back to me for more details. Best Regards Amos Kalonzo

RE:

How are you today and your family? I require your attention and honest co-operation about some issues which i will really want to discuss with you which. Looking forward to read from you soon. Qin's __ Sky Silk, http://aknet.kz

Re: Re: Re: Re: [PATCH 3/3] mwifiex: debugfs: trigger device dump for usb interface

Ganapathi Bhat ; James Cao > > Subject: [EXT] Re: Re: Re: [PATCH 3/3] mwifiex: debugfs: trigger device dump > for usb interface > > External Email > > -- > On Fri, Dec 01, 2017 at 08:36:01AM +, Xinming Hu wro

Re: (re)licensing the wireless wiki

On Mon, 2015-01-12 at 12:16 +0100, Johannes Berg wrote: > I've emailed every contributor who I could find an email address for, > but some (~40) don't have an email address and I already have a bunch of > bounces (~50). Additionally, gmail has apparently decided that I was spamming -- so you may

Re: (re)licensing the wireless wiki

On 01/12/2015 09:26 AM, Johannes Berg wrote: On Mon, 2015-01-12 at 12:16 +0100, Johannes Berg wrote: I've emailed every contributor who I could find an email address for, but some (~40) don't have an email address and I already have a bunch of bounces (~50). Additionally, gmail has apparently

Re: (re)licensing the wireless wiki

2015-01-12 20:57 GMT+02:00 Pat Erley : > On 01/12/2015 09:26 AM, Johannes Berg wrote: >> >> On Mon, 2015-01-12 at 12:16 +0100, Johannes Berg wrote: >> >>> I've emailed every contributor who I could find an email address for, >>> but some (~40) don't have an email address and I already have a bunch

Re: (re)licensing the wireless wiki

> 2015-01-12 20:57 GMT+02:00 Pat Erley : >> On 01/12/2015 09:26 AM, Johannes Berg wrote: >>> >>> On Mon, 2015-01-12 at 12:16 +0100, Johannes Berg wrote: >>> I've emailed every contributor who I could find an email address for, but some (~40) don't have an email address and I already have

Re: [SOLVED] Re: Oops with rtl8187

On 07/12/2015 05:29 PM, Oliver Kurth wrote: I have it solved now, I think - the issue was the cable :-P. I replaced the cable, and it's a lot more stable. With another cable I didn't see the Oops any more. On the RPi, I also need a cable with 2 USB plugs, one for extra power. Sorry for the nois

Re: Re: Re: [PATCH] mwifiex: add tdls uapsd support module parameter

Hi, > -Original Message- > From: Dmitry Torokhov [mailto:d...@google.com] > Sent: 2017年7月21日 1:29 > To: Brian Norris > Cc: Xinming Hu; Xinming Hu; Ganapathi Bhat; Linux Wireless; Kalle Valo; > raja...@google.com; Zhiyuan Yang; Tim Song; Cathy Luo > Subject: [EXT] Re

Re: [EXT] Re: mwifiex: update set_mac_address logic

Ganapathi Bhat writes: > I did resend the patch with 'git send-email': > https://patchwork.kernel.org/patch/10990209/ Thanks, I see it now. -- Kalle Valo

RE: [EXT] Re: mwifiex: update set_mac_address logic

Hi Kalle, I did resend the patch with 'git send-email': https://patchwork.kernel.org/patch/10990209/ Kindly review; Thanks, Ganapathi

Re: Re: [PATCH] iw: Static analyser fixes

nlmsg_free(ssids); + nlmsg_free(freqs); return 1; case FREQ: freq = strtoul(argv[i], &eptr, 10); -- 1.9.1 --- Original Message --- Sender : Julian Calaby Date : Jun 30, 2015 17:59 (GMT+05:30) Title : Re

RE: [EXT] Re: mwifiex: apply radar flag

> From: Kalle Valo [mailto:kv...@codeaurora.org] > Sent: Wednesday, April 05, 2017 4:19 PM > To: Amitkumar Karwar > Cc: linux-wireless@vger.kernel.org; Ganapathi Bhat; Karthik > Doddayennegere Ananthapadmanabha; Amitkumar Karwar > Subject: [EXT] Re: mwifiex: apply radar flag >

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

can be sure that each driver/hardware has its own bugs and limitations related to this. Ath10k wave 1 and wave 2 that I am aware of would ignore and/or not ACK probe responses sent back to an MAC address that is not that of the station itself. And changing the mac of a station would require co

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

ng the mac of a station would require complete re-association AFAIK.  That is likely just one of the many issues. I should add: If you really want to scan in this manner, you could just create a new station vdev with random addr and have it do the scanning, then delete it when done? The orig

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

dress that is not that of the station itself. And changing the mac of a station would require complete re-association AFAIK.  That is likely just one of the many issues. Yes, I understand that some hardware would not support this. But the question is does this check belong at the nl80211 lay

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

probe responses sent back to an MAC address that is not that of the station itself. And changing the mac of a station would require complete re-association AFAIK. That is likely just one of the many issues. Yes, I understand that some hardware would not support this. But the question is

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

> I've been poking around at how this flag is used and I noticed this > check in net/wireless/nl80211.c: > > nl80211_check_scan_flags() > > if (*flags & NL80211_SCAN_FLAG_RANDOM_ADDR) { > int err; > > if (!(wiphy->features & randomness_flag) || >

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

Hi Sergey, On 04/12/2019 04:26 AM, Sergey Matyukevich wrote: I've been poking around at how this flag is used and I noticed this check in net/wireless/nl80211.c: nl80211_check_scan_flags() if (*flags & NL80211_SCAN_FLAG_RANDOM_ADDR) { int err; if (!(

Re: NL80211_SCAN_FLAG_RANDOM_ADDR ?

On 4/12/2019 5:00 PM, Denis Kenzior wrote: Or put another way, besides hardware limitations, are there reasons why you would not want to randomize probe request address when connected? I was hoping to find your answer using 'git blame'. You might already have tried that. The wdev->current_bss

RE: Transaction

From: John Schlesselman Sent: Monday, November 09, 2015 5:08 PM To: John Schlesselman Subject: RE: Transaction Transaction Contact me ---> jon.symonds...@yahoo.com.sg for details.​​​

Re: RegulatoryDB

On Mon, Nov 23, 2015 at 03:50:53PM -0500, Robert wrote: > For Educational/Learning Purposes I am attempting to change some > information in this database... Is it possible to change data within > this binary file? You can make changes to db.txt and then build a new binary database from that. H

Re: rtl8192ce

Lobachevskii Vitalii writes: > Hello, > > The RTL8192CE device seems to work fine without any firmware, so you may > make it fully optional, removing dependency on FW_LOADER. Of course that > require some patching, but if I understood the driver internals > correctly, simple complete(&rtlpriv->fir

Re: rtl8192ce

On 08/25/2016 08:17 AM, Jes Sorensen wrote: Lobachevskii Vitalii writes: Hello, The RTL8192CE device seems to work fine without any firmware, so you may make it fully optional, removing dependency on FW_LOADER. Of course that require some patching, but if I understood the driver internals corr

Re: rtl8192ce

Larry Finger writes: > On 08/25/2016 08:17 AM, Jes Sorensen wrote: >> Lobachevskii Vitalii writes: >> The realtek devices all require firmwere to operate correctly, >> including the 8192c series. There are a bunch of commands flying back >> and forth between the driver and the firmware. >> >> If

Re: RTL8189ETV

On 31.08.2015 18:00, poma wrote: > > Hi Fi, > > What is this device, is it supported by > https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es > > $ modinfo rtl8189es > modinfo: ERROR: Module rtl8189es not found. > or is it supported by https://githu

Re: RTL8189ETV

On 08/31/2015 12:06 PM, poma wrote: On 31.08.2015 18:00, poma wrote: Hi Fi, What is this device, is it supported by https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es $ modinfo rtl8189es modinfo: ERROR: Module rtl8189es not found. or is it supp

Re: RTL8189ETV

On 31.08.2015 19:51, Larry Finger wrote: > On 08/31/2015 12:06 PM, poma wrote: >> On 31.08.2015 18:00, poma wrote: >>> >>> Hi Fi, >>> >>> What is this device, is it supported by >>> https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es >>> >>> $ modinfo rt

Re: RTL8189ETV

On 08/31/2015 03:31 PM, poma wrote: On 31.08.2015 19:51, Larry Finger wrote: On 08/31/2015 12:06 PM, poma wrote: On 31.08.2015 18:00, poma wrote: Hi Fi, What is this device, is it supported by https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es $

Re: RTL8189ETV

Hi, On 31-08-15 22:31, poma wrote: Let's see if Hans knows what type of this device is RTL8189ETV. Assuming you are talking about the wifi module of the Allwinner H3 based Orangepi2 as shown here: http://linux-sunxi.org/images/9/96/Xunlong_OrangePi2_front.jpg Then we are talking about a rea

Re: RTL8189ETV

On 01.09.2015 10:43, Hans de Goede wrote: > Hi, > > On 31-08-15 22:31, poma wrote: > >> Let's see if Hans knows what type of this device is RTL8189ETV. > > Assuming you are talking about the wifi module of the Allwinner H3 > based Orangepi2 as shown here: > > http://linux-sunxi.org/images/9/96/

Re: RTL8189ETV

On 31.08.2015 23:25, Larry Finger wrote: > On 08/31/2015 03:31 PM, poma wrote: >> On 31.08.2015 19:51, Larry Finger wrote: >>> On 08/31/2015 12:06 PM, poma wrote: On 31.08.2015 18:00, poma wrote: > > Hi Fi, > > What is this device, is it supported by > https://github.com/or

RE: RTL8192ee

Larry, I know that to some degree I am jumping this chain. That being said, please allow me to offer encouragement in the development of the rtl8192ee, rtl872ae, and the other members of the rtlwifi_new github. I have been using these myself, and keeping them in my sights as my commercial prod

Re: RTL8192ee

On 01/27/2015 08:19 AM, Jason Plum wrote: Larry, I know that to some degree I am jumping this chain. That being said, please allow me to offer encouragement in the development of the rtl8192ee, rtl872ae, and the other members of the rtlwifi_new github. I have been using these myself, and keep

Re: Hello

Good Day am Dr. Raymond Atu I have very important issue to discuss with you Please kindly get back to me urgently .E-mail : raymon...@hotmail.com raymno...@gmail.com == = Disclosure: This e-mail is intended only for the above address

Re: wil6200

On 9/25/2016 6:15 PM, Vikram wrote: > Hi, > > Could you please let me know as to how to change the mode of wil6200 > chip from WBE to WiFi? > > Regards, > Vikram > What is the exact device you are using? Older devices have firmware that only supports WBE mode. Thanks, Lior

Re: wil6200

Hi Lior, On 26 September 2016 at 18:19, Lior David wrote: > On 9/25/2016 6:15 PM, Vikram wrote: >> Hi, >> >> Could you please let me know as to how to change the mode of wil6200 >> chip from WBE to WiFi? >> >> Regards, >> Vikram >> > What is the exact device you are using? Older devices have firm

Re: wil6200

On 9/26/2016 9:05 PM, Vikram wrote: > Hi Lior, > > On 26 September 2016 at 18:19, Lior David wrote: >> On 9/25/2016 6:15 PM, Vikram wrote: >>> Hi, >>> >>> Could you please let me know as to how to change the mode of wil6200 >>> chip from WBE to WiFi? >>> >>> Regards, >>> Vikram >>> >> What is the

Re: help

On 12/04/14 20:01, m_del_b...@libero.it wrote: can you help me with this problems? thx Suspect that you are building newer kernel driver code against an older kernel. How did you populate /home/hp/rtl8192su-master/rtlwifi? Regards, Arend Sent from Libero Mobile

Re: Hello

Hello, I Have a financial transaction i want you to handle for me. Please kindly Reply for more details. Regards, Ms. Reem Al-Hashimy Reply To reem1...@naver.com

RE: ATTENTION!!!

From: Loretta Robles Sent: Friday, December 29, 2017 1:01 PM To: Loretta Robles Subject: ATTENTION!!! You have been randomly selected for a donation. Contact soriz4...@gmail.com for claims.

Re: cfg80211_ops

On 06/21/2017 05:03 PM, Tobin C. Harding wrote: Hi, Is some one able to please confirm for me that the following cfg80211_ops callbacks are enough to implement a minimal functioning Wi-Fi driver. Assume that a virtual interface is added during driver initialization. scan add_key get_key del_ke

Re: cfg80211_ops

On Wed, Jun 21, 2017 at 05:53:13PM -0700, Igor Mitsyanko wrote: > On 06/21/2017 05:03 PM, Tobin C. Harding wrote: > > > >Hi, > > > >Is some one able to please confirm for me that the following > >cfg80211_ops callbacks are enough to implement a minimal functioning > >Wi-Fi driver. Assume that a vir

Re: cfg80211_ops

On Wed, 2017-06-21 at 17:53 -0700, Igor Mitsyanko wrote: > > > scan > > add_key > > get_key > > del_key > > sat_default_key > > connect > > disconnect > > set_wiphy_params > > Hi, is this for STA-only? I guess you also need > mgmt_frame_register > mgmt_tx For really basic operation, I don't thin

Re: cfg80211_ops

On 22-06-17 08:30, Johannes Berg wrote: > Also, set_default_key is, IIRC, not needed in WPA/WPA2 client mode, but > may be needed for WEP - not sure off the top of my head. correct (if brcmfmac is). Gr. AvS

Re: Re: Re: [PATCH] mwifiex: cancel pcie/sdio work in remove/shutdown handler

s Cao > ; Ganapathi Bhat ; Ellie Reeves > ; Christoph Hellwig > Subject: [EXT] Re: Re: [PATCH] mwifiex: cancel pcie/sdio work in > remove/shutdown handler > > External Email > > -- > + Christopher >

Re: Re: Re: [PATCH] mwifiex: cancel pcie/sdio work in remove/shutdown handler

Hi Simon, On Wed, Jan 10, 2018 at 12:30:35PM +, Xinming Hu wrote: > > -Original Message- > > From: Brian Norris [mailto:briannor...@chromium.org] > > On Tue, Jan 09, 2018 at 11:42:21AM +, Xinming Hu wrote: > > > I am not sure whether there is any mutual exclusion protect between >

Re: Re: Re: [PATCH] mwifiex: cancel pcie/sdio work in remove/shutdown handler

On Thu, Jan 11, 2018 at 06:25:09PM -0800, Brian Norris wrote: > Anyway, I'll do my own testing and then submit my patch properly. OK, so I definitely confirmed: if your patch does anything, it introduces a new deadlock possibility. Just trigger a Wifi timeout or reset from within remove(), and you

Re: [v2,1/1] wireless: airo: re-use mac_pton()

> mac_pton() converts 6-byte MAC / BSSID to binary format. Change an open coded > variant by the generic one. > > Signed-off-by: Andy Shevchenko Thanks, applied to wireless-drivers-next.git. Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of

RE: [EXT] Re: mwifiex: Fix invalid port issue

> From: Kalle Valo [mailto:kv...@codeaurora.org] > Sent: Wednesday, April 05, 2017 4:22 PM > To: Ganapathi Bhat > Cc: linux-wireless@vger.kernel.org; Cathy Luo; Nishant Sarmukadam; > Ganapathi Bhat > Subject: [EXT] Re: mwifiex: Fix invalid port issue > > Ganapathi Bhat w

Re: Re: [PATCH] mwifiex: fixes the trivial print

; From: Kalle Valo [mailto:kv...@codeaurora.org] > Sent: 2017年6月13日 15:53 > To: Caesar Wang > Cc: amitkar...@gmail.com; Xinming Hu; Nishant Sarmukadam; Ganapathi > Bhat; linux-wireless@vger.kernel.org; net...@vger.kernel.org; > linux-ker...@vger.kernel.org; briannor...@chromium.org; &g

Re: Re: [PATCH] mwifiex: fixes the trivial print

m; Ganapathi Bhat; linux-wireless@vger.kernel.org; net...@vger.kernel.org; linux-ker...@vger.kernel.org; briannor...@chromium.org; jeffy.c...@rock-chips.com; Ganapathi Bhat Subject: [EXT] Re: [PATCH] mwifiex: fixes the trivial print External Email Hi Xinming,

Re: Re: Re: [PATCH 3/3] mwifiex: debugfs: trigger device dump for usb interface

Ganapathi Bhat ; James Cao > > Subject: [EXT] Re: Re: [PATCH 3/3] mwifiex: debugfs: trigger device dump for > usb interface > > External Email > > -- > Hi Simon, > > On Wed, Nov 15, 2017 at 11:31:

Re: Re: Re: [PATCH 3/3] mwifiex: debugfs: trigger device dump for usb interface

On Fri, Dec 01, 2017 at 08:36:01AM +, Xinming Hu wrote: > Thanks for the suggestion, it sounds better than exporting > mwifiex_send_cmd() directly. > In addition to used as debugfs tirgger, the "defined point" > if_ops.device_dump is only used in command timeout context. > For sdio/pcie interfa

RE: Re: Re: Re: [PATCH v3 4/4] mwifiex: pcie: extract wifi part from combo firmware during function level reset

Hi Brain, > -Original Message- > From: Brian Norris [mailto:briannor...@chromium.org] > Sent: 2017年4月15日 0:56 > To: Xinming Hu > Cc: Linux Wireless; Kalle Valo; Dmitry Torokhov; raja...@google.com; > Amitkumar Karwar; Cathy Luo; Ganapathi Bhat > Subject: [EXT] Re:

Re: [PATCH 1/1] wireless: airo: re-use mac_pton()

Andy Shevchenko writes: > mac_pton() converts 6-byte MAC / BSSID to binary format. Change an open coded > variant by the generic one. > > Signed-off-by: Andy Shevchenko This breaks compilation: CC [M] drivers/net/wireless/cisco/airo.o drivers/net/wireless/cisco/airo.c: In function ‘proc_APL

Re: [PATCH 1/1] wireless: airo: re-use mac_pton()

On Thu, 2015-11-26 at 15:32 +0200, Kalle Valo wrote: > Andy Shevchenko writes: > > > mac_pton() converts 6-byte MAC / BSSID to binary format. Change an > > open coded > > variant by the generic one. > > > > Signed-off-by: Andy Shevchenko > > This breaks compilation: > >   CC [M]  drivers/net/

RE: [EXT] Re: [PATCH] mwifiex: handle race during mwifiex_usb_disconnect

Hi Brian, > > @@ -644,6 +644,9 @@ static void mwifiex_usb_disconnect(struct > usb_interface *intf) > > MWIFIEX_FUNC_SHUTDOWN); > > } > > > > + if (adapter->workqueue) > > + flush_workqueue(adapter->workqueue); > > This seems like a bad fix. I'm

Re: wireless workshop (was: Re: Announcing Netdev 0x13 conference)

On Tue, Oct 09, 2018 at 12:28:23PM +0200, Johannes Berg wrote: > Kalle and I have (more or less) decided to propose a wireless workshop > for Netdev 0x13. > > In order to gauge interest and plan room size, can you reply (privately > if you like) if this would work for you and you'd (want to) atten

Re: ath5k: remove duplicated re-assignment to pointer 'tq'

Colin Ian King wrote: > Pointer tq is initialized with &ah->ah_txq[queue] and then a few > lines later is re-assigned the same value, hence this duplicate > assignment is redundant and can be removed. > > Cleans up clang warning: > drivers/net/wireless/ath/ath5k/qcu

RE: [EXT] Re: [PATCH] MAINTAINERS: drop akarwar from mwifiex

Hi Kalle/Brian, > Brian Norris writes: > > > His email is bouncing, and I expect he's not doing this work any > more. > > > > Cc: Amitkumar Karwar > > Cc: Nishant Sarmukadam > > Cc: Ganapathi Bhat > > Cc: Xinming Hu > > Signed-off-by: Brian Norris > > --- > > Or alternatively, we can update

Re: Re: [PATCH] mwifiex: add device specific ioctl handler

Cathy Luo ; Ganapathi Bhat > ; Xinming Hu > Subject: [EXT] Re: [PATCH] mwifiex: add device specific ioctl handler > > External Email > > -- > On 9/20/2017 8:44 AM, Xinming Hu wrote: > > From: Xinming Hu &g

RE: [PATCH] ath10k: Re-enable TXQs for all devices

> Commit 4ca1807815aa6801aaced7fdefa9edacc2521767 disables the use of the > mac80211 TXQs for some devices because of a theoretical throughput > regression. We have not seen this regression for a while now, so it should be > safe to re-enable TXQs. > > Signed-off-by: Toke

RE: [PATCH] ath10k: Re-enable TXQs for all devices

Rajkumar Manoharan writes: >> Commit 4ca1807815aa6801aaced7fdefa9edacc2521767 disables the use of the >> mac80211 TXQs for some devices because of a theoretical throughput >> regression. We have not seen this regression for a while now, so it should be >> safe to re-en

Re: [v2] ath10k: Re-enable TXQs for all devices

el qdisc drop performance, which was fixed in commit 9d18562a2278 > ("fq_codel: add batch ability to fq_codel_drop()"). Since then, we have not > seen the TXQ-related regression, so it should be safe to re-enable TXQs. > > [1] http://lists.infradead.org/pipermail/ath10k/

Re: mac80211_hwsim: EXT_FEATURE_CAN_REPLACE_PTK0 ?

On Mon, 2019-04-22 at 09:07 -0700, James Prestwood wrote: > Hi, > > I know for actual hardware drivers this feature requires more than just > the flip of a switch, but is there any technical reason why this is not > turned on in mac80211_hwsim? I know it was added relatively recently, > so maybe m

Re: mac80211_hwsim: EXT_FEATURE_CAN_REPLACE_PTK0 ?

On Tue, 2019-04-23 at 12:16 +0200, Johannes Berg wrote: > On Mon, 2019-04-22 at 09:07 -0700, James Prestwood wrote: > > Hi, > > > > I know for actual hardware drivers this feature requires more than just > > the flip of a switch, but is there any technical reason why this is not > > turned on in m

Re: carl9170 crash

tedheadster writes: > I am getting this crash for the carl9170 in recent kernels, though I > have not yet bisected it. It hangs the networking system completely > (ifconfig -a never returns) and it prevents a reboot. I have to use > sysrq-b to 'cleanly' reboot the system. > > I can apply and te

Re: carl9170 crash

Kalle, On Wed, May 1, 2019 at 3:20 AM Kalle Valo wrote: > What was the last working version? It worked perfectly in 4.14.110. The next version I have to test is 4.18.20 where I first noticed problems with loading regulatory.db, but the driver still worked. The same for 4.19.33, 4.20.17, and 5.0

Re: carl9170 crash

Kalle, I just tried to bisect this and got an unexpected result: commit 4c3f49ae1306c05e91211c06feddfd0a4a57fabd "Merge branch 'for-5.1-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu". I wanted to share this in case it is correct. I have a stronger suspicion that the probl

Re: SPDX identifier

https://www.kernel.org/doc/html/v4.17/process/license-rules.html explains why the comment style differs between .c and .h On Thu, 16 May 2019 at 12:36, Arend Van Spriel wrote: > > Hi Kalle, Thomas, > > I added SPDX tags in brcm80211 driver sources. Although it is a > no-brainer I decided to run c

Re: SPDX identifier

On May 16, 2019 4:17:55 PM James Hughes wrote: On Thu, 16 May 2019 at 12:36, Arend Van Spriel wrote: Hi Kalle, Thomas, I added SPDX tags in brcm80211 driver sources. Although it is a no-brainer I decided to run checkpatch for the changes and quirky stuff started to happen. For all files I

Re: SPDX identifier

Arend, On Thu, 16 May 2019, Arend Van Spriel wrote: > Hi Kalle, Thomas, > > I added SPDX tags in brcm80211 driver sources. Although it is a no-brainer I > decided to run checkpatch for the changes and quirky stuff started to happen. > For all files I added: > > // SPDX-License-Identifier > > b

Re: SPDX identifier

On 5/16/2019 8:17 PM, Thomas Gleixner wrote: Arend, On Thu, 16 May 2019, Arend Van Spriel wrote: Hi Kalle, Thomas, I added SPDX tags in brcm80211 driver sources. Although it is a no-brainer I decided to run checkpatch for the changes and quirky stuff started to happen. For all files I added:

Re: brcmfmac & DEL_INTERFACE

On 5/28/2019 8:16 PM, Denis Kenzior wrote: Hi Arend, We noticed that brcmfmac doesn't support .del_virtual_intf for non-p2p/ap interface types.  Any chance this can be added? We currently remove all wifi interfaces and re-create the needed ones with SOCKET_OWNER set, and it would be ni

Re: brcmfmac & DEL_INTERFACE

Hi Arend, On 05/28/2019 03:27 PM, Arend Van Spriel wrote: On 5/28/2019 8:16 PM, Denis Kenzior wrote: Hi Arend, We noticed that brcmfmac doesn't support .del_virtual_intf for non-p2p/ap interface types.  Any chance this can be added? We currently remove all wifi interfaces and re-creat

Re: rt2x00 regression

On Thu, Sep 26, 2019 at 06:32:23PM +0200, Anton Olsson wrote: > Hello I have a USB based ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 > Wireless Adapter, that stops working with recent kernels. It works on kernel > 5.1.15 and does not work with 5.2.7 or 5.3.1 (I have not tested other > ve

Re: Invalid SPLX

Hi, On Wed, Dec 2, 2015 at 10:35 PM, Andy Lutomirski wrote: > Hi- > > My laptop has SPLC implemented like this: > > Name (SPLX, Package (0x04) > { > Zero, > Package (0x03) > { > 0x8000, > 0x8000, >

Re: Cannot unsubscribe

Mário Lopes writes: > Our institution DNS as changed due to legal requirments, but old is > kept active with redirection to new one. So, when I send a e-mail, it > is sent with new DNS. Also I'm receiving e-mails that are sent to > older (probably as with this one from mailling list) due to > red

Re: SUPPORTS_CLONED_SKBS question

+Ido. On Mon, 2015-12-14 at 13:58 +0100, Janusz Dziedzic wrote: > Base of SUPPORTS_CLONED_SKBS description, we can set this flag > in case driver will not touch payload or tailroom. > What exactly does it mean? Well, you must not modify the data in a way that would make the clone invalid. That m

Re: Mediatek wifi

Sorry, 's/usb/pci' On Mon, Dec 21, 2015 at 2:09 PM, Anca Emanuel wrote: > Hi Linus Walleij, and everyone interested. > > http://askubuntu.com/questions/676390/no-wi-fi-on-ubuntu-14-04-lts-asus-notebook-with-mediatek-mt7630e > > Here is the bug report: > https://bugs.launchpad.net/ubuntu/+source/l

Re: Mediatek wifi

On Mon, Dec 21, 2015 at 1:09 PM, Anca Emanuel wrote: > https://github.com/neurobin/MT7630E is reported to work for wifi. Yes this works because it contains a forked and bitrotting copy of the entire Mediatek code drop including a fork of rt2x00 from the v3.10 kernel. It's not going to last, and

Re: getting start

On Mon, Dec 28, 2015 at 12:53 PM, Swapnil Pathak wrote: > Hi , > > I also want to contribute to wireless and want to create patches. I am not > getting from where I need to start. How to start. Please can any one guide > me. > Start with the wiki. https://wireless.wiki.kernel.org/ https://wirele

Re: [GIT] Networking

On Tue, May 17, 2016 at 12:11 PM, David Miller wrote: > > Highlights: Lowlights: 1) the iwlwifi driver seems to be broken My laptop that uses the intel 7680 iwlwifi module no longer connects to the network. It fails with a "Microcode SW error detected." and spews out register state over and ov

Re: [GIT] Networking

On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds wrote: > On Tue, May 17, 2016 at 12:11 PM, David Miller wrote: >> >> Highlights: > > Lowlights: > > 1) the iwlwifi driver seems to be broken > > My laptop that uses the intel 7680 iwlwifi module no longer connects > to the network. It fails with a

Re: [GIT] Networking

Hi Emmanuel, Linus, On Wed, 2016-05-18 at 06:37 +0300, Emmanuel Grumbach wrote: > On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds > wrote: > > > > On Tue, May 17, 2016 at 12:11 PM, David Miller > > wrote: > > > > > > > > > Highlights: > > Lowlights: > > > >  1) the iwlwifi driver seems to b

Re: [GIT] Networking

On Wed, May 18, 2016 at 4:51 AM, Coelho, Luciano wrote: > Hi Emmanuel, Linus, > > > On Wed, 2016-05-18 at 06:37 +0300, Emmanuel Grumbach wrote: >> On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds >> wrote: >> > >> > On Tue, May 17, 2016 at 12:11 PM, David Miller > > > wrote: >> > > >> > > >> > > H

Re: [GIT] Networking

On Wed, 2016-05-18 at 06:20 -0600, Reinoud Koornstra wrote: > On Wed, May 18, 2016 at 4:51 AM, Coelho, Luciano > wrote: > > > > Hi Emmanuel, Linus, > > > > > > On Wed, 2016-05-18 at 06:37 +0300, Emmanuel Grumbach wrote: > > > > > > On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds > > > wrote:

Re: [GIT] Networking

On Wed, May 18, 2016 at 6:41 AM, Coelho, Luciano wrote: > On Wed, 2016-05-18 at 06:20 -0600, Reinoud Koornstra wrote: >> On Wed, May 18, 2016 at 4:51 AM, Coelho, Luciano >> wrote: >> > >> > Hi Emmanuel, Linus, >> > >> > >> > On Wed, 2016-05-18 at 06:37 +0300, Emmanuel Grumbach wrote: >> > > >> >

Re: [GIT] Networking

On Wed, 2016-05-18 at 06:51 -0600, Reinoud Koornstra wrote: > On Wed, May 18, 2016 at 6:41 AM, Coelho, Luciano > wrote: > > > > On Wed, 2016-05-18 at 06:20 -0600, Reinoud Koornstra wrote: > > > > > > On Wed, May 18, 2016 at 4:51 AM, Coelho, Luciano > > > wrote: > > > > > > > > > > > > Hi Emma

Re: [GIT] Networking

On Wed, May 18, 2016 at 7:23 AM, Coelho, Luciano wrote: > > I can confirm that 4.6 contains the same bug. And reverting the patch > I mentioned does solve the problem... > > The same patch works fine in our internal tree. I'll have to figure > out together with Emmanuel what the problem actually

  1   2   3   4   5   6   7   8   9   10   >