From: Johannes Stezenbach <js@sig21.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "Jakub Kiciński" <moorray3@wp.pl>,
"Tuomas Räsänen" <tuomasjjrasanen@tjjr.fi>,
linux-wireless@vger.kernel.org, tuomasjjrasanen@opinsys.fi,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: About adding support for MT76x2U to Linux kernel
Date: Wed, 16 Dec 2015 22:24:25 +0100 [thread overview]
Message-ID: <20151216212425.GA25906@sig21.net> (raw)
In-Reply-To: <5671B310.2080200@openwrt.org>
Hi,
On Wed, Dec 16, 2015 at 07:53:04PM +0100, Felix Fietkau wrote:
> Once I'm done with mt7603 bringup (monitor mode rx already works), I
> plan on submitting mt76 upstream, and then we can see about adding
> support for 76x2u, or even merging the hardware support for mt7601u.
>
> You can check out my work in the mt7603 branch here:
> https://github.com/openwrt/mt76/tree/mt7603
let me chime in to say that I'm interested to work on
support for mt7610u (TP-LINK Archer T2U/T2UH).
https://wikidevi.com/wiki/TP-LINK_Archer_T2U
I'm facing the same question as Tuomas about using
mt76 or mt7601u as the base?
Johannes
next prev parent reply other threads:[~2015-12-16 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:15 About adding support for MT76x2U to Linux kernel Tuomas Räsänen
2015-08-14 12:32 ` Jakub Kiciński
2015-12-16 18:53 ` Felix Fietkau
2015-12-16 21:24 ` Johannes Stezenbach [this message]
2015-12-17 20:28 ` Johannes Stezenbach
2015-12-17 8:55 ` Linus Walleij
2016-03-02 7:32 ` Tuomas Räsänen
2016-03-07 11:14 ` Johannes Stezenbach
2016-03-07 11:51 ` Felix Fietkau
2016-03-07 12:41 ` Johannes Stezenbach
2016-03-07 12:54 ` Felix Fietkau
2016-03-07 21:22 ` Felix Fietkau
2016-03-08 12:49 ` Johannes Stezenbach
2016-03-08 12:58 ` Felix Fietkau
2016-03-08 13:22 ` Johannes Stezenbach
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=20151216212425.GA25906@sig21.net \
--to=js@sig21.net \
--cc=linus.walleij@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=moorray3@wp.pl \
--cc=nbd@openwrt.org \
--cc=tuomasjjrasanen@opinsys.fi \
--cc=tuomasjjrasanen@tjjr.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.