From: "Tuomas Räsänen" <tuomasjjrasanen@tjjr.fi>
To: Jakub Kicinski <kubakici@wp.pl>, Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, tuomasjjrasanen@opinsys.fi
Subject: About adding support for MT76x2U to Linux kernel
Date: Fri, 14 Aug 2015 11:15:26 +0300 [thread overview]
Message-ID: <20150814081526.GC20192@hackpad.Elisa> (raw)
Hi
I'm very interested in adding support (especially AP mode) for MT76x2U
USB-dongles to Linux kernel. I'm aware of the work you both have done, Felix's
work on MT76x2 PCI-devices and Jakub's work to add support for MT7601U. So I
guess no one knows this exact problem domain better than you (perhaps excluding
MediaTek's subcontractors who wrote the original vendor driver), that is why I'm
writing specifically to you.
I have ASUS USB-N53_B1 adapter (0b05:180b) as a test device:
https://wikidevi.com/wiki/ASUS_USB-N53_B1
As far as I know, no one has been / is working on MT76x2U USB-dongles, please
correct me if I'm wrong.
I have a strong system programming background, some knowledge on 802.11 in
general, but no actual experience in Linux kernel programming. So I'm pretty
confident that I'll have many questions to throw at you before I have managed to
make anything functional.
So, to get started, I was wondering what would be the best way forward. I can
think of two reasonable approaches:
#1 Base the new driver on Felix's mt76 and modify it to work on USB-bus
instead of PCI.
#2 Base the new driver on Jakub's mt7601u and modify it to handle mt76x2u
devices by using Felix's mt76 and the vendor driver as a reference.
Of course there's the third option to write it from scratch based solely on the
vendor driver, but because you have already done such a great job in
interpreting the outdated and quite ugly (subjective view?) vendor driver code,
that would be foolish.
At first I had a hunch that #1 would be the easiest way forward, but now that I
skimmed through the code, I'm beginning to think that approach #2 has the least
resistance. However, I'm not necessarily looking for the easiest way but *the
best/right* way. So any ideas, opinions and thoughts are more than welcome.
--
Tuomas
next reply other threads:[~2015-08-14 8:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:15 Tuomas Räsänen [this message]
2015-08-14 12:32 ` About adding support for MT76x2U to Linux kernel Jakub Kiciński
2015-12-16 18:53 ` Felix Fietkau
2015-12-16 21:24 ` Johannes Stezenbach
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=20150814081526.GC20192@hackpad.Elisa \
--to=tuomasjjrasanen@tjjr.fi \
--cc=kubakici@wp.pl \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=tuomasjjrasanen@opinsys.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 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).