linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jakub Kiciński" <moorray3@wp.pl>
To: linux-wireless@vger.kernel.org
Cc: 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: Fri, 6 Feb 2015 18:29:15 +0100	[thread overview]
Message-ID: <20150206182915.7467bac7@north> (raw)
In-Reply-To: <5463D28F.9080106@lwfinger.net>

Hello everyone!

I put together a mac80211 driver for Mediatek MT7601U.  It's partially
based on Felix's mt76, but I'm not sure if it will make sense to merge
the two together.  MT7601U is a pretty old 1x1 bgn chip for USB dongles
and mt76 now only supports the latest and greatest ac APs.

I'm testing STA functionality right now and it seems to be working ok.
The code is very much a work in progress but if anyone is interested you
can get it here:

https://github.com/kuba-moo/mt7601u

Cheers,
kuba

  reply	other threads:[~2015-02-06 17:29 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 [this message]
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
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=20150206182915.7467bac7@north \
    --to=moorray3@wp.pl \
    --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=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).