From: poma <pomidorabelisima@gmail.com>
To: "Jakub Kiciński" <moorray3@wp.pl>
Cc: linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>,
Felix Fietkau <nbd@openwrt.org>,
Oleksij Rempel <linux@rempel-privat.de>,
kubakici@wp.pl, "John W. Linville" <linville@tuxdriver.com>,
Etna <etna@openmailbox.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>
Subject: Re: MediaTek WiFi hardware support in upstream kernel
Date: Tue, 19 May 2015 03:03:33 +0200 [thread overview]
Message-ID: <555A8BE5.5020102@gmail.com> (raw)
In-Reply-To: <55592C54.6010204@gmail.com>
kernel 4.0.4 - no more:
WARNING: CPU: x PID: 0 at kernel/softirq.c:150 __local_bh_enable_ip+0x72/0xa0()
One more detail - at least for this MT7601U device, USB extension cable must be high quality.
next prev parent reply other threads:[~2015-05-19 1:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 3:02 MediaTek WiFi hardware support in upstream kernel Etna
2014-10-27 15:20 ` John W. Linville
2014-10-27 18:19 ` Oleksij Rempel
2014-10-28 13:46 ` John W. Linville
2014-10-28 14:06 ` Arend van Spriel
2014-10-28 14:20 ` Oleksij Rempel
2014-10-29 10:17 ` Felix Fietkau
2014-11-11 11:55 ` Oleksij Rempel
2014-11-12 21:04 ` Felix Fietkau
2014-11-12 21:35 ` Larry Finger
2015-02-06 17:29 ` Jakub Kiciński
2015-02-25 0:49 ` Sergei Antonov
2015-02-25 9:33 ` mt7601u dies during channel switch (was: MediaTek WiFi hardware support in upstream kernel) Jakub Kiciński
2015-02-25 23:58 ` Sergei Antonov
2015-02-26 16:05 ` Jakub Kiciński
2015-02-26 18:50 ` Sergei Antonov
2015-02-26 19:01 ` Jakub Kiciński
2015-03-02 10:30 ` Sergei Antonov
2015-02-26 13:56 ` MediaTek WiFi hardware support in upstream kernel poma
2015-02-26 14:40 ` Jakub Kiciński
[not found] ` <5520FB36.8050301@openmailbox.org>
2015-04-05 9:12 ` Etna
2015-05-18 0:03 ` poma
2015-05-19 1:03 ` poma [this message]
2015-05-20 17:06 ` poma
2015-05-20 17:14 ` Jakub Kiciński
2015-05-21 13:37 ` poma
2015-06-27 20:45 ` poma
2015-12-23 15:05 ` poma
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=555A8BE5.5020102@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=etna@openmailbox.org \
--cc=kubakici@wp.pl \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=linville@tuxdriver.com \
--cc=moorray3@wp.pl \
--cc=nbd@openwrt.org \
--cc=sgruszka@redhat.com \
--cc=users@rt2x00.serialmonkey.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).