From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Ivo van Doorn <IvDoorn@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stanislaw Gruszka <stf_xl@wp.pl>,
Gabor Juhos <juhosg@openwrt.org>
Subject: Re: Driver for Mediatek MT7630E
Date: Thu, 12 Jun 2014 14:44:09 +0200 [thread overview]
Message-ID: <20140612124408.GB7325@redhat.com> (raw)
In-Reply-To: <CAGXE3d81xMB3Y4WdTBPHKCC91QaieAQd5xzAqWSgGeonbD7_vw@mail.gmail.com>
On Thu, Jun 12, 2014 at 09:16:02AM +0200, Helmut Schaa wrote:
> On Wed, Jun 11, 2014 at 5:45 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> > In a recent E-mail interchange
> > (http://marc.info/?l=linux-wireless&m=140238255916367&w=2), I was made aware
> > that this device is not currently being handled by any driver in the kernel,
> > but that there was a GitHub repo at https://github.com/anthonywong/mt7630.
> > That code modifies rt2800pci to operate the MT7630E, but it is quite
> > outdated.
> >
> > As a followup, I found such a device at a reasonable price on E-bay, and
> > ordered it. It should arrive next week. I also was able to find the firmware
> > in an RPM for SUSE SLE11, and a license allowing redistribution. Before I
> > start modifying rt2800pci for this new device, I want to be assured that
> > this modification is not currently being done by anyone in the rt2x00
> > project. There is too much to be done to duplicate effort.
>
> I'm not doing anything in this regard at the moment. So I'm really glad if you
> are working on that!
>
> CC'ed Stanislaw even though I don't think he's doing anything regarding the
> device you've mentioned.
Nope, I'm not working on adding support for new chips to rt2x00 at
present nor plan to work on that in the near future, though I have that
on my TODO list :-)
> > For interested readers, I have modified the GitHub code to compile using the
> > current wireless-testing kernel source. If there is sufficient interest, I
> > could set up a new GH repo for it as an interim measure with conditional
> > code allowing it to build on recent kernels (3.5+).
> Awesome news.
+1
Stanislaw
next prev parent reply other threads:[~2014-06-12 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 15:45 Driver for Mediatek MT7630E Larry Finger
2014-06-12 7:16 ` Helmut Schaa
2014-06-12 12:44 ` Stanislaw Gruszka [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2015-07-28 22:23 Linus Walleij
2015-08-10 12:46 ` Linus Walleij
2015-07-28 23:24 Xose Vazquez Perez
2015-07-29 7:38 ` Linus Walleij
2015-07-29 8:03 ` Jakub Kicinski
2015-07-29 10:47 ` Xose Vazquez Perez
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=20140612124408.GB7325@redhat.com \
--to=sgruszka@redhat.com \
--cc=IvDoorn@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=helmut.schaa@googlemail.com \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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.