From: "John W. Linville" <linville@tuxdriver.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Etna <etna@openmailbox.org>, linux-wireless@vger.kernel.org
Subject: Re: MediaTek WiFi hardware support in upstream kernel
Date: Tue, 28 Oct 2014 09:46:08 -0400 [thread overview]
Message-ID: <20141028134608.GA26283@tuxdriver.com> (raw)
In-Reply-To: <544E8CB4.3000607@rempel-privat.de>
On Mon, Oct 27, 2014 at 07:19:32PM +0100, Oleksij Rempel wrote:
> Am 27.10.2014 um 16:20 schrieb John W. Linville:
> > On Mon, Oct 27, 2014 at 11:02:00AM +0800, Etna wrote:
> >> I am not a developer, but I stumbled upon this just a couple of days ago in
> >> the OpenWRT forums:
> >>
> >> https://forum.openwrt.org/viewtopic.php?id=53215
> >>
> >> In short, MediaTek is looking for volunteers to help get their drivers
> >> mainlined in the upstream kernels; this includes drivers for their USB and
> >> PCI wifi hardware under both the MediaTek and Ralink brands. They are
> >> willing to provide "chip info, reference driver, dev board, etc" and even
> >> some degree of sponsorship, apparently subject to their management's
> >> approval.
> >>
> >> In exchange, they require that the volunteers fulfill the following
> >> requirements:
> >> - skilled in wifi driver development
> >> - provide a suitable schedule / roadmap
> >> - be able to get the code mainlined in the official linux kernel.
> >>
> >> Those who are keen on taking up the task can contact the original poster at
> >> hua.shao[AT]mediatek.com
> >>
> >> **Disclaimer: I am in no way related to, or under the employ of MediaTek or
> >> Ralink. I am only posting this here because I have a handful of MT wifi
> >> chips which I hope to see being supported in the upstream kernel so that I
> >> can actually use them under Linux,
> >
> > Well, this is mostly good to see. I hope there is someone that wants
> > to take-up the cause!
> >
> > If someone is interested in working-on the project above but for
> > whatever reason doesn't want to deal with MediaTek on their own,
> > feel free to contact me. I'll try to be helpful however I can.
> >
> > Thanks,
> >
> > John
>
>
> Sounds interesting and as perfect possibility to learn. I would like to
> do it, but i have two concerns:
> - i never wrote an wifi driver from scratch.
FWIW, I think MediaTek already has some form of drivers. With that
said, it might be easier to write new mac80211-based ones than to
adapt the existing ones.
> - i'm seeking for a job. It means if i will find one, this project will
> get lower priority.
No one can ask anything more.
> If nobody has problems with this two points, then i'm ok.
It sounds like we have a volunteer! Let me know if you need any
specific help or guidance.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-10-28 14:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 3:02 MediaTek WiFi hardware support in upstream kernel Etna
2014-10-27 15:20 ` John W. Linville
2014-10-27 18:19 ` Oleksij Rempel
2014-10-28 13:46 ` John W. Linville [this message]
2014-10-28 14:06 ` Arend van Spriel
2014-10-28 14:20 ` Oleksij Rempel
2014-10-29 10:17 ` Felix Fietkau
2014-11-11 11:55 ` Oleksij Rempel
2014-11-12 21:04 ` Felix Fietkau
2014-11-12 21:35 ` Larry Finger
2015-02-06 17:29 ` Jakub Kiciński
2015-02-25 0:49 ` Sergei Antonov
2015-02-25 9:33 ` mt7601u dies during channel switch (was: MediaTek WiFi hardware support in upstream kernel) Jakub Kiciński
2015-02-25 23:58 ` Sergei Antonov
2015-02-26 16:05 ` Jakub Kiciński
2015-02-26 18:50 ` Sergei Antonov
2015-02-26 19:01 ` Jakub Kiciński
2015-03-02 10:30 ` Sergei Antonov
2015-02-26 13:56 ` MediaTek WiFi hardware support in upstream kernel poma
2015-02-26 14:40 ` Jakub Kiciński
[not found] ` <5520FB36.8050301@openmailbox.org>
2015-04-05 9:12 ` Etna
2015-05-18 0:03 ` poma
2015-05-19 1:03 ` poma
2015-05-20 17:06 ` poma
2015-05-20 17:14 ` Jakub Kiciński
2015-05-21 13:37 ` poma
2015-06-27 20:45 ` poma
2015-12-23 15:05 ` poma
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=20141028134608.GA26283@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=etna@openmailbox.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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.