From: Larry Finger <Larry.Finger@lwfinger.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Matt Chen <mattsled@gmail.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
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: Fri, 13 Jun 2014 08:49:39 -0500 [thread overview]
Message-ID: <539B0173.2070300@lwfinger.net> (raw)
In-Reply-To: <20140613132545.GD2211@redhat.com>
On 06/13/2014 08:25 AM, Stanislaw Gruszka wrote:
> On Thu, Jun 12, 2014 at 02:22:34PM -0500, Larry Finger wrote:
>> On 06/12/2014 11:33 AM, Matt Chen wrote:
>>> If I remember correct for SLE11, that was from MediaTek-Ralink, they
>>> did it based on SLE11 kernel. The code is ouch but could work. That
>>> was a nightmare when I tried to port...can't imagine that.... :(
>>
>> I have not tested as my hardware has not been delivered, but I have
>> the driver building with current wireless-testing source. I also
>> have created a proper Makefile.
>>
>> Yes, merging the changes into rt2x00 will be a hassle.
>
> We usually we look at vendor driver and write new code to rt2x00 based
> on that. For example, I did that for RT5592, Gabor for RT3593. In
> oposite to cleaning up vendor driver in staging, it require lot of more
> work, but also guarantee that we will have clean and maintaible code.
That is what I plan on doing. This driver is already mac80211 based, thus I see
no benefit in going to staging. You will have plenty of opportunities to review
the code before it is submitted.
Larry
next prev parent reply other threads:[~2014-06-13 13:49 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
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 [this message]
-- 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=539B0173.2070300@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=IvDoorn@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mattsled@gmail.com \
--cc=sgruszka@redhat.com \
--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 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).