linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kubakici@wp.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Felix Fietkau <nbd@openwrt.org>
Subject: Re: Driver for Mediatek MT7630E
Date: Wed, 29 Jul 2015 10:03:06 +0200	[thread overview]
Message-ID: <20150729100306.7d5d20af@north> (raw)
In-Reply-To: <CACRpkdYTJWS7mbw_OJtW78ThQ6jZ7aSoM5uR1SLihV4L+E5vtQ@mail.gmail.com>

On Wed, 29 Jul 2015 09:38:04 +0200, Linus Walleij wrote:
> On Wed, Jul 29, 2015 at 1:24 AM, Xose Vazquez Perez
> <xose.vazquez@gmail.com> wrote:
> > Linus Walleij wrote:
> >
> >> Did anything ever happen to this?
> >>
> >> My daughter has this device in her laptop it seems, sigh.
> >>
> >> I might start fiddling with it unless someone else is already
> >> doing it.
> >
> > Jakub Kicinski was working on it at: https://github.com/kuba-moo/mt7630e
> 
> Ah yeah that is what I have running. It's a fork of rt2x00 so it's
> missing all fixes since 3.11 or so, just a question of when this
> becomes unsupportable.

The rt2x00 does not change that much itself so it's not a biggie.
However, we are missing all the mac80211-related changes :/
 
> This code is a complete mashup of Linux and duct-taped Windows
> NDIS-based driver code, my eyes are bleeding from looking at it.
> 
> The defines etc patched in have obvious gaps due to other unsupported
> chips such as MT7601u I suspect. I guess it's necessary to also
> look at this in order to not screw things up for 7601.
> https://github.com/porjo/mt7601

The problem with this hardware is that it's a something between old
Ralink stuff and new AC devices which Felix is supporting in mt76,
just like mt7601u.  I started hacking on mt76 to add support but not
sure if Felix is interested in merging support for old chips there.

So the support for mt7630e could be added in three places,
theoretically: (1) rt2x00, (2) mt7601u, (3) mt76.  IMO they're all bad
choices.

Also MediaTek has no interest in supporting Open Source driver for this
device.

  reply	other threads:[~2015-07-29  8:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 23:24 Driver for Mediatek MT7630E Xose Vazquez Perez
2015-07-29  7:38 ` Linus Walleij
2015-07-29  8:03   ` Jakub Kicinski [this message]
2015-07-29 10:47   ` Xose Vazquez Perez
  -- strict thread matches above, loose matches on Subject: below --
2015-07-28 22:23 Linus Walleij
2015-08-10 12:46 ` Linus Walleij
2014-06-25  9:41 Josip Volf - Wuk
2014-06-27  0:20 ` Larry Finger
2014-06-27  6:53   ` Gertjan van Wingerde
2014-06-27 17:29     ` Larry Finger
2014-06-11 15:45 Larry Finger
2014-06-12  7:16 ` Helmut Schaa
2014-06-12 12:44   ` Stanislaw Gruszka
2014-06-12 16:33     ` Matt Chen
2014-06-12 19:22       ` Larry Finger
2014-06-13 13:25         ` Stanislaw Gruszka
2014-06-13 13:49           ` Larry Finger

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=20150729100306.7d5d20af@north \
    --to=kubakici@wp.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=xose.vazquez@gmail.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).